[Release 382] Asuswrt-Merlin 382.1 is now available

[hotsauce2007]

Clear your browser cache.

Merlin, one question:

Everytime that I set the DNS global filter with a YANDEX or another DNS for filter the devices on my network some devices can´t access the internet and keep failing , I will attach some screens showing the way I use, some devices are on LAN and another devices are on WIFI, I only have some problems with devices on WIFI, I am using this way because I dont want to have a ''open'' network for guest people and family, I only want to set my cellphone and laptop with a normal dns and the rest of the house can pass the global filter, but seems like we have a lot of issues with it, any idea?

The screen number one shows the global dns / YANDEX
The second one shows the DNS filter with the devices that I want to evade the global filter
The third shows the configuration for the AP router 1 and 2 at home

 

[PIO1]

With the latest build I am seeing a thousands of lines on the same errors in my log. I searched the forum but could not find much. Thoughts ?

Dec 9 16:38:06 kernel: CONSOLE: 098921.238 lb_alloc: req_size: 866 hnd_pktid_free_cnt: 297 OSL_MEM_AVAIL: 10208
Dec 9 16:38:06 kernel: CONSOLE: 098921.238 wl0: wlc_frame_get_mgmt: pktget error for len 866 fc 50
Dec 9 16:38:06 kernel: CONSOLE: 098921.238 wl0.1: wlc_probresp_send_probe_resp: wlc_frame_get_mgmt failed
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 lb_alloc: req_size: 866 hnd_pktid_free_cnt: 297 OSL_MEM_AVAIL: 10208
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 wl0: wlc_frame_get_mgmt: pktget error for len 866 fc 50
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 wl0.0: wlc_probresp_send_probe_resp: wlc_frame_get_mgmt failed
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 lb_alloc: req_size: 866 hnd_pktid_free_cnt: 297 OSL_MEM_AVAIL: 10208
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 wl0: wlc_frame_get_mgmt: pktget error for len 866 fc 50
Dec 9 16:38:06 kernel: CONSOLE: 098921.251 wl0.1: wlc_probresp_send_probe_resp: wlc_frame_get_mgmt failed
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 lb_alloc: req_size: 866 hnd_pktid_free_cnt: 297 OSL_MEM_AVAIL: 10208
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 wl0: wlc_frame_get_mgmt: pktget error for len 866 fc 50
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 wl0.0: wlc_probresp_send_probe_resp: wlc_frame_get_mgmt failed
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 lb_alloc: req_size: 866 hnd_pktid_free_cnt: 297 OSL_MEM_AVAIL: 10208
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 wl0: wlc_frame_get_mgmt: pktget error for len 866 fc 50
Dec 9 16:38:06 kernel: CONSOLE: 098921.274 wl0.1: wlc_probresp_send_probe_resp: wlc_frame_get_mgmt failed

 

[Ari_el]

Upgraded from 380 to 382.1_2 (AC3100). After reboot, a Belkin WeMo Mini smartplug was unable to associate with the AP - device factory reset, making SSID visible, nothing would help. Another WeMo model (insight) had no issues.
After some tinkering and finding some references in this thread, disabling "Airtime Fairness" in the 2.4Ghz did the trick. I have MU-MIMO also disabled (but I had never enabled that); Universal & Explicit Beamforming are both ON and cause no issues with this device.

 

[telUK]

Hi

I installed my ac86u yesterday, so far all good, I have about 11 devices connected, mostly all wifi.

Just wondering if there is any advise on settings I should change, all I have done so far is choose a fixed channel for the 2.4ghz band and switch it to 20mhz bandwidth as advised on here.

Wondering about things like Airtime Fairness and anything else on or off ?

Thanks

 

[cvee]

I just successfully restored my Asus rt-ac3200 from the official 382 codebase firmware released by Asus. Is there a Merlin version planned on new 382 code? Does Merlin allow media bridge to share wifi also?


Sent from my iPad using Tapatalk

 

[RMerlin]

Is there a Merlin version planned on new 382 code?

There's no GPL code available for that model yet. It will have to wait until a) Asus releases it, b) that I can confirm that this code is compatible with the other models I support, and c) that I'm done with other current works in progress.

Current focus is on finalizing 380.69. After that, it will be on 382.2 and the RT-AC68U support. RT-AC3200 support would only come after that.

Does Merlin allow media bridge to share wifi also?

Wifi-related features are identical to stock firmware. If stock firmware has it, then mine will as well.

 

[Eric Lieb]

Is AIMesh going to be added to the 382 code base eventually? Having to run the asus official aimesh firmware right now.

 

[RMerlin]

Is AIMesh going to be added to the 382 code base eventually? Having to run the asus official aimesh firmware right now.

Depends if Asus adds it to the generic code base or not. That feature is still under development by them, so it's too early to tell.

If they make it available only through a separate build (like they do for Facebook Wifi) then no, it won't be included.

 

[Eric Lieb]

Depends if Asus adds it to the generic code base or not. That feature is still under development by them, so it's too early to tell.

If they make it available only through a separate build (like they do for Facebook Wifi) then no, it won't be included.

Damn that may suck! I love your build but also need AiMesh (much better than repeater).

 

[Keenan]

Hi

I installed my ac86u yesterday, so far all good, I have about 11 devices connected, mostly all wifi.

Just wondering if there is any advise on settings I should change, all I have done so far is choose a fixed channel for the 2.4ghz band and switch it to 20mhz bandwidth as advised on here.

Wondering about things like Airtime Fairness and anything else on or off ?

Thanks

See this post made in response to similar questions I asked,

[Release 382] Asuswrt-Merlin 382.1 is now available

That said, I'm still having issues with a 2.4GHz WeMo light switch, sometimes it will respond, but very slowly and other times it doesn't work at all. And even other times it works just fine. I'm not sure what's going on with it but I didn't have this behavior with my RT-N66U.

I do recall SNB's review of the 86U mentioning something about erratic connection behavior on the 2.4 GHz and I'm wondering if that's what I'm seeing. Although, it seems to be only the one device, so I don't know.

 

[Jack Yaz]

See this post made in response to similar questions I asked,

[Release 382] Asuswrt-Merlin 382.1 is now available

That said, I'm still having issues with a 2.4GHz WeMo light switch, sometimes it will respond, but very slowly and other times it doesn't work at all. And even other times it works just fine. I'm not sure what's going on with it but I didn't have this behavior with my RT-N66U.

I do recall SNB's review of the 86U mentioning something about erratic connection behavior on the 2.4 GHz and I'm wondering if that's what I'm seeing. Although, it seems to be only the one device, so I don't know.

Have you tried disabling AirTime Fairness on 2.4ghz radio (Professional tab)

 

[Keenan]

Have you tried disabling AirTime Fairness on 2.4ghz radio (Professional tab)

Yes, per Merlin's suggestions in that above-linked post. I did have the router set to a specific channel based on a site scan with some wifi scanning software but I just changed it back to Auto and I'll see how it goes today.

 

[Jack Yaz]

Yes, per Merlin's suggestions in that above-linked post. I did have the router set to a specific channel based on a site scan with some wifi scanning software but I just changed it back to Auto and I'll see how it goes today.

Does the light switch respond to a ping? Wondering if you could run a constant ping, and see if/when latency increases or packets drop, and see if anything else is happening in the environment at the time.

 

[Keenan]

Does the light switch respond to a ping? Wondering if you could run a constant ping, and see if/when latency increases or packets drop, and see if anything else is happening in the environment at the time.

I haven't actually tried that, but it does respond instantly when controlled directly with the Wemo iOS app. Additional info is that the Wemo switch is being controlled by the Alexa system, I tell Alexa to turn on/off and then it does its thing. With the N66U this worked fine probably 95+% of the time. With the only change being the router it makes think that's where the problem is. Of course, it could also just be a matter of finding the right settings.

Any input is appreciated, thanks!

 

[skeal]

Does the light switch respond to a ping? Wondering if you could run a constant ping, and see if/when latency increases or packets drop, and see if anything else is happening in the environment at the time.

Is the light switch trying to negotiate with a a hidden network?

 

[Keenan]

Is the light switch trying to negotiate with a a hidden network?

This is the switch in question,
http://www.belkin.com/us/F7C029-Belkin/p/P-F7C029;jsessionid=394324419A4933C8700CBE1EAB8F1E40/

Wemo(Belkin) Smart Plug model F7C029fc

I also have this switch here, http://www.belkin.com/us/F7C063-Belkin/p/P-F7C063;jsessionid=394324419A4933C8700CBE1EAB8F1E40/ and I don't have any trouble with it. It is only a few feet from the router, the problem switch is about 15 ft away.

 

[XIII]

I'm having some unexpected DNS (leak test) results, but I'm not sure whether I did something wrong (most likely!) when migrating from AC66U to AC86U or it's 382.1 related:

https://www.snbforums.com/threads/m...86u-router-how-to-ddns-etc.42419/#post-363719

Who can help?

 

[skeal]

This is the switch in question,
http://www.belkin.com/us/F7C029-Belkin/p/P-F7C029;jsessionid=394324419A4933C8700CBE1EAB8F1E40/

Wemo(Belkin) Smart Plug model F7C029fc

I also have this switch here, http://www.belkin.com/us/F7C063-Belkin/p/P-F7C063;jsessionid=394324419A4933C8700CBE1EAB8F1E40/ and I don't have any trouble with it. It is only a few feet from the router, the problem switch is about 15 ft away.

I'm just wondering if the 2.4 network has it's SSID hidden. This can cause intermittent connections.

 

[Vulnax]

Still getting repeat system log entries for the below, looks like failing services??
Only since 382.1_2 firmware . RT-AC88U.

Any thoughts / ideas what to adjust, or is it a bug ??
Thanks

Dec 10 23:00:35 kernel: CONSOLE: 112956.987 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xf93 for 200 ms
Dec 10 23:00:35 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:35 kernel: CONSOLE: 112957.298 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xf9c for 200 ms
Dec 10 23:00:36 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: wl1.0 2c:f0:a2:ba:96:d8 scb:00341bc4 tid:0
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: wl1.0 dead_cnt 2 tx_in_transit 1 psm_mux 0xfff0 aqmqmap 0x0x303 aqmfifo_status 0x0x4000 fifordy 0x0 cpbusy 0x0
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: ifsstat 0xa2 nav_stat 0x1 txop 96904
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: pktpend: 0 0 0 0 0 ap 1
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: txall 1383 txbcn 0 txrts 0 rxcts 0 rsptmout 0 rxstrt 0
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 3 0 0 0 0 ifs_boff 0
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: again1 ifsstat 0xa2 nav_stat 0x1
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 ampdu_dbg: again2 ifsstat 0xa2 nav_stat 0x1
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 wl1: wlc_ampdu_watchdog: cleaning up ini tid 0 due to no progress for 2 secs tx_in_transit 1
Dec 10 23:00:36 kernel: CONSOLE: 112957.533 wl1: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 39
Dec 10 23:00:36 kernel: CONSOLE: 112957.665 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xf9f for 200 ms
Dec 10 23:00:36 kernel: CONSOLE: 112958.029 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfa1 for 200 ms
Dec 10 23:00:36 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:37 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:37 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:37 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:37 kernel: CONSOLE: 112959.317 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfb3 for 200 ms
Dec 10 23:00:37 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:37 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:38 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:38 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:38 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:38 kernel: CONSOLE: 112959.665 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfb7 for 200 ms
Dec 10 23:00:38 kernel: CONSOLE: 112959.965 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfc0 for 200 ms
Dec 10 23:00:38 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:38 kernel: CONSOLE: 112960.265 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfc7 for 200 ms
Dec 10 23:00:39 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:39 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:39 kernel: CONSOLE: 112961.417 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfcb for 200 ms
Dec 10 23:00:40 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:40 kernel: CONSOLE: 112961.717 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfce for 200 ms
Dec 10 23:00:40 kernel: CONSOLE: 112962.017 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfd1 for 200 ms
Dec 10 23:00:40 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:40 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:41 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:41 kernel: CONSOLE: 112962.595 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:41 kernel: CONSOLE: 112962.595 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:41 kernel: CONSOLE: 112962.595 wlc_ieml_parse_frame: err -1
Dec 10 23:00:41 kernel: CONSOLE: 112962.595 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:41 kernel: CONSOLE: 112962.908 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:41 kernel: CONSOLE: 112962.908 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:41 kernel: CONSOLE: 112962.908 wlc_ieml_parse_frame: err -1
Dec 10 23:00:41 kernel: CONSOLE: 112962.908 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:41 kernel: CONSOLE: 112962.974 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfd4 for 200 ms
Dec 10 23:00:41 kernel: CONSOLE: 112963.221 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:41 kernel: CONSOLE: 112963.221 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:41 kernel: CONSOLE: 112963.221 wlc_ieml_parse_frame: err -1
Dec 10 23:00:41 kernel: CONSOLE: 112963.221 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:41 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:42 kernel: CONSOLE: 112963.534 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:42 kernel: CONSOLE: 112963.534 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:42 kernel: CONSOLE: 112963.534 wlc_ieml_parse_frame: err -1
Dec 10 23:00:42 kernel: CONSOLE: 112963.534 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:42 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:42 kernel: CONSOLE: 112963.758 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfdd for 200 ms
Dec 10 23:00:42 kernel: CONSOLE: 112963.847 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:42 kernel: CONSOLE: 112963.847 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:42 kernel: CONSOLE: 112963.847 wlc_ieml_parse_frame: err -1
Dec 10 23:00:42 kernel: CONSOLE: 112963.847 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:42 kernel: CONSOLE: 112964.098 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfeb for 200 ms
Dec 10 23:00:42 kernel: CONSOLE: 112964.159 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:42 kernel: CONSOLE: 112964.159 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:42 kernel: CONSOLE: 112964.159 wlc_ieml_parse_frame: err -1
Dec 10 23:00:42 kernel: CONSOLE: 112964.159 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:42 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:43 kernel: CONSOLE: 112964.473 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:43 kernel: CONSOLE: 112964.473 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:43 kernel: CONSOLE: 112964.473 wlc_ieml_parse_frame: err -1
Dec 10 23:00:43 kernel: CONSOLE: 112964.473 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:43 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:43 kernel: CONSOLE: 112964.787 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:43 kernel: CONSOLE: 112964.787 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:43 kernel: CONSOLE: 112964.787 wlc_ieml_parse_frame: err -1
Dec 10 23:00:43 kernel: CONSOLE: 112964.787 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:43 kernel: CONSOLE: 112965.009 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xff2 for 200 ms
Dec 10 23:00:43 kernel: CONSOLE: 112965.100 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:43 kernel: CONSOLE: 112965.100 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:43 kernel: CONSOLE: 112965.100 wlc_ieml_parse_frame: err -1
Dec 10 23:00:43 kernel: CONSOLE: 112965.100 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:43 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:44 kernel: CONSOLE: 112965.413 wl1: WPA2 mcast cipher 00:0f:ac:2 not enabled
Dec 10 23:00:44 kernel: CONSOLE: 112965.413 wl1: wlc_akm_arq_parse_rsn_ie: unsupported request in WPA2 IE from e8:99:c4:b6:64:91
Dec 10 23:00:44 kernel: CONSOLE: 112965.413 wlc_ieml_parse_frame: err -1
Dec 10 23:00:44 kernel: CONSOLE: 112965.413 wl1: wlc_ap_process_assocreq: wlc_iem_parse_frame failed
Dec 10 23:00:44 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:44 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:44 kernel: CONSOLE: 112965.758 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xff9 for 200 ms
Dec 10 23:00:44 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:45 kernel: CONSOLE: 112966.496 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xfff for 200 ms
Dec 10 23:00:45 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:45 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:45 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:45 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:45 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:46 kernel: CONSOLE: 112967.358 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0x2 for 200 ms
Dec 10 23:00:46 kernel: CONSOLE: 112967.658 wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0x15 for 200 ms
Dec 10 23:00:46 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:47 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:47 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Dec 10 23:00:47 kernel: dhd_flow_rings_delete_for_peer: ifindex 0

 

[Keenan]

I'm just wondering if the 2.4 network has it's SSID hidden. This can cause intermittent connections.

How would I determine that?