Joined: 30 Jun 2014 Posts: 61 Location: California
Posted: Thu Oct 19, 2017 0:09 Post subject:
bdg2 wrote:
gin-n-tonic wrote:
Router Model: WNDR3700v2
Status: good
Reset: none
<snipped for brevity>
Does your httpd crash when you go to the Status_Conntrack.asp page like on my WNDR3700v2?
I had no problem. Accessed via dd-WRT> Status> Router> Active IP Connections. Used the Refresh, Close, and upper-right x. GUI stayed alive and responsive. I am using http, not https, over a wired LAN if that makes any difference.
Does your httpd crash when you go to the Status_Conntrack.asp page like on my WNDR3700v2?
I had no problem. Accessed via dd-WRT> Status> Router> Active IP Connections. Used the Refresh, Close, and upper-right x. GUI stayed alive and responsive. I am using http, not https, over a wired LAN if that makes any difference.
That's all exactly the same as me.
Thanks, I guess I might have a weird hardware fault, or possibly something in my configuration.
Last edited by bdg2 on Thu Oct 19, 2017 3:47; edited 1 time in total
Router Model: Netgear WNDR3700 v1
Status: Good
Reset: No
Errors: None
Updated from r31544 via WebGUI. I had been holding back from updating from r31544 given tatsuya46's raft of outstanding tickets associated with every subsequent release (include this one), however I considered that the risk was warranted considering that this release includes the fix for the KRACK exploit and the number of unpatched Android and iOS devices I have connected.
After some time of working web interface is crashed on Chromium browser. In the FireFox in the same time the GUI is good.
Please define crashed.
Does it completely die until the httpd process is restarted or can you hit refresh and try again?
There were two screenshots in the same time. Is it not enough? The process still working, I can access the router by FireFox. But in the Chrome browser the GUI is crashed. In the same time.
it's a fix on hostapd, i'm confident it will be in the next build
i'm curious to try this _________________ --
Netgear WNDR3700 v.2 - 26081
Tp-Link TL-WR841N v.9.2- 25934
Will there be a fix for not being able to update from 33375? It seems more people are affected by it in this thread and the previous release.
The bug in 33375 was fixed, but that fix won't get you out of 33375 itself so to get out of that one you have to do some steps as was mentioned on its corresponding thread. Following builds haven't got the issue. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
