TP-Link -1043ND - No access to internet from wired lan hosts

[red6]

Installed latest stable build. (Jan 30/2012)

Gargoyle version 1.4.6 | OpenWrt backfire branch
Gargoyle revision 06f88cb | OpenWrt revision r29961
Built January 30, 2012 | Target ar71xx/ath9k_usb

Wireless access gets me to the internet. Speed is very good. 30mbit/sec to a speedtest site.

Wired access (into 1 of the 4 lan ports) won't allow me any access.
But if I putty on to the router I can ping an internet host. I can also resolve names do DNS is working.

Hopefully this might help:
Gargoyle version 1.4.6 | OpenWrt backfire branch
Gargoyle revision 06f88cb | OpenWrt revision r29961
Built January 30, 2012 | Target ar71xx/ath9k_usb

root@tplink:~# ifconfig
br-lan Link encap:Ethernet HWaddr F8:D1:11:2F:0D:86
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:379 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:89565 (87.4 KiB) TX bytes:11170 (10.9 KiB)

eth0 Link encap:Ethernet HWaddr F8:D1:11:2F:0D:86
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:114 errors:0 dropped:0 overruns:0 frame:0
TX packets:429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21579 (21.0 KiB) TX bytes:104606 (102.1 KiB)
Interrupt:4

eth0.1 Link encap:Ethernet HWaddr F8:D1:11:2F:0D:86
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:320 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:87732 (85.6 KiB)

eth0.2 Link encap:Ethernet HWaddr 54:04:A6:1A:D2:42
inet addr:174.113.xxx.yyy Bcast:255.255.255.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1400 Metric:1
RX packets:109 errors:0 dropped:0 overruns:0 frame:0
TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18888 (18.4 KiB) TX bytes:15831 (15.4 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

mon.wlan0 Link encap:UNSPEC HWaddr F8-D1-11-2F-0D-86-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7199 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:1122644 (1.0 MiB) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr F8:D1:11:2F:0D:86
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:378 errors:0 dropped:0 overruns:0 frame:0
TX packets:382 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:94851 (92.6 KiB) TX bytes:104202 (101.7 KiB)

root@tplink:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan
174.mmm.nnn.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0.2
0.0.0.0 174.mmm.nnn.1 0.0.0.0 UG 0 0 0 eth0.2
root@tplink:~#

Any help would be greatly appreciated.

red6

[ispyisail]

can you show us a screen shot of your summary page?

[red6]

Can't capture a summary page today as I decided to try my own build of openwrt.

Much latest hunch is that the switch configuration on my TP-Link is not working. Evan a 'stable' build of openwrt from the backfire rc6 repository does the same thing.

[pmerrill]

I too have no Internet access. Dropped out sometime overnight and now I cannot get the router to connect. I've rebooted and power cycled many times. The router does not want to get an IP address from the modem.

What's the approach to debugging this problem? Perhaps go back to the previous version (1.4.6)?

[pmerrill]

Solved! Amazingly, it turned out to be the CAT5 cable from my router to my modem. For some reason it went bad overnight!!! I flashed from 1.4.7 to 1.4.6 and then back to 1.4.7, was about to try stock firmware and thought, what the hell, I'll switch the cable. Boom, worked immediately. Needless to say, the cable has paid for this poor performance with its life!!!