Modify

Opened 20 months ago

Last modified 20 months ago

#22538 new defect

TP-Link TL-WR841ND: WAN-Port gets stuck on congested network

Reported by: Camu Owned by: developers
Priority: normal Milestone:
Component: kernel Version: Chaos Calmer 15.05
Keywords: ag71xx TP-LINK TL-WR841ND Cc:

Description

When the network on the WAN-Port of the TP-Link TL-WR841ND gets congested, the NIC stops receiving packages. The LED also doesn't blink any more. Resetting the link (eg. by replugging) the port returns to normal operation. It seems, the port gets stuck as soon as a collision occurs. The collision counter displayed by ifconfig stays at zero.

dmesg output:

[ 8036.320000] eth1: link up (100Mbps/Half duplex)
[ 8036.320000] br-vpnonly: port 1(eth1.1) entered forwarding state
[ 8036.330000] br-vpnonly: port 1(eth1.1) entered forwarding state
[ 8036.340000] br-guest: port 1(eth1.2) entered forwarding state
[ 8036.340000] br-guest: port 1(eth1.2) entered forwarding state
[ 8038.330000] br-vpnonly: port 1(eth1.1) entered forwarding state
[ 8038.340000] br-guest: port 1(eth1.2) entered forwarding state

ifconfig output:

eth1      Link encap:Ethernet  HWaddr F4:F2:6D:**:**:**
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13722 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17481 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:9887920 (9.4 MiB)  TX bytes:2509673 (2.3 MiB)
          Interrupt:4

Attachments (0)

Change History (1)

comment:1 Changed 20 months ago by Camu

I found out, that problem only occurs when connected to a specific NIC. Using a hub to connect the WAN port to my router instead of a direct connection resolved the problem. But the collision-counter still stays at zero although the collision LED on the hub blinks.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.