Page 1 of 1

WAN port not working on WR1043ND

Posted: Fri Jan 04, 2013 3:34 pm
by esgudnason
I've upgraded 4 identical TP-link WR1043ND using gargoyle_1.4.7-ar71xx-tl-wr1043nd-v1-squashfs-factory.bin.

All but one is working properly as it does not active the WAN port either by using DHCP (Wired) or providing Static IP (Wired). The "Renew Lease Now" is greyed out when using DCHP and no green light is active on the WAN port on the front of the router.

I backed to original TP-link software using the provided firmware on Gargoyle (wr1043nv1_en_3_9_17-sysupgrade.bin) and then upgraded to the lastest firmware from TP-link (wr1043nv1_en_3_13_12_up_boot(120405).bin).

Using the TP-link firmware the DCHP on WAN works immediately.

Now upgrading the router back to Gargoyle using the sem firmware gargoyle_1.4.7-ar71xx-tl-wr1043nd-v1-squashfs-factory.bin and even using "Restore Default configuration Now" the router is back to the state where WAN port is no longer functional :?

Any ideas what is causing this behavior and ideally how to resolve this?

Thanks!

Re: WAN port not working on WR1043ND

Posted: Sat Jan 05, 2013 2:11 pm
by esgudnason
I tried to upgrade to 1.5.9 and now the WAN port is working using Gargoyle.

This is however not the best solution as I would like to use stable version and not experimental.

Any ideas would be greatly appreciated how to resolve this using version 1.4.7. :)

Re: WAN port not working on WR1043ND

Posted: Sun Jan 06, 2013 1:11 am
by ericwong
esgudnason wrote:I tried to upgrade to 1.5.9 and now the WAN port is working using Gargoyle.

This is however not the best solution as I would like to use stable version and not experimental.

Any ideas would be greatly appreciated how to resolve this using version 1.4.7. :)
The experimental branch is not as bad as you think...
The latest firmware 1.5.8+ is already using RC release of Openwrt

Re: WAN port not working on WR1043ND

Posted: Wed Jan 09, 2013 6:19 pm
by esgudnason
Thanks Eric for your comment.

I've been running 1.5.8 for 4 days and it's been running fine, so no problems so far.

As you point out, 1.5.x seems close to being the next stable version its not worth the trouble to try to fix this issue on 1.4.7.