Modify

Opened 2 years ago

Last modified 17 months ago

#20604 new defect

WDS link loses connectivity under network load

Reported by: tribut Owned by: developers
Priority: normal Milestone:
Component: kernel Version: Trunk
Keywords: wds Cc:

Description

I'm running OpenWRT 15.04 (r46767) on a TP-Link WDR-4300 and a TP-Link WDR-3600, connected via WDS.

                                            |-- Cable-Client 1
 Internet -- WDR4300 -(Wifi/WDS)- WDR3600 --|-- Cable-Client 2
                                            |-- Cable-Client 3

This works fine until one of the clients connected to the WDR3600 creates a significant load on the network (e.g. a large rsync-Job or a torrent). After a while (around 60 seconds), the WDS link completely dies (routers can't ping each other, can't connect to the internet from cable clients). The other wifi clients connected to the WDR4300 still have internet though and I can still connect to the WDR3600 from the cable clients. Typing wifi up on the WDR3600 restores connectivity.

Unfortunately, nothing is logged on either router when this happens. This is what I get on WDR3600 after I type wifi up:

Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1708.500000] wlan1: deauthenticating from 62:66:b3:8a:4c:38 by local choice (Reason: 3=DEAUTH_LEAVING)
Sat Sep 26 16:08:45 2015 daemon.notice netifd: Network device 'wlan1' link is down
Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1708.530000] br-lan: port 3(wlan1) entered disabled state
Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1708.580000] br-lan: port 3(wlan1) entered disabled state
Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1708.610000] device wlan1 left promiscuous mode
Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1708.610000] br-lan: port 3(wlan1) entered disabled state
Sat Sep 26 16:08:45 2015 kern.info kernel: [ 1709.230000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sat Sep 26 16:08:46 2015 daemon.notice netifd: radio1 (5433): Successfully initialized wpa_supplicant
Sat Sep 26 16:08:46 2015 kern.info kernel: [ 1709.770000] device wlan1 entered promiscuous mode
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.680000] wlan1: authenticate with 62:66:b3:8a:4c:38
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.690000] wlan1: send auth to 62:66:b3:8a:4c:38 (try 1/3)
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.700000] wlan1: authenticated
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.710000] wlan1: associate with 62:66:b3:8a:4c:38 (try 1/3)
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.710000] wlan1: RX AssocResp from 62:66:b3:8a:4c:38 (capab=0x11 status=0 aid=1)
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.720000] wlan1: associated
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.720000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Sat Sep 26 16:08:48 2015 daemon.notice netifd: Network device 'wlan1' link is up
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.760000] br-lan: port 2(wlan1) entered forwarding state
Sat Sep 26 16:08:48 2015 kern.info kernel: [ 1711.760000] br-lan: port 2(wlan1) entered forwarding state
Sat Sep 26 16:08:50 2015 kern.info kernel: [ 1713.760000] br-lan: port 2(wlan1) entered forwarding state

I even tried moving the WDS link to a separate SSID which is not used by normal clients, but this did not change the behavior.
What can I do to help debug this?

Attachments (0)

Change History (4)

comment:1 Changed 20 months ago by gonghuan98@…

Ham..
Seems this issue has been troubling us for a long time.
See : https://dev.openwrt.org/ticket/22075#no3
I even found similar issues reported 10 years ago.
See also: https://forum.openwrt.org/viewtopic.php?id=7790 and

https://forum.openwrt.org/viewtopic.php?id=45220

The owner of this ticket : jmomo described the same situation in detail.
You may get some useful information there.
Since few people use 4-address/wds function, and no official reply/solutions for a decade.
I have to find out the origin of this issue myself.
And I do have a suspicion that this happens when heavy load on the WDS Connection exists.

comment:2 Changed 19 months ago by hojuruku

Wow I had this problem too trying to do a wds wifi bridging setup 3 years ago.
Go straight to mesh. That's what it looks like.

comment:3 Changed 17 months ago by jmomo

tribut, can you please contact me? I would like to provide you with some scripts/info and find out if you are having the same problem that I reported in my ticket, or if this is a different issue. Mail me at jmomo@…

comment:4 Changed 17 months ago by jmomo

Make that jmomo at jmomo dot net

Last edited 17 months ago by jmomo (previous) (diff)

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.