Dotted lines indicate wireless connections, solid lines indicate Ethernet connections.
I used two ASUS routers and Tomato (Tomato Firmware 1.28.0000 MIPSR2-101 K26 USB Mega-VPN) to bridge my network. So I have two wired segments and a wireless network provided by the main router connected to my cable modem.
Everything seemed to be fine when I set up the bridge last week.
The main .1 router is set up for DHCP and virtually everything is DHCP with reservations by MAC address. The bridge has .2 assigned to it's LAN and it is set in wireless bridge mode. The .2 router is set in bridged mode and connects wirelessly to .1, providing connectivity for all the devices on its Ethernet ports.
But what I'm seeing today is that Pogoplug 2 (.195) cannot seem to get to the Internet.
It cannot ping 192.168.1.1.
It can ping .2 (it's bridge), .199 (wireless Mac), .197 (wired), .196 (wired) etc.
I am connected from .199 to .195 via SSH.
If I use Tomato's tools on the bridge, it can ping .1, 126.96.36.199 etc, so it seems to be fine.
What am I missing here? Seems like something simple.
[root@alarm ~]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.195 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::225:31ff:fe05:38bc prefixlen 64 scopeid 0x20<link> ether 00:25:31:05:38:bc txqueuelen 1000 (Ethernet) RX packets 169 bytes 20660 (20.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 89 bytes 11323 (11.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 11 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 4 bytes 260 (260.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 260 (260.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
A PC on the bridged part is fine - pings 192.168.1.1
So there is something about the Pogoplug and the bridge. Moving it to the other router, it keeps its IP address and is able to connect out and see the bridged network just fine - it can ping the PC on the other segment and the .2 interface. If I don't get any ideas here, I guess I'll take it up on the ArchLinux of ArchLinux ARM boards.