another daisy chaining router question
I have a Netgear wireless/wired router in my office and need to expand the wireless segment to the other end of the building. I have a Linksys range expander but it does not appear to be compatible with the Netgear unit. I have a Linksys wireless/wired router in hand and would like to know if I can daisy chain these two units. The Netgear hosts 192.168.0.1 and the Linksys hosts 192.168.1.1, so these two routers are on different subnets?
If I can connect the two routers in my office and get the 192.168.1.1 network propagated to the other end on existing cable attached to the Linksys and then utilize the expander to service the other end of the building, talking back to the want through the 192.168.0.1 router, my life would be good again. Any insights as to how I should set this up, I have played with it a bit but not getting there yet. Your feedback is as always, greatly appreciated.
Carl at St. Andrew's UMC
If I can connect the two routers in my office and get the 192.168.1.1 network propagated to the other end on existing cable attached to the Linksys and then utilize the expander to service the other end of the building, talking back to the want through the 192.168.0.1 router, my life would be good again. Any insights as to how I should set this up, I have played with it a bit but not getting there yet. Your feedback is as always, greatly appreciated.
Carl at St. Andrew's UMC
Discusfish
Do you have an ethernet cable between the two sides of the building?
ASKER
Yes, I have ethernet current running off of the ;192.168.0.1 Netgear router for hard wire connections in that location.
You should be able to persuade the routers to talk through the ethernet across the building, with each serving the local wireless users. Make sure you use different channels that don't overlap.
Whichever one actually connects to the ADSL line or whatever becomes the "master".
Configure that to hand out IP addresses.
On the second one ("slave"), tell it not to hand out IP addresses - on my linksys, I was able to persuade it to use DHCP to get its own IP address from another DHCP server on our network, and not act as a DHCP server. For some reason, to get it to actually work, I had to plug the "internet" port into the general LAN ports, and then the cable connecting to the rest of the LAN/internet also into a general LAN port - plugging that into the Internet port didn't work. Connecting wireless devices get their IPs etc from the DHCP server on the network.
Connect the two together with a long ethernet cable and you're done. You may have to do a bit of fiddling with exactly what ports to use, but you should find plugging from a LAN port on Master into the Internet port of Slave (or the LAN of slave and a short cable between another LAN and the Internet port [both on Slave]) sorts it out.
Of course, if you need two /24 subnets, then it gets more complex, but if you have less than 250-odd devices, working off one subnet should be fine.
Whichever one actually connects to the ADSL line or whatever becomes the "master".
Configure that to hand out IP addresses.
On the second one ("slave"), tell it not to hand out IP addresses - on my linksys, I was able to persuade it to use DHCP to get its own IP address from another DHCP server on our network, and not act as a DHCP server. For some reason, to get it to actually work, I had to plug the "internet" port into the general LAN ports, and then the cable connecting to the rest of the LAN/internet also into a general LAN port - plugging that into the Internet port didn't work. Connecting wireless devices get their IPs etc from the DHCP server on the network.
Connect the two together with a long ethernet cable and you're done. You may have to do a bit of fiddling with exactly what ports to use, but you should find plugging from a LAN port on Master into the Internet port of Slave (or the LAN of slave and a short cable between another LAN and the Internet port [both on Slave]) sorts it out.
Of course, if you need two /24 subnets, then it gets more complex, but if you have less than 250-odd devices, working off one subnet should be fine.
ASKER
My concern is the fact that the Linksys is out of the box with 192.168.1.1
The NetGear is setup with 192.168.0.1
What do I have to do to allow the two to talk. If I change the Linksys/Wireless router to Static IP, what IP do I use. I am trying to avoid crashing the network during working hours with collisions, etc. but it is lookiing like once I have a solution I will likley have to spend some weekend time when I can get the network stand alone for testing. The Netgear uses .2-100 for its DHCP assignments so I suppose I could use something in the 101 to 150 range. I have a few remote printers static set in the 145-150 range now.
I am also assuming that a crossover is required between the Netgear(master/DHCP) and the Linksys(Slave/Wireless)? They are both in the same data cabinet and the extension cable is plugged into the slave server that runs to the destination area where I want to use the Linksys wireless expander, which is only compatible with the Linksys.
Your thoughts!
The NetGear is setup with 192.168.0.1
What do I have to do to allow the two to talk. If I change the Linksys/Wireless router to Static IP, what IP do I use. I am trying to avoid crashing the network during working hours with collisions, etc. but it is lookiing like once I have a solution I will likley have to spend some weekend time when I can get the network stand alone for testing. The Netgear uses .2-100 for its DHCP assignments so I suppose I could use something in the 101 to 150 range. I have a few remote printers static set in the 145-150 range now.
I am also assuming that a crossover is required between the Netgear(master/DHCP) and the Linksys(Slave/Wireless)? They are both in the same data cabinet and the extension cable is plugged into the slave server that runs to the destination area where I want to use the Linksys wireless expander, which is only compatible with the Linksys.
Your thoughts!
I don't have a Netgear here to play with, but they're usually pretty straightforward to configure.
Modern networking gear is usually auto MDI/MDIX on ports so you don't generally need crossover cables.
Simply move the linksys from the cabinet to the end of the cable where the remote server is, and plug the slave server into a port on the back of the linksys - you can then use the linksys range extender there (if you still need to). See my earlier note about how you sometimes have to plug the connection into the switch part of the router and then have a short patch between another port on the switch and the internet/WAN port.
Finally, to get everything talking (you never let me know if you have more than 250 hosts), just get everything working on the same subnet. Make the Netgear router do all the DHCP (turn it off on the Linksys), and assign everything IPs in 192.160.0/24. You should be able to configure the Linksys to request an IP from the Netgear (I suggest you get it to issue the same IP for that MAC address every time so you know what it's IP is - perhaps .2 so you can ping it for troubleshooting.
If you're not sure what to change, I put a screenshot of my Linksys WRT54GL in a configuration where it gets its IP from the network, and has DHCP turned off here:
https://www.experts-exchange.com/questions/25047605/How-to-setup-a-WiFi-router-in-my-office-of-a-building-with-its-own-that-I'm-connecting-to.html
You can obviously change the names to whatever you want - the important parts are to get the Internet setup to use DHCP (although you can also manually assign Static info if you prefer - just get the Netgear to be the gateway etc etc.).
You should set the LAN address (in Network Setup) to be different to the one the Netgear assigns (reserve .3 and set it here, for example) - so the Linksys will be both .2 and .3 - this should help to prevent network loops (which are bad). On my Linksys, the LAN's DHCP server gives the Internet port .45, and the LAN port is .46 - I can access the router through either IP.
Modern networking gear is usually auto MDI/MDIX on ports so you don't generally need crossover cables.
Simply move the linksys from the cabinet to the end of the cable where the remote server is, and plug the slave server into a port on the back of the linksys - you can then use the linksys range extender there (if you still need to). See my earlier note about how you sometimes have to plug the connection into the switch part of the router and then have a short patch between another port on the switch and the internet/WAN port.
Finally, to get everything talking (you never let me know if you have more than 250 hosts), just get everything working on the same subnet. Make the Netgear router do all the DHCP (turn it off on the Linksys), and assign everything IPs in 192.160.0/24. You should be able to configure the Linksys to request an IP from the Netgear (I suggest you get it to issue the same IP for that MAC address every time so you know what it's IP is - perhaps .2 so you can ping it for troubleshooting.
If you're not sure what to change, I put a screenshot of my Linksys WRT54GL in a configuration where it gets its IP from the network, and has DHCP turned off here:
https://www.experts-exchange.com/questions/25047605/How-to-setup-a-WiFi-router-in-my-office-of-a-building-with-its-own-that-I'm-connecting-to.html
You can obviously change the names to whatever you want - the important parts are to get the Internet setup to use DHCP (although you can also manually assign Static info if you prefer - just get the Netgear to be the gateway etc etc.).
You should set the LAN address (in Network Setup) to be different to the one the Netgear assigns (reserve .3 and set it here, for example) - so the Linksys will be both .2 and .3 - this should help to prevent network loops (which are bad). On my Linksys, the LAN's DHCP server gives the Internet port .45, and the LAN port is .46 - I can access the router through either IP.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.