If it is GOOGLE causes the wifi disconnecting issue, what would be the work-around for now for us to keep our router stabilized. I was trying to roll back to the old Kongac firmware I thought was working but the problem persists....
34015 is a really good build. I had 20+ days uptime on my gateway with QoS, OpenVPN Server, SFE, dnsmasq for DHCP, USB and overclocked to 1400 with no problems or cutouts. Best of luck.
Update: v3.0-r34015M freezes after 22hours.
Does DDNS works on your R7000 with DD-WRT v3.0-r34015M kongac (12/09/17) ????
Also DD-WRT v3.0-r34320M kongac (01/03/1 DDNS does not work.
Mine does not, I'm not able to save nor apply settings.
Tested in Chrome, Firefox & IE11 all same results.
nvram was erased before upgrading and also when before configuration? _________________ Regards,
Vaako
1x Netgear R7800 Nighthawk - firmware not decided yet !!!!
1x Netgear R7000 Nighthawk r36410
1x Ubiquiti RouterStation Pro DD-WRT r23204 std (12/24/13)
1x Asus RT-N16 SVN revision 20675 NEWD-2 K2.6
1x Linksys E4200 v3.0 r34777 mega (01/31/18 )
1x Buffalo WZR-HP-G300NH B0 B0 Gargoyle FW
1x Linksys WRT600N v1.1 (Bricked)
1x Linksys WRT54GL v1.1 (DD-WRT 26446)
1x Linksys WRT54GS v2.2 (DD-WRT 26446)
1x Linksys RVS4000 (stock fw)
3x D-Link DWL-7100AP (openWRT)
2x TP-Link TL-WA801ND (Bridge mode) 100mW TX-Power
Asus WL-520GU SVN 16403M NEWD-2 Eko std-nokaid
4x Fonera with Gargoyle FW
Last edited by Vaako on Wed Jan 17, 2018 19:03; edited 1 time in total
Router:R7000
Firmware:34320M
Kernel: 4.4.109
Status: up and running for >12 hours / >2,5 hours.
Reset: Yes 3x
Errors: The issue that WL0 (2.4G) und WL1 (5G) crashing randomly after several hours is also present in this fw release (I first realized it in 33675M) . Hope you get this fixed soon. reverting back to 31800M
How are you identifying that WL0/WL1 are crashing? I suspect something similar is happening with my 2.4ghz connection since my extenders and printer stop communicating unless I reboot.
I have observed the exact same issue on R7000 on 33675 and later, all KONG versions. It might have been present on earlier firmwares but I do not have a record of it.
Typically I get into a situation where SSID is no longer broadcasted. A total freeze. Sometimes after 3 hours, sometimes after 48...
I also get another issue which might be related. Where the SSID is still broadcasted, but the password is no longer accepted (on iPad, iPhone, and windows 10 pc).
I have a similar setup with WL0 and WL1 for private lan (same SSID) and WL0.1restricted to. IOT devices, setup with NAT and Network isolation as recommended by Kong.
I use DNS Masq and have separate up ranges for LAN and IOT.
How can I best troubleshoot last actions on router before freeze?
This, and maybe all, firmwares don't handle all OpenVPN connection issues. I had PIA over OpenVPN lose connection a couple of days ago. Reconnection was being attempted repeatedly by the router, but it would not reconnect. Manually killed the openvpn process (kill -9 'pid of openvpn process') and then my custom script restarted openvpn and it connected fine. If/when it happens again, I will see if there is anything the router can use to detect the problem and modify the script file to force a restart of openvpn. Existing custom script:
Code:
#!/bin/bash
/bin/pidof openvpn >/dev/null
if [ $? -ne 0 ]; then
if [ -f /tmp/openvpnfail.log ]; then
/usr/sbin/openvpn --config /tmp/openvpncl/openvpn.conf --route-up /tmp/openvpncl/route-up.sh --route-pre-down /tmp/openvpncl/route-down.sh --daemon &
echo "openvpn restarted" >> /tmp/openvpnrestart.log
else
/bin/touch /tmp/openvpnfail.log
fi
else
/bin/rm -f /tmp/openvpnfail.log
fi
/bin/date > /tmp/openvpndate.log
This, and maybe all, firmwares don't handle all OpenVPN connection issues. I had PIA over OpenVPN lose connection a couple of days ago. Reconnection was being attempted repeatedly by the router, but it would not reconnect. Manually killed the openvpn process (kill -9 'pid of openvpn process') and then my custom script restarted openvpn and it connected fine. If/when it happens again, I will see if there is anything the router can use to detect the problem and modify the script file to force a restart of openvpn. Existing custom script:
Code:
#!/bin/bash
/bin/pidof openvpn >/dev/null
if [ $? -ne 0 ]; then
if [ -f /tmp/openvpnfail.log ]; then
/usr/sbin/openvpn --config /tmp/openvpncl/openvpn.conf --route-up /tmp/openvpncl/route-up.sh --route-pre-down /tmp/openvpncl/route-down.sh --daemon &
echo "openvpn restarted" >> /tmp/openvpnrestart.log
else
/bin/touch /tmp/openvpnfail.log
fi
else
/bin/rm -f /tmp/openvpnfail.log
fi
/bin/date > /tmp/openvpndate.log
Router:R7000
Firmware:34320M
Kernel: 4.4.109
Status: up and running for >12 hours / >2,5 hours.
Reset: Yes 3x
Errors: The issue that WL0 (2.4G) und WL1 (5G) crashing randomly after several hours is also present in this fw release (I first realized it in 33675M) . Hope you get this fixed soon. reverting back to 31800M
How are you identifying that WL0/WL1 are crashing? I suspect something similar is happening with my 2.4ghz connection since my extenders and printer stop communicating unless I reboot.
I have observed the exact same issue on R7000 on 33675 and later, all KONG versions. It might have been present on earlier firmwares but I do not have a record of it.
Typically I get into a situation where SSID is no longer broadcasted. A total freeze. Sometimes after 3 hours, sometimes after 48...
I also get another issue which might be related. Where the SSID is still broadcasted, but the password is no longer accepted (on iPad, iPhone, and windows 10 pc).
I have a similar setup with WL0 and WL1 for private lan (same SSID) and WL0.1restricted to. IOT devices, setup with NAT and Network isolation as recommended by Kong.
I use DNS Masq and have separate up ranges for LAN and IOT.
How can I best troubleshoot last actions on router before freeze?
L
Yes! The very same thing happens where the password is no longer accepted...this only is fixed after a reboot of the router. Annoying to say the least, since I have roughly 30 wifi devices still on 2.4ghz.
Router:R7000
Firmware:34320M
Kernel: 4.4.109
Status: up and running for >12 hours / >2,5 hours.
Reset: Yes 3x
Errors: The issue that WL0 (2.4G) und WL1 (5G) crashing randomly after several hours is also present in this fw release (I first realized it in 33675M) . Hope you get this fixed soon. reverting back to 31800M
How are you identifying that WL0/WL1 are crashing? I suspect something similar is happening with my 2.4ghz connection since my extenders and printer stop communicating unless I reboot.
I have observed the exact same issue on R7000 on 33675 and later, all KONG versions. It might have been present on earlier firmwares but I do not have a record of it.
Typically I get into a situation where SSID is no longer broadcasted. A total freeze. Sometimes after 3 hours, sometimes after 48...
I also get another issue which might be related. Where the SSID is still broadcasted, but the password is no longer accepted (on iPad, iPhone, and windows 10 pc).
I have a similar setup with WL0 and WL1 for private lan (same SSID) and WL0.1restricted to. IOT devices, setup with NAT and Network isolation as recommended by Kong.
I use DNS Masq and have separate up ranges for LAN and IOT.
How can I best troubleshoot last actions on router before freeze?
L
Yes! The very same thing happens where the password is no longer accepted...this only is fixed after a reboot of the router. Annoying to say the least, since I have roughly 30 wifi devices still on 2.4ghz.
I have a similar issue, where all of a sudden my Fedora machine prompts me for the WiFi password. I just click cancel, go to the list of SSIDs and click "connect" to reconnect to my WiFi. Works fine, no reboot needed.
This is on 34320, didn't have this issue before (but I came straight from 33675 I think, definitely skipped some versions before 34320).
Kong DD-WRT used to be 100% rock stable on my R7000, but ever since the KRACK fixes (not saying it's related, it's just at that time period) it's been less stable for me.
@kong
there is definitely something funky going on with the wifi driver
ever since the november builds I been getting clients that are disconnecting or complains of not having internet,rebooting the router usually fixes it I have about ~8-15 devices connected on avg speeds are fine it just drops WAN without warning
I spent most of today rolling back though builds to find one thats stable I finally ended up on DD-WRT nonkong v3.0-r33525 std 10/17/17
if you have any archive of your older builds that would help I couldn't find anything older than november
netgear r6250/tplink 841v9 running as a wired extender
@kong
there is definitely something funky going on with the wifi driver
ever since the november builds I been getting clients that are disconnecting or complains of not having internet,rebooting the router usually fixes it I have about ~8-15 devices connected on avg speeds are fine it just drops WAN without warning
I spent most of today rolling back though builds to find one thats stable I finally ended up on DD-WRT nonkong v3.0-r33525 std 10/17/17
if you have any archive of your older builds that would help I couldn't find anything older than november
netgear r6250/tplink 841v9 running as a wired extender
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 ...
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 ...
are your clients disconnecting or what behavior are you getting
on the 6250 I am getting not really drops and when the client reconnects it complains about not having internet access wired remains up
if you still get issues try dropping back to a october 2017 build I am currently testing it but the issue was very sporadic makes it hard to test
I'm happy to see that I'm not alone having massive issue with the wifi ...
I am running R33770M on R7000 for 50 days uptime now, both wireless bands enabled and a guest wifi on 2.4, so if you guys want to roll back, that older version seems solid.
DDNS does not work.
reverting back to 31800M
