<snip>
And that's where strange things happen. While it appears to be working
fine, I cannot get into its admin page with Firefox. The ifconfig
command now returns:
eth0 Link encap:Ethernet HWaddr 00:90:f5:ef:f2:59
inet6 addr: fe80::290:f5ff:feef:f259/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:224 errors:0 dropped:12 overruns:0 frame:0
TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:48950 (48.9 KB) TX bytes:12754 (12.7 KB)
eth1 Link encap:Ethernet HWaddr 00:23:54:8c:65:20
inet addr:192.168.0.126 Bcast:192.168.0.255
Mask:255.255.255.0 inet6 addr: fe80::223:54ff:fe8c:6520/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:55497133 errors:0 dropped:0 overruns:0 frame:0
TX packets:74416205 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8725814863 (8.7 GB) TX bytes:65815244794 (65.8 GB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:788901 errors:0 dropped:0 overruns:0 frame:0
TX packets:788901 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:70046669 (70.0 MB) TX bytes:70046669 (70.0 MB)
wlan0 Link encap:Ethernet HWaddr 00:c2:c6:00:1e:1e
inet addr:192.168.0.147 Bcast:192.168.0.255
Mask:255.255.255.0 inet6 addr: fe80::2c2:c6ff:fe00:1e1e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37562 errors:0 dropped:2 overruns:0 frame:0
TX packets:11214 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2950545 (2.9 MB) TX bytes:1381951 (1.3 MB)
It seems counter-intuitive but what you have is an asymmetric routing
problem. Packets are going out to the linksys on 1 interface and coming
back in on the other and the 2 interfaces don't exchange packets between
themselves on the Linux box unless you configure policy routing.
To test this just try pinging the management ip addr of the linksys first
with both the eth1 and wlan0 up and then unlpug the ethernet cable from
eth1.
If you successfully ping the linksys mngmt ip addr over the wifi net then
you should be able to login to the admin page and make the necessary
changes.
Here's a link to the policy routing and an example of what it looks like if
that's something that interests you in the future.
http://pontus.ullgren.com/view/multiple_interfaces_on_the_same_subnet
______________________________________________________________________________
uto eth2
iface eth2 inet static
address 192.168.1.20
network 1192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
up ip route add 192.168.1.0/24 dev eth2 proto kernel scope link src
192.168.61.20 table 20
up ip route add default via 192.168.1.1 dev eth2 table 20
up ip rule add from 192.168.1.20 lookup 20
auto eth3
iface eth3 inet static
address 192.168.1.21
network 1192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
up ip route add 192.168.1.0/24 dev eth3 proto kernel scope link src
192.168.61.21 table 30
up ip route add default via 192.168.1.1 dev eth3 table 30
up ip rule add from 192.168.1.21 lookup 30
_____________________________________________________________________________________________________________
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
