WAN not working on TP-Link TL-WR1043ND

[Chilling_Silence]

Hi all,

So I've flashed a couple of these just fine. However, this one is having issues with the WAN port.
On standard firmware, it's fine, and I can go back to the standard TP-Link firmware, chopping / changing from Gargoyle <-> TP-Link firmware and every time the TP-Link firmware works.

Basically the WAN Port doesn't want to get an IP Address if set to DHCP, or if I statically assign it, it simply doesn't work. The WAN light never comes on.

Code: Select all

root@Gargoyle:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 90:f6:52:a4:db:b6 brd ff:ff:ff:ff:ff:ff
3: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 90:f6:52:a4:db:b6 brd ff:ff:ff:ff:ff:ff
4: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 90:f6:52:a4:db:b7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.253.209/24 brd 192.168.253.255 scope global eth0.2
7: imq0: <NOARP> mtu 16000 qdisc noop state DOWN qlen 11000
    link/void 
8: imq1: <NOARP> mtu 16000 qdisc noop state DOWN qlen 11000
    link/void 
9: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 90:f6:52:a4:db:b6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
10: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 32
    link/ether 90:f6:52:a4:db:b6 brd ff:ff:ff:ff:ff:ff
11: mon.wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 32
    link/ieee802.11/radiotap 90:f6:52:a4:db:b6 brd ff:ff:ff:ff:ff:ff

WAN is 192.168.253.209
LAN is 192.168.1.0/24

Code: Select all

root@Gargoyle:~# cat /proc/cpuinfo 
system type		: Atheros AR9132 rev 2
machine			: TP-LINK TL-WR1043ND
processor		: 0
cpu model		: MIPS 24Kc V7.4
BogoMIPS		: 266.24
wait instruction	: yes
microsecond timers	: yes
tlb_entries		: 16
extra interrupt vector	: yes
hardware watchpoint	: yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ff8, 0x0ffb]
ASEs implemented	: mips16
shadow register sets	: 1
core			: 0
VCED exceptions		: not available
VCEI exceptions		: not available

tplink_firmware.png (12.89 KiB) Viewed 20127 times

Now I've tried a couple of things I've found suggested. Basically I noticed the MAC on the TP-Link firmware was different so I tried forcing that to be the same as what it was in the stock firmware. Still no go.

Looks like there's a lot of similar issues out there:
http://www.gargoyle-router.com/phpbb/vi ... f=8&t=2408
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=701315
And there's quite a few more. Some threads are quite recent, some are not (There was some issue back around mid 2010 that openwrt sorted).

I also note here:
http://wiki.openwrt.org/toh/tp-link/tl- ... stallation

It appears that in order to use the "Firmware upgrade" option in the original firmware for installing OpenWRT, the WR1043ND must be connected to internet, or at least to a dhcp server on its WAN port - otherwise it won't flash the OpenWRT image, but come up with original firmware again after reboot. UPDATE: not a problem with hardware v1.8 running stock firmware 20110429: leaving connected back to back the Windows client PC performing the upgrade was good enough.

I've been flashing back and forth with wr1043nv1_en_3_13_12_up(120405).bin and gargoyle_1.5.5-ar71xx-tl-wr1043nd-v1-squashfs-factory.bin
It sounds like a similar issue. There's a DHCP server on the WAN Port but I can also statically assign it an IP Address. However, neither is working.

The results are the same, regardless of me using a static IP for the WAN or a DHCP IP for the WAN... It also behaves the same, regardless of there being anything plugged in to the LAN ports while it boots (and for 5 minutes following) or not.

As mentioned, I've done a few previously and even wrote a quick How-To on my blog about it for me to give out to friends and family. This one however seems to be a curly one. I'm open to suggestions.

Thanks


Chill.

[ispyisail]

quick How-To on my blog

where?

do you mind if I copy it?

[ispyisail]

Basically the WAN Port doesn't want to get an IP Address

Have you tried another DHCP server?

[Chilling_Silence]

Yes I've tried multiple WAN DHCP Servers. One was an AM300 in Halfbridge, another a Draytek DV120 (Not in halfbridge, just giving out 50 IPs and had only given out 1 of the pool of 50), a Linux DHCP server we use here at work....

The interesting part is the WAN light doesn't even seem to light up? I know that on my own the WLAN doesn't light up but the WAN light does.

Latest two posts here: http://www.c2s.co.nz/blog/

[whynotnowtoday]

any more on this i appear to have the same issue with this router : dead wlan

[Chilling_Silence]

No not dead WLAN, dead WAN... WiFi works fine for me.
However the WiFi light never turns on. It still works though

[ispyisail]

No not dead WLAN, dead WAN... WiFi works fine for me.
However the WiFi light never turns on. It still works though

how do you use the router without a WAN port?

[ispyisail]

what hardware version are you using?

Eric sells these routers, you would assume if the WAN port stopped working people would complain..........

[wetwilly]

I've been running Gargoyle on my 1043ND for a long while and not experienced much issues at all.

I would say it's broken hardware rather than something wrong with Gargoyle.

[Chilling_Silence]

I know, and the reason Eric sells them is the reason I went for it, because I presumed it'd be pretty reliable (And my own personal one is most certainly, and a few others I've setup for other mates). It's just this one in particular that doesn't wanna play nice.

I thought Hardware also, but that can't be the case if the standard firmware work just fine.
IIRC hardware rev 1.8 but I'll check when I get in to the office where the router is (I'm basically doing this for a workmate helping him get setup at his house with Gargoyle).

WiFi works because I can get to the Gargoyle WebUI through it, and another test machine that was hooked up via the LAN. It's *just* the WAN which doesn't work. But that's the point, it's basically useless, sitting there on our test bench doing bugger all coz he can't really take it home without a WAN port working :p