(no subject)
Okay, I had to post this. This is big!
So I've got this router upstairs, it's a wired one, and 2 computers connect to that directly via ethernet, and a third cat5e cable runs downstairs to connect the game consoles. There are two consoles however, and having to switch the cables out when you're couch-potatoed can be a task, so I set out to remedy this. The problem I had encountered was that the cat5e cable running downstairs came from a LAN port on the upstairs router, with an IP address handed out by the upstairs router's DHCP server. When the signal came downstairs, the WAN port on the bottom router recognized that specific IP address as its WAN, which would be incorrect. What followed was all devices being able to connect, but only one at a time; counter-intuitive to my goal. A phone call from Jason enlightened me, and I found out that by plugging in said cat5 cable to the downstairs router, it was given instructions to access the internet from the router, when it should be pushing through to the actual cable modem.
I plugged the cat5 cable instead into the downstairs router's LAN cable which made all the difference, as it was able to toggle the upstairs DHCP server, push through an IP address from the upstairs router downstairs, filtered by means of limiting the IP address range the downstairs router hands out as not to interfere with the upstairs router's IP address range field, and now...
everything works!
The problem now, is that the routers I am using are generic and have a limited amount of cache and memory, so there is an intermittent but temporary time-out of the network. Next paycheck? Industrial grade router/switch.
If you are wondering why routers can cost so much, applications like this are why.
So I've got this router upstairs, it's a wired one, and 2 computers connect to that directly via ethernet, and a third cat5e cable runs downstairs to connect the game consoles. There are two consoles however, and having to switch the cables out when you're couch-potatoed can be a task, so I set out to remedy this. The problem I had encountered was that the cat5e cable running downstairs came from a LAN port on the upstairs router, with an IP address handed out by the upstairs router's DHCP server. When the signal came downstairs, the WAN port on the bottom router recognized that specific IP address as its WAN, which would be incorrect. What followed was all devices being able to connect, but only one at a time; counter-intuitive to my goal. A phone call from Jason enlightened me, and I found out that by plugging in said cat5 cable to the downstairs router, it was given instructions to access the internet from the router, when it should be pushing through to the actual cable modem.
I plugged the cat5 cable instead into the downstairs router's LAN cable which made all the difference, as it was able to toggle the upstairs DHCP server, push through an IP address from the upstairs router downstairs, filtered by means of limiting the IP address range the downstairs router hands out as not to interfere with the upstairs router's IP address range field, and now...
everything works!
The problem now, is that the routers I am using are generic and have a limited amount of cache and memory, so there is an intermittent but temporary time-out of the network. Next paycheck? Industrial grade router/switch.
If you are wondering why routers can cost so much, applications like this are why.