SG-5100 can ping, but no internet and long wait for admin webpage - requires reboot
-
I don't know if I have a modem problem or if there is a problem with the SG-5100.
The modem is resetting for unknown reasons. I changed it out with a known working modem.
However, what is odd is that when this happens I can't get the login screen for the SG-5100 admin webpage. Sometimes it takes a very long time, several minutes. Sometimes I give up and power cycle the SG-5100.
When I do get the web page, I have to reboot the SG-5100 to get internet back. This is weird. Access to the SG-5100 admin web page should not depend on the Wan interface access to the internet. I'm accessing it on the local network on the Lan interface. Is this normal behavior for an SG-5100?
Or does it seem like there might be an issue with the SG-5100. When it works, it works wonderfully, but it goes through periods of dropping the internet. I would blame it all on the modem if there wasn't this weird behavior with access to the SG-5100 admin webpages.
Barry
-
@badkins it could be many things, not necessarily hardware dependent.
A. Can you ping it when its slow /not responding? Are replies within a msec?
B. Can you ssh to the box? If yes, what load do you see via top? -
There used to be an issue related to either not having a DNS server configured or having a non-responsive DNS server configured in pfSense that would cause slow response like this. Not sure if this is still the case.
-
@mhab12 said in SG-5100 can ping, but no internet and long wait for admin webpage - requires reboot:
There used to be an issue related to either not having a DNS server configured or having a non-responsive DNS server configured in pfSense that would cause slow response like this. Not sure if this is still the case.
It was last I encountered it. I seem to recall in one case the DNS Resolver service was stopped and several pages in the GUI were super slow, because it was waiting to time out on each individual DNS request. But I am pretty sure I've seen that even if I disconnect the WAN and thus the DNS requests can't get out.
-
I think this might be it (can't reach the DNS servers). I swapped the 3.1 modem for a 3.0 modem I had used for a long time with no problems. So far the problem has ceased. I was actually hoping it would be the modem, but the behavior from pfSense is well uhm, a bug if you ask me. You're trying to work out a problem and pfSense just contributes to the problem.
Well thanks all for replies.
Yes, I could ping. Yes it was a rapid reply. I did not ssh into the box. Once the above appeared to solve the problem I did not want to go back to the old modem since it seems clear (for now) the problem is not with pf Sense.
Regards,
Barry