Hello, this is my first post here as a new owner of the RT-N66U. Maybe this question has been answered before but I looked through many threads in this forum before asking without a definitive answer.
I am trying to see the config page of my Linksys WAG200G that has been flashed with openwag and used only as a modem (Modem only option) so DHCP automatically disabled. The RT-N66U is used as a router and the PPPoE connection is done with it. My setup is as follows:
WAG200G (modem) IP: 192.168.0.1 - Subnet mask: 255.255.255.0
RT-N66U IP: 192.168.1.1 - Subnet mask: 255.255.255.0
The two devices are only connected with a Cat5e from LAN port of WAG200G to WAN port of RT-N66U. Is there any way to access the config page of WAG200G? When trying from a computer connected to the asus router I get connection timed out. Maybe there is a routing scheme I can enter in the LAN - Route page of the RT-N66?
Note: I tried connecting a 2nd ethernet cable from a LAN port of RT-N66U to a LAN port of WAG200G and managed to access it (by first giving an IP 192.168.1.254) but this method proved strange as it kept creating strange messages in the log i.e. "kernel: vlan1: received packet with own address as source address" every 2-3 seconds or so.
I am trying to see the config page of my Linksys WAG200G that has been flashed with openwag and used only as a modem (Modem only option) so DHCP automatically disabled. The RT-N66U is used as a router and the PPPoE connection is done with it. My setup is as follows:
WAG200G (modem) IP: 192.168.0.1 - Subnet mask: 255.255.255.0
RT-N66U IP: 192.168.1.1 - Subnet mask: 255.255.255.0
The two devices are only connected with a Cat5e from LAN port of WAG200G to WAN port of RT-N66U. Is there any way to access the config page of WAG200G? When trying from a computer connected to the asus router I get connection timed out. Maybe there is a routing scheme I can enter in the LAN - Route page of the RT-N66?
Note: I tried connecting a 2nd ethernet cable from a LAN port of RT-N66U to a LAN port of WAG200G and managed to access it (by first giving an IP 192.168.1.254) but this method proved strange as it kept creating strange messages in the log i.e. "kernel: vlan1: received packet with own address as source address" every 2-3 seconds or so.