Gargoyle Forum

I would like to report a bug on the TP-Link TL-WR1043ND Ver. 1.6

The LAN Port 4 does not work with any of the 1.7.x releases

I have tested all versions of 1.7.x with only the default setup and only version 1.6.2 has all the LAN ports working.

Can you post back your network config file?


cat /etc/config/network

Lantis wrote:Can you post back your network config file?


cat /etc/config/network

Hi Lantis,
Here is the contents of the file:

root@Gargoyle:~# cat /etc/config/network

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd73:43b7:f41e::/48'

config interface 'lan'
option ifname 'eth0.1'
option force_link '1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'

config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'

config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option ports '1 2 3 4 5t'

config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0 5t'

root@Gargoyle:~#

If that is from 1.7.X then I see no reason it shouldn't be working.

How exactly are you testing?

I install the latest firmware
when the router has booted up, I connect an ethernet cable to ports 1 to 4 one at a time and look at the LED light as well as ping the router.

In all cases I get a reply and the LED's light up except port 4

Here is the network contents for 1.6.2:
root@Gargoyle:~# cat /etc/config/network

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config interface 'lan'
option ifname 'eth0.1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'

config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'

config switch
option name 'rtl8366rb'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'rtl8366rb'
option vlan '1'
option ports '1 2 3 4 5t'

config switch_vlan
option device 'rtl8366rb'
option vlan '2'
option ports '0 5t'

root@Gargoyle:~#

except port 4

bad Ethernet lead?

ispyisail wrote:

except port 4

bad Ethernet lead?

No, I made sure to use the same known good cable on each port.

I first tested port with 1 single ethernet cable , watched for the LED to light up and performed a ping test on the router.

Then I removed the cable from port 1 and plugged it into port 2 and did the same test above.

I did this procedure for all 4 ports and the only one that does not work is port 4.

I even re-did the above test with a different cable to make sure that somehow the cable was not defective as you say, but the same results.
There has to be something affecting port 4 on version 1.7.x release because it does indeed work when I flash the firmware back to version 1.6.2

Hello All,

I found out that this issue with the LAN Port # 4 not working is caused by OpenWrt.
I just flashed my TP-Link TL-WR1043ND HW v1.10 with OpenWRT Barrier Breaker and the LAN port # 4 also does not work. So I proceeded to downgrade to OpenWRT Attitude Adjustment and LAN Port # 4 works.
Please stand by... I am testing further as I have noticed some anomalies...

My next question: Is there a formal way to report this through the Gargoyle Team back to OpenWRT Team? Or do I need to report this to the OpenWRT team myself?

Or do I need to report this to the OpenWRT team myself?

yes

I has been suggested that mentioning gargoyle may have a negative effect at openwrt?

Status Update:
Well it seems after extensive testing with many different Gargoyle and OpenWRT releases I have finally found that all releases based on OpenWRT for this specific router has a bug.
It would seem that the only release of firmware for the WR-TL1043ND H/W v1.6 that works consistently on LAN port 4 is the original factory firmware.
My test results are shown below:
(in all my testing, the option to keep the configuration was not enabled, meaning factory defaults was always used)

Success results are below:
-
Original TP-Link
Firmware Version:
3.13.15 Build 140319 Rel.41339n
Hardware Version:
WR1043ND v1 00000000

Able to ping all 4 ports and all LED's light up.
*
Failed results are below:
-
Hostname OpenWrt
Model TP-Link TL-WR1043N/ND v1
Firmware Version OpenWrt Chaos Calmer 15.05-rc3 / LuCI Master (git-15.167.71950-8005ecb)
Kernel Version 3.18.17

Not able to ping while connected to port 4 and LED does not light up.
-
Hostname OpenWrt
Model TP-Link TL-WR1043N/ND v1
Firmware Version OpenWrt Barrier Breaker 14.07 / LuCI Trunk (0.12+svn-r10530)
Kernel Version 3.10.49

Not able to ping while connected to port 4 and LED does not light up.
-

Router Name OpenWrt
Router Model TP-Link TL-WR1043N/ND v1
Firmware Version OpenWrt Attitude Adjustment 12.09 / LuCI 0.11.1 Release (0.11.1)
Kernel Version 3.3.8

(In this release, the LAN port works only when all ethernet connections are removed the router is physically powered off for at least 20 seconds and then powered back on)
Intermittently the LED will light up after approximately 40 to 50 seconds and replies are received from pings. Note: I have sometimes had to wait for more than 2 minutes before the LED lights up and pings are responded to.
If the ethernet cable is removed and then plugged back into port 4, the LED never comes back and does not reply to pings.
-
Router Name OpenWrt
Router Model TP-LINK TL-WR1043ND
Firmware Version OpenWrt Backfire 10.03.1 / LuCI 0.10.0 Release (0.10.0)
Kernel Version 2.6.32.27

See the same results from Attitude Adjustment release above.
-
OpenWrt Backfire 10.03
Load: 0.00 0.01 0.00
Hostname: OpenWrt

See the same results from Attitude Adjustment release above.


It would seem that I need to report this to the OpenWRT Team and (not mention Gargoyle)