Plenty of articles on the web also mention that Google rolled out a fix on January 18. What nobody mentions is that it's currently a beta fix. I had version 11.9.51 for Google Play Services and it was causing issues. Upgrading to the beta version 11.9.75 resolved my wifi issues (network not longer visible, or asking for password again, or not responding at all).
So : upgrade to beta version or wait for the public rollout to begin.
Click "Read More" and scroll all the way down for the version.
Back up once, and scroll all the way down to see "Become a beta tester". Click "I'm in". You might want to be on wifi and have the device charging so it updates faster. This will update the Google Play Services app across all your Google devices.
Click "Leave" to go back to public version whenever you want.
As of today (January 24, 2018), the public version was still not updated.
Plenty of articles on the web also mention that Google rolled out a fix on January 18. What nobody mentions is that it's currently a beta fix. I had version 11.9.51 for Google Play Services and it was causing issues. Upgrading to the beta version 11.9.75 resolved my wifi issues (network not longer visible, or asking for password again, or not responding at all).
So : upgrade to beta version or wait for the public rollout to begin.
Click "Read More" and scroll all the way down for the version.
Back up once, and scroll all the way down to see "Become a beta tester". Click "I'm in". You might want to be on wifi and have the device charging so it updates faster. This will update the Google Play Services app across all your Google devices.
Click "Leave" to go back to public version whenever you want.
As of today (January 24, 2018), the public version was still not updated.
Do you have an Android phone or tablet on your wifi network ? If so, the Google Play Services app may be at fault
Interesting. Thank you very much for the find.
As with all intermittent wifi issues, it's hard to evaluate any measures taken, but I haven't had issues since updating to the 180120 beta of Google Play Services, and haven't had any issues on Android, so can recommend the update.
More interestingly, I'm in the Android O/8 beta program (currently one minor ahead of mainstream) but still had the old Google Play Services app.
It should work by just clicking the link to the app. I didn't have to use any workaround at all. Joining the beta program for Google Play apps should be available to everyone, everywhere, or? Did you try the link?
I had to switch Google Play accounts to join the beta for this particular app, but Android told me about it loud & clear.
I'm happy to see that I'm not alone having massive issue with the wifi ...
I'm trying to isolate where is the problem because obviously this works for some people with the same hardware as me (R7000).
I've managed to get an incredible 3 days uptime by enabling only 2.4Ghz with the following settings (see attachment)
I leave it like that until end of the week and if it is still stable I will change a setting, (I know that setting fixed wireless channel, enabling "Optimize Multicast Traffic", "Explicit Beamforming" and "Implicit Beamforming" is unstable ...
So I've got 5 days and half uptime and this is still working ...
I haven't noticed weird behavior.
I'm enabling now "Optimize Multicast Traffic" lets see if that break, I'll report in a week or before if I got a crash.
After 3 days the router is still up and running on wired connexion, but not for wifi.
So enabling "Optimize Multicast Traffic" seems to break things for me ...
I'm going to try to see if 33675 is better.
So after a day a half the router rebooted by itself. I kept the configuration from 34320M, and turned off "Optimize Multicast Traffic" and set Regulatory Domain fo France ...
So 33675M is another piece of shite for me
Here the errors I gathered from a remote syslog.
From what I see ledtool was stuck writing then traff OOM (probably triggering the reboot).
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Thu Feb 01, 2018 3:01 Post subject:
Kong R34320M on a Netgear r8000. Has been running fine for over 5 days. This evening started having issues with dhcp not giving out IP addresses only on the 2.4GHz wireless. 5GHz wireless was working fine and could get IP address. Did the obvious of rebooting router, no I did not check the syslog first, dumb me. Reboot did not fix, really a power off and on. Did a reset and reconfigure from backup and then things were working again. Don't understand. However, since I want a reliable network to keep teens from complaining as well as my own things like streaming I decided to reinstall the latest Netgear firmware. Especially bothersome when it is 8:30 in eve and just want to sit down and chill. Backup up and everyone is now happy. Will wait for next Kong and try again. When I tried Brainslayer's build my wireless speed was not as good as with Kong, which was also slower then OEM in my simple iperf test. Not by a huge amount, but is slower. _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
My router has been up and online (no reboots, wifi dropping, etc.) for the past 3 days. Devices have not disconnected themselves.
My configuration is abnormal, in that I have well over 50 wireless devices, ranging from security cameras, wifi outlets, lights, and other IoT devices, so I cannot reset the settings with each build. I'd be stuck configuring static IPs all day long.
Kong R34320M on a Netgear r8000. Has been running fine for over 5 days. This evening started having issues with dhcp not giving out IP addresses only on the 2.4GHz wireless. 5GHz wireless was working fine and could get IP address. Did the obvious of rebooting router, no I did not check the syslog first, dumb me. Reboot did not fix, really a power off and on. Did a reset and reconfigure from backup and then things were working again. Don't understand. However, since I want a reliable network to keep teens from complaining as well as my own things like streaming I decided to reinstall the latest Netgear firmware. Especially bothersome when it is 8:30 in eve and just want to sit down and chill. Backup up and everyone is now happy. Will wait for next Kong and try again. When I tried Brainslayer's build my wireless speed was not as good as with Kong, which was also slower then OEM in my simple iperf test. Not by a huge amount, but is slower.
From what I understand Shibby is not doing any Tomato development at least for now so Tomato improvements and feature adds are not going to happen as everyone else just take Shibby and tweak it. Guessing it does not have the KRACK fix installed for example.
Reading about broadcomm support with Openwrt/LEDE. They do not have support from Netgear for the wireless driver so they are using a opensource driver which lacks in functionality. This is an advantage Brainslayer has as he has a license with Netgear and has signed a non-disclosure with them.
Both Tomato and OpenWRT use outdated Linux kernels. Not that there’s anything wrong with that, but there are probably some benefits with dd-wrt in the security department or if you use IPv6.
I like to be on the bleeding edge of technology. When I see builds of firmware go dead for months at a time, like Tomato, I tend to stay away from them.
DDWRT has been working for me for many years, and I just view this wifi bug as just that, a bug. Eventually it will be squashed and things will be back to normal.
It doesnt mean I'll abandon the firmware and go elsewhere. I dont think others should rush to find something different either.
Reboot did not fix, really a power off and on. Did a reset and reconfigure from backup and then things were working again. Don't understand. However, since I want a reliable network to keep teens from complaining as well as my own things like streaming I decided to reinstall the latest Netgear firmware. Especially bothersome when it is 8:30 in eve and just want to sit down and chill. Backup up and everyone is now happy. Will wait for next Kong and try again. When I tried Brainslayer's build my wireless speed was not as good as with Kong, which was also slower then OEM in my simple iperf test. Not by a huge amount, but is slower.