Can't load Web GUI when WAN is down
-
One of these :
euh .... back-off !
-
@Gertjan - Interesting I don't have that ?
-
You showing the Advanced option for the DHCP IPv6 client.
Just above you have the DHCP Client Configuration option (IPv4).
-
@Gertjan - I don't have the IPv4 option or should this be under the PPoE settings somewhere?
-
@Gertjan
DHCP Client Configuration" and check "Advanced Configuration".
Here you can try some time delays.
Like the hold-off when the modem because unreachable after an ISP outage, and re creating the connection takes minutes, to long for the pfSense DHCP client - or give a list with IP networks it should not accept ( typically, RFC1918 )or in the other way round, when a cisco cable modem not getting
an officical IP it hands out a private IP to the WAN If of pfS
so am I gettin this right I can block this IP-Range anda) WAN shows offline as long as no other (not blocked IP ) reveived
b) pfS still tries to get an IP on the WAN port (sends request to Modem)cuz its monday i prefer to talk first then test and cut the wire ;)
brNP
-
-
Correct.
You just mentionned some new, cruicial info.
You're not using DHCP (IP4v).
You're using : *
PPPoE.
That one tries to connect itself using a indefint loop.
It will try, and failed, pause 10 seconds, try again, etc.This protocol implies that the upstream modem re connects itself, so that 'PPPoE' works.
But something failed to connect.I've been using PPPoE myself for years. Don't recall much issues, although it's a "protocol over a protocol". All or most depends on the modem used, the ISP - and more factor you actually don't control.
Except one maybe : hook up to an UPS both pfSense and the modem.edit :
@northwarks said in Can't load Web GUI when WAN is down:
I just noticed I have an idle timeout in PPoE
Don't use that one.
It exists for ancient reasons : have the connection drop if there is no traffic ant more. usefull when people apid for every bit they send and received. It's all flat based they days, this option isn't really needed any more and doesn't bring a solution for you. probably another problem. -
So another outage early this morning, resulting in yet another power reset of the box, I can't access the GUI, doesn't ever load even after 30/60/90 seconds.
It responds to a ping, my network monitor box is seeing snmp as up and no data passing. I can't SSH into the box but port 22 is up, it just times out.
As this looks like an issue related to DNS what can I look to add to the settings to get the 3100 to timeout and give me GUI access?
-
System > Update > Update Settings > Disable the Dashboard auto-update check
-Rico
-
really ... awesome !
@northwarks plz keep us posted brNP -
-
@northwarks said in Can't load Web GUI when WAN is down:
I can't SSH into the box but port 22 is up, it just times out.
Insist on having this one working.
The ssh is as important as the GUI.ssh is running ?
ps ax | grep '/sshdListens to port 22 ?
netstat | grep 'ssh'Connect from LAN, the default firewall that (was), there permits the access.
-
So an update, after a week of issues I've narrowed this down to pfBlockerNG-devel/DNS issues. I've removed pfBlockerNG-devel and reverted to AdGuard Home and I've had a stable WAN connection and box for 3 days. I did notice this and wasn't sure if that was a contributing factor:
https://www.reddit.com/r/PFSENSE/comments/88wg6g/issue_with_pfblockerng_dnsbl_and_cloudflares_1111/
@Rico - I made these changes and it made no difference when DNS was down or been blocked by pfBlockerNG-devel
So thanks all for the help and pointers, all really useful and I defiantly improved my knowledge of PFSense and DNS over the last week!
