Dumb AP with linksys e8450 / Belkin RT3200 occasionaly client associates but no connectivity

Installing and Using OpenWrt Network and Wireless Configuration
1

I have flashed with two e8450 / Belkin RT3200 with openwrt snapshots build (now i am on OpenWrt SNAPSHOT r18777-1847382456). I mainly followed the dump ap guide https://openwrt.org/docs/guide-user/network/wifi/dumbap.

I configured the both wlan interfaces on both routers with the same ssid and wpa_passphrase on both routers. The only difference is that the second router is on different channels. I have tried to setup 802.11r but soon I understand that I have more basic issues and I disabled it.

The config of one of the two routers.

/tmp/run/hostapd-phy0.conf

driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=GR
ieee80211d=1
hw_mode=g
supported_rates=60 90 120 180 240 360 480 540
basic_rates=60 120 240
beacon_int=100
dtim_period=2
channel=1
chanlist=1


ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1]

radio_config_id=54ba586e11d48387a54cee6ef906d55f
interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
skip_inactivity_poll=0
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
sae_require_mfp=1
wpa_passphrase=testestest
wpa_psk_file=/var/run/hostapd-wlan0.psk
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=testap
bridge=br-lan
wds_bridge=
snoop_iface=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256 SAE
okc=1
ieee80211w=1
group_mgmt_cipher=AES-128-CMAC
dynamic_vlan=0
vlan_naming=1
vlan_no_bridge=1
vlan_file=/var/run/hostapd-wlan0.vlan
qos_map_set=0,0,2,16,1,1,255,255,18,22,24,38,40,40,44,46,48,56
config_id=d613163329751f9bd0939d0d0d2fe9a8
bssid=c4:41:1e:f8:9b:cc"

/tmp/run/hostapd-phy1.conf

driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=GR
ieee80211d=1
ieee80211h=1
hw_mode=a
beacon_int=100
dtim_period=2
channel=36
chanlist=36

tx_queue_data2_burst=2.0
ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935]
ieee80211ac=1
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][VHT160-80PLUS80][MAX-MPDU-7991][MAX-A-MPDU-LEN-EXP7]
ieee80211ax=1
he_oper_chwidth=1
he_oper_centr_freq_seg0_idx=42
he_default_pe_duration=4
he_rts_threshold=1023
he_mu_edca_qos_info_param_count=0
he_mu_edca_qos_info_q_ack=0
he_mu_edca_qos_info_queue_request=0
he_mu_edca_qos_info_txop_request=0
he_mu_edca_ac_be_aifsn=8
he_mu_edca_ac_be_aci=0
he_mu_edca_ac_be_ecwmin=9
he_mu_edca_ac_be_ecwmax=10
he_mu_edca_ac_be_timer=255
he_mu_edca_ac_bk_aifsn=15
he_mu_edca_ac_bk_aci=1
he_mu_edca_ac_bk_ecwmin=9
he_mu_edca_ac_bk_ecwmax=10
he_mu_edca_ac_bk_timer=255
he_mu_edca_ac_vi_ecwmin=5
he_mu_edca_ac_vi_ecwmax=7
he_mu_edca_ac_vi_aifsn=5
he_mu_edca_ac_vi_aci=2
he_mu_edca_ac_vi_timer=255
he_mu_edca_ac_vo_aifsn=5
he_mu_edca_ac_vo_aci=3
he_mu_edca_ac_vo_ecwmin=5
he_mu_edca_ac_vo_ecwmax=7
he_mu_edca_ac_vo_timer=255

radio_config_id=cd75326b1bc35164c7b572835c7f897b
interface=wlan1
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
skip_inactivity_poll=0
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
sae_require_mfp=1
wpa_passphrase=testestest
wpa_psk_file=/var/run/hostapd-wlan1.psk
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=testap
bridge=br-lan
wds_bridge=
snoop_iface=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256 SAE
okc=1
ieee80211w=1
group_mgmt_cipher=AES-128-CMAC
dynamic_vlan=0
vlan_naming=1
vlan_no_bridge=1
vlan_file=/var/run/hostapd-wlan1.vlan
qos_map_set=0,0,2,16,1,1,255,255,18,22,24,38,40,40,44,46,48,56
config_id=6abb50d9a7ebe5c1105f63218f35dda8
bssid=c4:41:1e:f8:9b:cd

/etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/18000000.wmac'
        option channel '1'
        option band '2g'
        option cell_density '0'
        option htmode 'HT40'
        option country 'GR'

config wifi-device 'radio1'
        option type 'mac80211'
        option path '1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
        option channel '36'
        option band '5g'
        option htmode 'HE80'
        option cell_density '0'
        option country 'GR'

config wifi-iface 'wifinet1'
        option device 'radio1'
        option mode 'ap'
        option encryption 'sae-mixed'
        option key 'testest'
        option network 'lan'
        option ssid 'testap'

config wifi-iface 'wifinet2'
        option device 'radio0'
        option mode 'ap'
        option encryption 'sae-mixed'
        option key 'testest'
        option network 'lan'
        option ssid 'testap'

/etc/config/network

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

config globals 'globals'
        option ula_prefix 'fdbd:e7de:18b0::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'
        #option igmp_snooping '1'
        #option query_interval '3000'
        #option igmpversion '3'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.2.5'
        option gateway '192.168.2.1'
        list dns '1.1.1.1'
        list dns '8.8.8.8

After reboot everything is working hanky dory.
But if I move around and my android phone deassociates and re associates a phew times then the issues start.
The 4way-handshake completes but the WiFi device has no connectivity at all, i happens on any android phone (i tested with Galaxy S8 and S9) and an ipad air.

Wed Feb 23 10:54:57 2022 daemon.info hostapd: wlan0: STA 26:63:6b:73:05:44 RADIUS: starting accounting session D0BA3451AAC51851
Wed Feb 23 10:54:57 2022 daemon.info hostapd: wlan0: STA 26:63:6b:73:05:44 WPA: pairwise key handshake completed (RSN)
Wed Feb 23 10:54:57 2022 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 26:63:6b:73:05:44

I have disabled firewall, dnsmasq, odhcpd and igmproxy

If I reboot the router everything again is hanky dory for a while, then the issue starts again.
The issue is driving me mad and I don't know where to start the debugging.

2

Only ever setup a dumb AP (ie no fast roaming). Someone else might spot an error in your config.

I believe onemarcfifty walks through configuration of fast roaming in one of his earlier videos. Link to a more recent one in which I think he might reference the one to which I refer:

3

Thank you i will check it, but I am afraid that there is a underlying issue either with hostapd or with the hardware driver for the MT7622BV , MT7915E.

4

I assume you've updated/replaced hostapd ?

can't see any existance of the params below, in your config.

option ieee80211r "1"
option mobility_domain "xxxx"
option pmk_r1_push "1"

should look something like this

image
image556×777 16 KB

6

I disabled 802.11r for the moment to debug these issue first.

7

Hey there.

I updated a couple of Dumb APs around the house last weekend.
Three of them are TP-Link 4900, one is a TP-Link 4300, one is a TP-Link 1034 and one is a Belkin RT3200.
So not completely your setup (since you have two RT3200), but I guess your problems are related to mine.

  • I installed latest stable 21.02.1 on all TP-Link
  • I installed snapshot r18621 on the Belkin (that was actually a couple of days ago)

Seems like there's an issue with combining 802.11r (fast transition) with 802.11.w (management frame) and WPA3.

  • When I used all of those, no FT was happening.
  • When I used 802.11r with WPA3 but without 802.11w, FT was working just fine but my Macbook wouldn't connect at all.
  • When I used 802.11r with WPA2 and 802.11w, FT was not working but all devices connected at least at some point.
  • When I used 802.11w with WPA3 but without 802.11r, all devices at least connected

I ended up setting encryption to WPA2 ("psk-mixed"), ticking the 802.11r box to checked (ieee80211r 1) and disabling 802.11w (ieee80211w 0).

Seems like if I switch from WPA2 to WPA3, the ieee80211w goes from 0 to 1 (disabled to optional) by default, if I switch from WPA3 to WPA2, the ieee80211w goes from 1 to 0. So I guess there's actually a different default value per encryption setting.

  • I didn't need to update/replace package, neither hostapd nor wpad.
  • I didn't need to set the mobility domain since it's derived from the SSID automatically and just works. The input shows a placeholder value, and this placeholder value is identical amongst all devices with the same SSID but different amongst different SSIDs even on the same device.
  • I didn't need to set the NAS ID. The input is just empty.
  • I didn't need to enable the R1 Push. The checkbox is just not ticked.
  • I didn't change the FT protocol but left it to "FT over DS". That's fine since all my dumb APs share a common LAN interface with interface type static and IP addresses on the same subnet.

As for the wireless connections, I just create a new wireless connection, set encryption to WPA2, enable the 802.11r checkbox and assign that connection to an interface. Done.

This setup just works on all of my TP-Link devices as well on my Belkin device.

The WPA2 setting is the thing I immediately spot in the screenshot @frollic posted and what you, @nkef, state as being set to WPA3 ("encryption sae-mixed").

I guess the actual issue is 802.11w being not compatible with 802.11r at the moment and the WPA3 thing is just what triggers the 802.11w to change on one hand and what seems to be not implemented properly on my Macbook.

Regards,
Stephan.

8

never mind, the answers get wrong, if you don't read the whole post :slight_smile:

9

@golialive thank you for your info.
Now you mentioned I was reading too that there issues with 802.11w alongside with 802.11r so for a period I had enabled the 802.11r with 802.11w disabled but I was experiencing a similar issue.
So I gave up on 802.11r and tried to test the dump ap with 802.11w set to optional and encryption set to WPA2-PS/WPA3-SAE Mixed Mode and I have the same issue of clients successfully perform the 4way handshake but with no connectivity.

I will set encryption to WPA2-PSK with 802.11w and 802.11r disabled to check if the no connectivity issue persists.

Regarding my 802.11r tests,

  • I had specified a NAS ID in my setup,
  • Generate PMK locally
  • FT over DS my access points are also connected through Ethernet on the same lan with static IP
  • I had specified the 4-character hexadecimal ID for the mobility domain.
  • I had not enabled R1 Push

FT kinda worked buy I was getting "key addition failed" in the logs which is another can of worms with no definitive answer why that happens, a lot forum threads can be found around that issue.

In your setup, is band steering is working since your routers have 2.4 and 5 GHz bands?

Thanks,
nkef

10

I get the "key addition failed" log line as well, but FT works just nicely. I can even put an Android device right in the middle of two APs, click alternating "Disconnect" buttons on both OpenWRT APs and observe the Android device toggle-switch between them -- without loosing a ping.

The thing with setting NAS ID and Mobility Domain is: It's easy to do wrong. Misstype the Mobility Domain or fail on user generated randomness for NAS ID and things don't work. I even don't know if things go crazy if two different SSIDs just by accident use the same Mobility Domain. There's a chance this gives error you won't be able to search for.
So I decided there's not much benefit in doing it manually as it is supposed to work with defaults anyway.

The "Generate PMK locally" is enabled an all of my hosts.

I didn't do anything crazy in terms of band steering. I reduced 2.4GHz to 12dBm, set "Distance Optimization" to 5 meters and "Beacon Interval" to 300. That pushes most of my devices to prefer 5GHz over 2.4GHz, but it doesn't completely prevent 5GHz capable devices from sometimes entering the 2.4GHz net.
I honestly don't care too much. The one thing I wanted to have is being able to wander around my home with MS Teams call not disconnecting for a couple of seconds.

11

I have the same setup, Linksys e8450 set as dump ap & tp-link archer c7 v5 as the main router & I'm seeing the same issue, devices have no connectivity after a few hours of runtime. Rebooting fixes everything, but every few hours I have to reboot.

When devices have no connectivity we can't even ping the dumb AP, ping responds back with no route to host.
Connecting to the dumb ap using a wired connection works.

I have 802.11r turned off, I had it ON earlier but then disabled it because I thought it could be related to the connectivity issue.

e8450 is running SNAPSHOT r18125-b764cb9e5b, and archer c7 is running 21.02.2.

I'm new to openWRT but I can help with logs/configuration if required

12

I followed @golialive advice and disabled WPA3 and selected WPA2-PSK only and also I disabled 802.11w.
I have now 802.11r enabled and fast BSS transition (FT) works fine regardless the "key addition failed".

With 802.11r or without 802.11r the main issue lies with the WPA3-SAE and it should be investigated further.

2 Likes
13

Interestingly I always had it set to WPA2-PSK & 802.11w disabled

14

I will keep that configuration for the next days to see if the no connectivity bug hits again and I will report back, for the moment it looks promising.

1 Like
15

After some days the "no connectivity" issue occurred again...
But little before the "no connectivity" event, I found in the logs for the particular android phone that I had the issue

IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE
IEEE 802.11: disassociated due to inactivity

I disabled the wifi and re-enabled the wifi on the phone and the phone was reconnected again without needing to reboot the router.

After searching the around for the de-authenticated due to inactivity i found the following suggestions for hostapd parameters.

disassoc_low_ack=0
max_inactivity=900
skip_inactivity_poll=1
wpa_group_rekey=0

Can anyone elaborate further on those hostapd parameters ?

Now i am thinking that we have to do with a multitude of issues some are related with WPA3 and some with the de-authentication due to inactivity.

16

I applied the

disassoc_low_ack=0
max_inactivity=900
skip_inactivity_poll=1

For the moment the "no connectivity" issue has not reoccurred but at least a couple of days should pass to verify it.

Can a hostapd graybeard elaborate further on those ?

disassoc_low_ack=0
max_inactivity=900
skip_inactivity_poll=1
wpa_group_rekey=0
17

As i was trying to get more info for the wireless interfaces with iw tool.
When I run to get the driver events:

iw event -f -t

i stumped on the following:

1645945618.215152: wlan0 (phy #0): unknown event 60
1645945619.244104: wlan1 (phy #1): unknown event 60

Searching the unknown event 60 i run into the following forum post
Archer C7 2.4 GHz wireless dies in 24~48 hours
In the post @sammo user notes:

I have also monitored the wifi event without the workaround

iw event -f -t

and notice when things goes bad you get event number 64,84
64 = notify_cqm
84 = probe_client

I am monitoring the iw event logs by saving the log in the /tmp by running

iw event -f -t > /tmp/iwevent.log &

Moreover in the main discussion thread about Belkin RT3200/Linksys E8450
Belkin RT3200/Linksys E8450 WiFi AX discussion and bugs
In the post @ilshatms notes:

I run into a similar problem on a regular basis. Restarting radio0 for 2.4G helps. In the kernel log, from interesting things, I observe the following entries

167014.660438] device wlan0 left promiscuous mode
[167014.665114] br-lan: port 5(wlan0) entered disabled state
[167014.832227] mt7622-wmac 18000000.wmac: Message 000025ed (seq 13) timeout
[167014.839140] mt7622-wmac 18000000.wmac: Message 00002aed (seq 14) timeout
[167015.305356] br-lan: port 5(wlan0) entered blocking state
[167015.310767] br-lan: port 5(wlan0) entered disabled state
[167015.316530] device wlan0 entered promiscuous mode
[167015.321506] br-lan: port 5(wlan0) entered blocking state
[167015.326961] br-lan: port 5(wlan0) entered forwarding state
[167015.721544] br-lan: port 5(wlan0) entered disabled state
[167024.735905] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[167024.742584] br-lan: port 5(wlan0) entered blocking state
[167024.747992] br-lan: port 5(wlan0) entered forwarding state

When you get the "no connectivity" issue can you check the kernel logs and the iw event logs to check if it is any of the two above cases ?

18

I have a single client (iPhone 11) that gets dropped. The WiFi connectivity symbol on the phone disapears and the LTE symbol is displayed. There is a corresponding event in logread output showing these lines:

Sun Feb 27 08:02:45 2022 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED xx:xx:xx
Sun Feb 27 08:02:45 2022 daemon.info hostapd: wlan1-1: STA xx:xx:xx IEEE 802.11: disassociated
Sun Feb 27 08:02:47 2022 daemon.info hostapd: wlan1-1: STA xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

I did not reply because I thought this one was about setups with fast roaming. So I started a
new thread at the time. Seeing this from @nkef, makes me think my issue and the issues here are related:

19

I'll try to capture the events. Started logging and monitoring
iw event -f -t > /tmp/iwevent.log &

20

I literally just caught an event with a broken wifi for 2.4G.

iw event -f -t:

1646049267.941741: wlan0 (phy #0): unknown event 139

1646049268.506660: wlan0 (phy #0): unknown event 139

1646049269.446994: wlan0 (phy #0): unknown event 60

1646049269.447690: wlan0 (phy #0): unknown event 60

1646049269.507885: wlan0 (phy #0): unknown event 60

1646049269.557064: wlan0: del station 78:28:ca:07:f9:48

1646049269.558367: wlan0 (phy #0): unknown event 139

1646049269.558615: wlan0 (phy #0): unknown event 139

1646049269.560283: wlan0 (phy #0): unknown event 60

1646049269.561416: wlan0 (phy #0): unknown event 60

1646049269.561950: wlan0 (phy #0): unknown event 60

1646049269.563643: wlan0 (phy #0): unknown event 60

1646049269.564115: wlan0 (phy #0): unknown event 60

1646049269.565792: wlan0 (phy #0): unknown event 60

1646049269.566349: wlan0 (phy #0): unknown event 60

1646049269.568266: wlan0 (phy #0): unknown event 60

1646049269.569346: wlan0 (phy #0): unknown event 60

1646049269.569674: wlan0 (phy #0): unknown event 60

1646049270.603817: wlan0 (phy #0): unknown event 60

1646049271.757194: wlan0: del station 44:23:7c:60:a5:26

1646049271.759102: wlan0: new station 44:23:7c:60:a5:26

1646049271.760379: wlan0 (phy #0): unknown event 60

1646049271.765658: wlan0 (phy #0): unknown event 60

1646049271.770014: wlan0 (phy #0): unknown event 139

1646049271.782243: wlan0 (phy #0): unknown event 139

1646049274.935932: wlan1 (phy #1): unknown event 60

1646049274.946629: wlan1 (phy #1): unknown event 60

1646049281.528183: wlan0 (phy #0): unknown event 60

1646049281.539219: wlan0 (phy #0): unknown event 60

1646049281.539982: wlan0 (phy #0): unknown event 60

1646049282.389580: wlan0 (phy #0): unknown event 60

1646049282.391006: wlan0: new station 78:28:ca:07:f9:48

1646049282.392734: wlan0 (phy #0): unknown event 60

1646049282.395072: wlan0 (phy #0): unknown event 60

1646049282.762708: wlan0 (phy #0): unknown event 139

1646049283.652474: wlan0 (phy #0): unknown event 139

1646049284.498770: wlan0 (phy #0): unknown event 139

1646049285.500944: wlan0 (phy #0): unknown event 60

1646049285.537014: wlan0: del station 78:28:ca:07:f9:48

1646049285.537377: wlan0 (phy #0): unknown event 139

1646049285.628089: wlan0 (phy #0): unknown event 60

1646049286.498129: wlan0 (phy #0): unknown event 60

1646049286.500589: wlan0: new station 78:28:ca:07:f9:48

1646049286.503066: wlan0 (phy #0): unknown event 60

1646049286.505387: wlan0 (phy #0): unknown event 60

1646049286.609654: wlan0 (phy #0): unknown event 139

1646049287.839240: wlan1 (phy #1): unknown event 60

1646049287.850068: wlan1 (phy #1): unknown event 60

1646049288.614127: wlan0 (phy #0): unknown event 139

1646049288.614472: wlan0 (phy #0): unknown event 139

Kernel log:

167014.660438] device wlan0 left promiscuous mode
[167014.665114] br-lan: port 5(wlan0) entered disabled state
[167014.832227] mt7622-wmac 18000000.wmac: Message 000025ed (seq 13) timeout
[167014.839140] mt7622-wmac 18000000.wmac: Message 00002aed (seq 14) timeout
[167015.305356] br-lan: port 5(wlan0) entered blocking state
[167015.310767] br-lan: port 5(wlan0) entered disabled state
[167015.316530] device wlan0 entered promiscuous mode
[167015.321506] br-lan: port 5(wlan0) entered blocking state
[167015.326961] br-lan: port 5(wlan0) entered forwarding state
[167015.721544] br-lan: port 5(wlan0) entered disabled state
[167024.735905] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[167024.742584] br-lan: port 5(wlan0) entered blocking state
[167024.747992] br-lan: port 5(wlan0) entered forwarding state
[185339.514787] mt7530 mdio-bus:00 lan3: Link is Down
[185339.519722] br-lan: port 3(lan3) entered disabled state
[185355.117529] mt7530 mdio-bus:00 lan3: Link is Up - 100Mbps/Full - flow control rx/tx
[185355.125377] br-lan: port 3(lan3) entered blocking state
[185355.130700] br-lan: port 3(lan3) entered forwarding state
[185358.234701] mt7530 mdio-bus:00 lan3: Link is Down
[185358.240108] br-lan: port 3(lan3) entered disabled state
[185360.318329] mt7530 mdio-bus:00 lan3: Link is Up - 100Mbps/Full - flow control rx/tx
[185360.326188] br-lan: port 3(lan3) entered blocking state
[185360.331512] br-lan: port 3(lan3) entered forwarding state
[219495.827558] br-lan: port 3(lan3) entered disabled state
[219495.834313] mt7530 mdio-bus:00 lan3: Link is Down
21

After I applied the :

disassoc_low_ack=0
max_inactivity=900
skip_inactivity_poll=1

The "no connecitity" issue has not occurred again but not enough days have passed.
Could you try to apply those also to both wifi interfaces to see if you get disconnected ?

I applied them the via uci:

uci set wireless.wifinet0.disassoc_low_ack='0'
uci set wireless.wifinet1.disassoc_low_ack='0'
uci set wireless.wifinet0.max_inactivity='900'
uci set wireless.wifinet1.max_inactivity='900'
uci set wireless.wifinet0.skip_inactivity_poll='1'
uci set wireless.wifinet1.skip_inactivity_poll='1'

uci commit wireless
wifi
1 Like