I own all, except the guest. I offer the guest network as a free service to my neighborhood to the less privileged who live close to me. It is just about 3 to 5 devices on the guest network most of the time. I monitor their traffic all the time and it isn't anything to talk about.
I would suggest the guest network is a red herring. There were reports of issues with android device in the past (around (de)associate), I thought these had been addressed but maybe not, Check the open/closed issue tracker at the repository maybe.
Update: I really don't know where to start. lol.
Disabling legacy mode on both SSID's definitely helps. The spikes in pings and timeout, I observed are less but still unsatisfactory. My cellphone, though, a relatively modern device(Moto G5 Plus) does not connect when legacy mode is disabled. Of my 15 wireless devices on this AP, this is the only one which behaves this way.
I cannot tell whether the problem is caused specifically by Android devices on the Guest network because the guest devices are all of Android type. It is quite possible it is caused by Android devices but I also think the problem may be caused by those devices when they are far from the Guest access point and are continuously trying to negotiate the best low rate(about 1 Mbps). Somehow, this appears to throw the entire wireless network off.
I may have to try an older Wifi driver to see if this is the issue. Also contemplating trying DD-WRT to see if the behaviour is the same under similar conditions.
Any other suggestions?
I have a G5 plus and it connects to my wrt1900acs V2 in non legacy mode just fine.
Do you have igmp snooping enabled?
Also have you actually power cycled this device? Not reboot, but power cycle.
IGMP snooping is not enabled.
root@OpenWrt:~# cat /sys/devices/virtual/net/br-lan/bridge/multicast_snooping
0
Just power cycled - same issue. Maybe it is a ROM issue. I'm running AOSIP Pie.
I tried DD-WRT today. Version 3.0-r37305 (10/10/18). Kernel is 4.9.131(as compared to v4.14 in OpenWrt 18.06.2 ). Sad to say the experience is the same. I do not know what version of the mlmwifi driver is being utilised. Can't find that anywhere.. The router buckles when about 3 or 4 Android devices are connected to the Guest 2.4Ghz network. Ping time shoots up and connection begins to time out. They all seem to connect in "legacy mode", even if I've set up the AP to use G/N mode only. I am not sure why this is. I do not see any strange messages in dmesg.
I will revert to OpenWRT later and try other drivers built by @eduperez to see if this makes a difference. Any advice/suggestion is surely welcome. Thanks.
If you install 18.06.1, you can then update the drivers using my packages. However, 18.06.2 has the most updated drivers, and there are no further packages.
Yesterday I built a current master image with commit 2f160bb reverted if you want to see if that actually is the cause of your issue. Link is off the mutts head.
Sorry I don't understand the part about the link. Did you compile OpenWrt or the driver and is a link available?
I had built a complete image, but with the one commit in question backed out of mwlwifi. If you click on my avatar you will see a Stuff link, or just go to my github and follow the link to my goggle drive.
Btw, I noticed some of you here are also on the threads concerning the official Mwlwifi driver on Github:
For the benefit of those who are not following on Github, I should state here that I may have overlooked the following messages in my kernel and system logs. I am not certain whether this has anything to do with the issues being discussed but I thought I would just list it here:
Kernel Log
[ 20.528096] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 20.534609] br-lan: port 3(wlan0) entered blocking state
[ 20.539940] br-lan: port 3(wlan0) entered forwarding state
[ 20.601909] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
[ 20.697022] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
[ 2082.685205] ieee80211 phy0: cmd 0x9101=SetApBeacon timed out
[ 2082.691010] ieee80211 phy0: return code: 0x9136
[ 2082.695621] ieee80211 phy0: timeout: 0x1101
[ 2437.871201] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
[ 2437.877259] ieee80211 phy0: return code: 0x9101
[ 2437.881804] ieee80211 phy0: timeout: 0x1128
[77104.796473] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
[77104.802525] ieee80211 phy0: return code: 0x9101
[77104.807099] ieee80211 phy0: timeout: 0x1128
[126708.626648] ieee80211 phy0: cmd 0x9101=SetApBeacon timed out
[126708.632471] ieee80211 phy0: return code: 0x9136
[126708.637353] ieee80211 phy0: timeout: 0x1101
[157716.797139] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
[157716.803308] ieee80211 phy0: return code: 0x9101
[157716.808032] ieee80211 phy0: timeout: 0x1128
[157791.976000] ieee80211 phy0: cmd 0x9125=BAStream timed out
[157791.981540] ieee80211 phy0: return code: 0x9101
[157791.986196] ieee80211 phy0: timeout: 0x1125
[166589.548330] ieee80211 phy0: cmd 0x9101=SetApBeacon timed out
[166589.554142] ieee80211 phy0: return code: 0x9136
[166589.558804] ieee80211 phy0: timeout: 0x1101
[172890.881186] ieee80211 phy0: cmd 0x9101=SetApBeacon timed out
[172890.887436] ieee80211 phy0: return code: 0x9136
[172890.892280] ieee80211 phy0: timeout: 0x1101
[340719.899916] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
[340719.906165] ieee80211 phy0: return code: 0x9101
[340719.910827] ieee80211 phy0: timeout: 0x1128
[340919.540463] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
[340919.546607] ieee80211 phy0: return code: 0x9101
[340919.551238] ieee80211 phy0: timeout: 0x1128
System Log
Thu Feb 21 20:00:27 2019 kern.err kernel: [340719.899916] ieee80211 phy0: cmd 0x9128=SetSpectrumMgmt timed out
Thu Feb 21 20:00:27 2019 kern.err kernel: [340719.906165] ieee80211 phy0: return code: 0x9101
Thu Feb 21 20:00:27 2019 kern.err kernel: [340719.910827] ieee80211 phy0: timeout: 0x1128
Thu Feb 21 20:00:27 2019 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Feb 21 20:00:27 2019 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
"The mutts head". Lol. I will try the image. Thanks.