TL-WR1043N/ND v1.6 WAN bridge to LAN broken

[dlogictech]

Hi,
I have found an issue when I am using the TP-Link TL-WR1043N/ND v1.6 with firmware 1.7.X (Built 20150604-0528 git@e7e4e5e) as a network switch.
The problem happens when the WAN port is disabled and then set the WAN Ethernet Port to "Bridge To LAN"

WAN Port Bridge to LAN.JPG

As soon as the settings are saved the 4 LAN ports act erratically and the only stable connection is the "WAN" port and the router is only accessible through this port to change the settings back. (short of resetting the router back to defaults).

[dlogictech]

Hi All,
Just wondering why the option for the "Wan Ethernet Port" option To "Bridge to Lan" has been removed.

I have tried 1.7.2 and the latest download from ispyisail
http://www.gargoyle-router.com/phpbb/vi ... =14&t=7317

Both of latest 2 releases has this option removed.

[nworbnhoj]

Just wondering why the option for the "Wan Ethernet Port" option To "Bridge to Lan" has been removed.

"Bridge to LAN" exists on my TL-WDR3600 running Gargoyle 1.7.2

Gargoyle - Connection - Basic - Internet/WAN - Wan Ethernet Port - Bridge to LAN

[dlogictech]

Just wondering why the option for the "Wan Ethernet Port" option To "Bridge to Lan" has been removed.

"Bridge to LAN" exists on my TL-WDR3600 running Gargoyle 1.7.2

Gargoyle - Connection - Basic - Internet/WAN - Wan Ethernet Port - Bridge to LAN

Unfortunately it does not show on my TP-Link TL-WR1043ND Ver. 1.6 using Gargoyle 1.7.X (Built 20150718.
See pic below:

Bridge to LAN.JPG

[apvm]

Just wondering why the option for the "Wan Ethernet Port" option To "Bridge to Lan" has been removed.

"Bridge to LAN" exists on my TL-WDR3600 running Gargoyle 1.7.2

Gargoyle - Connection - Basic - Internet/WAN - Wan Ethernet Port - Bridge to LAN

+1 "Bridge to LAN" exists on my 1043nd v1.7 running Gargoyle 1.7.2

If you are using your 10.43nd as a switch,I don't think firmware matters, try reverting it back to older firmware or even stock.

[dlogictech]

I did a factory reset and the option came back.
It seems to be related to me installing different versions of the Gargoyle firmware when testing for issues posted on this forum for troubleshooting issues.