#22228: WDS sta Disconnect Unable to Reconnect UNLESS ap reboot
---------------------------------+---------------------------------------
  Reporter:  openwrt.org-2012@…  |      Owner:  developers
      Type:  defect              |     Status:  new
  Priority:  normal              |  Milestone:  Designated Driver (Trunk)
 Component:  packages            |    Version:  Trunk
Resolution:                      |   Keywords:
---------------------------------+---------------------------------------

Comment (by pkgadd):

 I'm observing the same issue with a TP-Link TL-WDR4300 v1 as WDS-AP and an
 old TP-Link TL-WR941ND v1 as WDS-STA, to provide a connection to a single
 wired client (IPv4 and IPv6) over 2.4 GHz WLAN. At first, the WDS-STA
 device
 (TL-WR941ND v1) connects fine to the WDS-AP (TL-WDR4300 v1), but after a
 while (ranging from a few minutes to 3-4 days) the connection stops
 responding and both the TL-WR941ND v1 and the wired client behind it
 timing
 out. Rebooting the WDS-STA usually doesn't recover the connection, while
 rebooting the WDS-AP always helps (at least for a while). The WDS link
 goes through several interior walls and a floor, which means it's rather
 weak and has to suffer intermittent interference.

 Given that the TL-WR941ND v1 is only powered on ~twice in three weeks on
 average, for a couple of hours each, I can't be 100% sure when exactly
 the problems started, but I'm rather confident about this timeframe.

 Last known good version:
 unmodified OpenWrt trunk snapshots from late last year (on both devices),
 I'm pretty sure that trunk r48185 was running fine, as I've been running
 that revision for quite a while, without remembering any of these issues.

 First known bad version:
 It started rather early this year, while I have unfortunately already
 deleted intermediate snapshot builds, trunk r49065 is definately affected.

 My current working theory, unconfirmed(!), is a potential regression
 between
 hostapd v2.3 (2015-03-25 plus security fixes) and 2016-01-15. The WDS-AP
 (TL-WDR4300 v1) has the full wpad package installed, while the WDS-STA
 (TL-WR941ND v1) only uses wpad-mini, due to its limited flash size.

 In order to debug this further, I've first built a trunk r49166 snapshot
 for
 the TL-WR941ND v1 with package/network/services/hostapd/* reverted to the
 state of r48345. This didn't improve the situation and I triggered the
 issue
 within 1-2 hours.

 My second approach was basically doing the same for the TL-WDR4300, namely
 injecting a r48345 /usr/sbin/wpad into the known-broken r49065 firmware
 via
 overlayfs. With this change, the WDS connection has been up without
 problems
 for 23 hours so far, but it is too early to be 100% sure about this
 observation yet (as it may still trigger within the next 3-4 days). At the
 moment both devices are (still successfully) running wpad{,-mini}
 2015-03-25-2 (package/network/services/hostapd/* reverted to r48345).

 Network topology:
 {{{
 +--------------------------------------------------------------------------+
 |                                 TL-WDR4300
 |
 +----------------------------------------------+---------------+-----------+
 |                    2.4  GHz                  |     5  GHz    |   wired
 |
 |                     WDS-AP                   |    plain AP   |  switch
 |
 +----------------------------------------------+---------------+-----------+
          |                |            |               |             |
 +-----------------+  +---------+  +---------+     +---------+        |
 |  TL-WR941ND v1  |  |  plain  |  |  plain  |     |  plain  |       /
 | 2.4 GHz WDS-STA |  |   STA   |  |  STA(s) |     |  STA(s) |      |
 |    no AP i/f    |  | 2.4 GHz |  | 2.4 GHz |     |  5 GHz  |      /
 +-----------------+  +---------+  +---------+     +---------+     |
          |                                                        |
 +-----------------+
 +-----------------+
 |  wired client   |                                      | wired client(s)
 |
 +-----------------+
 +-----------------+
 }}}

 TP-Link TL-WDR4300 v1, /etc/config/wireless:
 {{{
 config wifi-device 'radio0'
         option type 'mac80211'
         option hwmode '11g'
         option path 'platform/ar934x_wmac'
         option country 'DE'
         option htmode 'HT20'
         option txpower '20'
         option channel '13'

 config wifi-iface
         option device 'radio0'
         option network 'lan'
         option mode 'ap'
         option ssid 'XXX-2'
         option encryption 'psk2+ccmp'
         option key 'ZZZ'
         option wds '1'

 config wifi-device 'radio1'
         option type 'mac80211'
         option hwmode '11a'
         option path 'pci0000:00/0000:00:00.0'
         option country 'DE'
         option htmode 'HT40'
         option txpower '17'
         option channel '36'

 config wifi-iface
         option device 'radio1'
         option network 'lan'
         option mode 'ap'
         option ssid 'XXX-5'
         option encryption 'psk2+ccmp'
         option key 'ZZZ'
 }}}

 TP-Link TL-WR941ND v1, /etc/config/wireless:
 {{{
 config wifi-device 'radio0'
         option type 'mac80211'
         option hwmode '11g'
         option path 'platform/ath9k'
         option country 'DE'
         option htmode 'HT20'
         option txpower '20'
         option channel '13'

 config wifi-iface
         option device 'radio0'
         option network 'lan'
         option mode 'sta'
         option ssid 'XXX-2'
         option encryption 'psk2+ccmp'
         option key 'YYY'
         option wds '1'
 }}}

 TP-Link TL-WR941ND v1, /etc/config/network,
 the WAN port is not connected,
 one wired client is connected to a LAN port:
 {{{
 config interface 'loopback'
         option ifname 'lo'
         option proto 'static'
         option ipaddr '127.0.0.1'
         option netmask '255.0.0.0'

 config interface 'eth'
         option ifname 'eth0'
         option proto 'none'

 config interface 'lan'
         option ifname 'lan1 lan2 lan3 lan4'
         option force_link '1'
         option type 'bridge'
         option proto 'dhcp'

 config interface 'wan'
         option ifname 'wan'
         option proto 'dhcp'

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

--
Ticket URL: <https://dev.openwrt.org/ticket/22228#comment:2>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to