#2588 closed (invalid)
SVN revision 19342 - QoS Port Triggering Crashes HTTPD
| Reported by: | BergRD | Owned by: | |
|---|---|---|---|
| Keywords: | QOS, Port Triggering, HTTPD | Cc: |
Description
Upon trying to enter more than 2 entries into the QoS Port Triggering setup Save or Apply Changes simply returns with an error page and verbiage
"Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data."
This occurs with Chrome, Firefox and IE and subsequent refreshes of the page fails with a server not found error. Logged into SSH to find the HTTPD process was missing. Spawning the new daemon I'm able to get back into the router web GUI but the QoS settings are unchanged.
If left unattended the HTTP Daemon does restart after few mins but still unable to modify QoS Port Triggering past 2 entries.
Attachments (2)
Change History (10)
Changed 12 months ago by BergRD
Changed 12 months ago by BergRD
comment:1 Changed 12 months ago by BergRD
comment:2 Changed 12 months ago by BergRD
- Summary changed from r19342 - QoS Port Triggering Crashes HTTPD to SVN revision 19342 - QoS Port Triggering Crashes HTTPD
comment:3 Changed 12 months ago by fractal
I can confirm this same problem on the Buffalo WZR-D1800H as well.
-Fractaql
comment:4 Changed 11 months ago by BrainSlayer
- Resolution set to invalid
- Status changed from new to closed
i cannot confirm it and the screenshot shows a invalid setting. the last entry is empty and invalid
comment:5 Changed 11 months ago by BrainSlayer
and beside this its no qos setting. its port triggering
comment:6 Changed 11 months ago by BergRD
I'll get you a different screenshot if you like and the second screenshot is the result of trying to add the 3rd entry into the Port Triggering. You are also correct it's not QoS and I generalized that into this ticket so my apologies.
I enter the 3rd entry, set the 2 ports for each the triggered and the forward areas and enable it. Upon Save or Apply you get the error response the server did not return. Upon the HTTPD restarting or starting manually the 2nd screenshot is what you get back.
Invalid resolution or not it fails. Forgive me if you cannot confirm it but just ask and I'll try to get you what you would like to confirm it. If not, I'm sure you have other pressing issues just wanted to do my part to support but from this point forward I see now it may be frivolous. Thanks.
comment:7 Changed 11 months ago by BrainSlayer
solved in r19363
comment:8 Changed 11 months ago by BrainSlayer
i will place a new build soon within the forum
Forgot to add this is a Netgear WNDR3700v1.
Flashing procedures: 30/30/30 tftp factory-NA 30/30/30
Repeated twice to ensure it flashed properly and rebuilt nvram.