Someone educate me - why would you distribute 169.x.x.x addresses? Isn't that what a self assigned ip would start with?
Sent from my iPhone using Tapatalk
Contrary to popular belief the 192.168.x.x network is nothing more than a network which is commonly used for in house subnets. Networks outside the "house", such as those networks used on the WWW are fully licensed, registered, and controlled/monitored. That is not to say the you can't use anything you want for a subnet on your own PRIVATE network, such as the network we are talking about here, or even for a very large company, as long as those addresses are restricted to traffic on your network only. The 169.x.x.x network you're are referring to is probably a loopback address.
I get a big kick out of some of the "solutions" I see published on the web, especially on this site. I say that because my day job for the past 30 years has been to design, implement and service some of the largest wide area networks, storage and server farms in the world. That would include a state police department, a "fast lane" network, and the network for a federal agency that gives old people money. It can be fun, and it can be exasperating.
The OP's goal here is to provide connectivity to three (3) buildings located in close proximity to each other. That means nothing more than three (3) workgroup solutions and a method for establishing a connection to the outside world (WWW). The OP states the site already has a DSL router being used by all three buildings, and copper running from the outer buildings to the house, so I would do nothing more than what I outline below.
The reason behind the use of static IP addresses.
The use of static networks has special meaning in larger networks. Servers, storage, firewalls, routers and most devices of that type are ALWAYS given a static address in larger or corporate networks. This is done for a number of reasons, too many to speak of in this short document. What I'll ask is that some of the reasoning to use and apply a static IP address become more apparent when creating small business and home networks. Yes, DHCP is your friend, but in corporate networks dedicated and redundant DHCP servers are used for the purpose of allocating IP addresses from groups allocated for specific devices, many of which now allow that device to retain an allocated IP address forever.
When creating smaller networks it is more often than not an advantage to use a static address for all of the devices attached to that network even though the initial planning may seem tedious for many, and not understood by most, a static IP address will always be your friend . The major advantage will be when problems arise (And they will), when a device is upgraded, when additional devices are added, and when devices on the network stop working or can't be found. It is and always will be easier to trouble shoot the lost connectivity of a device when you know the device located at 192.168.1.22 is a printer located at location "C" vs. "Let's walk around through three buildings and see where the little light on the port is off. ". Every aspect of network control and device connectivity is simplified by using a static address, except the initial assignment. So, if you like DHCP and it makes your life easy it's the thing do. If your network has grown a bit and the time and skill required to find a fault is more important, then I suggest static addresses. Ands finally, it doesn't hurt to put a label with the name and IP address on the front device. You may just one day thank me for that.
For this solution the OP will purchase;
3ea. low cost 10/100/1000 8 port hubs
2ea. single port WAPS
Enough Ethernet patch cables to connect all of the devices using the network to the 8 port hubs.
Total cost should be less than $2-400 plus labor if charged STEP #1 - Assigning IP addresses
Plan your IP scheme for the devices to be used, and using 192.168.1.xxx, that could and should by using, for a small network of this type, static addresses, and a flat network. (All the same subnet). There is ABSOLUTELY NO NEED for a separate subnet in each building. Not only is this complexity not required, but additional costs not needed.
MASK = 255.255.255.0, class "C", allows up to 253 devices attached
192.168.1.1 = gateway (DSL router)
192.168.1.10 thru .20 = servers
192.168.1. 21 thru .30 = printers
192.168.1. 31 thru .100 = PC's, tablets, etc.
192.168.1.101 thru .200 = all other devices
192.168.1.201 thru .210 - WAPs
Name each building. In this case we'll call the house with the DSL "A", and the outlying work spaces "B" and "C" for simplicity. STEP #2 - Creating your workgroup/small office/building network
Start by creating a workgroup/office network in each building using a single 10/100/1000 8 port switch, no routers required. Attach each device to the 8 port hub using copper, CAT 5 or 6, your choice. Address your devices as above and ping each device from within the building to insure connectivity, that the interface is active, properly addressed, and talking to the other devices in that building. Do this for all three buildings, "A", "B" and "C".
Wireless devices will be connected at a later step. STEP #3 - Attaching the main building to the WWW.
Using a patch cable attach the 8 port hub located in building "A" to the DSL router. This should be the only connection attached to the router other than the wide area connection itself, the connection from the outside world to the router. STEP #4, part a - Connecting the buildings/offices together
Go to building "A". Attach the copper running from buildings "B" and "C" to the DSL router using two of the available three (3) remaining ports on the DSL router, or connect these two cables to the 8 port hub previously attached to the DSL router in STEP #3 using ports 1 and 2 ("A" "B"). STEP #4, part b - Connecting the buildings/offices together
Go to building "B" and attach the cable running from building "A" to port 8 of the 8 port hub in building "B". Using any attached system ping the .1 gateway, any other active system in that building, and any active system in building "A". You should receive a response from every device. Using your web browser attempt to access the WWW. Google is a good choice for a site to use for this test. If all tests pass then building "B"s network is complete with the exception of wireless connections, and you can now move to building "C" and repeat. NOTE:
If during you tests you fail to receive a reply from a device, or if your devices can not ping any device on the network, start by checking the IP address and mask. If you can not access the WWW then check your DSL router security features for blocked MAC addresses, IP addresses, etc. STEP #5 - Wireless connectivity, IPads, printers, etc.
In this case speak with the client and the need for wireless connectivity. If the client has a DSL router which provides wireless connectivity, and provides that connectivity RELIABLY from building "A", "B", and "C" you're all set, and the installation and costs end here.
If reliability is an issue you will use a WAP (wireless access point) to provide connectivity. This requires nothing more than a WAP attached to the 8 port hub. This DOES NOT require an additional router or subnet and all devices attaching to the WAP will use a provided and available 192.168 address from the proper IP group listed above. The WAP itself is addressed using one of the IP addresses from the group reserved for WAPs. Good connectivity can be achieved inside, and probably outside of the buildings by attaching a WAP to the hubs in buildings "B" and "C".
The cost for this whole network would be less than $3-400, and time to install should be less than 4 hours. Congratulations, you've just learned how to create a low cost working and reliable flat network. Welcome to networking 101.
Switch - Your choice.http://www.netgear.com/home/products/networking/switches/GS608.aspx#tab-overview
WAP - My choice for this project. I use these often and have one in my own racks for access to my board, DSP, computer, etc.. If you use the WAP below then you could also eliminate the cost of the 8 port switch IF you only need to attach 3 or fewer devices in that building that are not wireless.http://www.netgear.com/business/products/wireless/soho-wireless/wn604.aspx
As a final note a fully redundant network can be created by using an additional two (2) interface adapters. ($50).