Well logicially, it should work like this (I've done it this way several
times, with different routers.)
I guess you could try:
LAN1 ---Router1 ---- (DHCP on - set as 192.168.1.x, set to use a static
IP on the WAN side.)
|
Router3 --- (DHCP off - set as 192.168.0.x , set to use
Dynamic IP - but that's the way my ISP does it, if your's is different,
set it accordingly.
|
WAP2 ---Router2 ---- (DHCP on - set as 192.168.2.x, set to use a static IP
on the WAN side.)
This is how I have set it up on a STATIC route. In the Linksys BIOS setup I
disable DHCP on WAN 3 and tell it to use a static route, which I define....
there is a place to do this.
So WAN3 is told to only send to 192.168.1.1 and 192.168.1.2
LAN1 is told to use the static route of 192.168.1.3 for internet out
WAP2 is told to use the static route of 192.168.1.3 for internet out
Could it be a DHCP lease problem on router3? Could router 1 and 2 somehow
be grabbing the same IP on the WAN side?
not possible because WAP two is behind two hardware firewalls
Could there be a miswiring somewhere with a loop setup between the routers?
no, wiring is very simple on the test setup.
One CAT5e from WAN3 internet port to cable modem
One CAT5e from LAN1 internet port to WAN3 port one
One CAT5e from WAP2 internet port to WAN3 port three
It should work but it doesn't work.... and woarse it brings the routers
down when I try to make it work. That is why I am wondering if I should use
one of the open source BIOS flashes on the WAN2 router. That router because
that is the one the other two Linksys talk to. With a different BIOS the
two Linksys shouldn't have any connection to each other. ... just a thought.
Any body use one of the these open source BIOS flashes ... is it worth
doing? What are the odds of frying my router?
