PF sense crashed after upstream ISP upgrade . Fixed but , working strangely .
-
It could be co-incidence, maybe not, however my PF sense crashed , at the same time ISP (Virgin Media) decided to give me a free upgrade (from 100Mb to 400Mb) . The night before the stated upgrade time , my internet becomes unstable, it suddenly went off after successive reboots it would come back for 20 seconds to 1 minute , then go off again .
The following morning , the PF sense became stuck in a boot-loop . After some inspired Google- Fu, I applied the following fix
"boot as single user mode, after give the command in prompt
/sbin/fsck -y -t ufs /"
The PF sense is now back to life, and provided a crash report for some great bedtime reading but , strangely I cannot get internet to the LAN devices ( even after many reboots ) . The PF sense itself can ping DNS names but confusingly the LAN devices can only ping Internet IP's but not DNS names .I tried adding DNS addresses to the two already inherited from the ISP (8.8.8.8 & 8.8.4.4) however this made no difference .
I dont know what else to try , apart from reset and build out again . Any ideas would be appreciated .
-
@90ninety If you use DHCP then make sure your LAN clients have an address, gateway and DNS for your LAN and not an APIPA address. Can a LAN client ping 8.8.8.8? Can a LAN client resolve www.google.com?
-
@kom said in PF sense crashed after upstream ISP upgrade . Fixed but , working strangely .:
@90ninety If you use DHCP then make sure your LAN clients have an address, gateway and DNS for your LAN and not an APIPA address. Can a LAN client ping 8.8.8.8? Can a LAN client resolve www.google.com?
The LAN clients get ip addresses from the PF sense DHCP server , within the range set (192.168.1.xx/24) , IPconfig/all shows the DNS address of windows clients as the PF sense '192.168.1.1'
LAN clients can ping 8.8.8.8. or External IP's ( across internet ) but cannot ping addresses for example 'google.com' or 'msn.com'
The PF sense can ping address names 'Google.com' and 'msn.com' ect . -
@90ninety Ok so then your problem is specifically DNS. How is your DNS configured on pfSense?
-
Mmm, when you test from Diag > DNS Lookup do you see a response from 127.0.0.1?
If not is Unbound or DNSMasq actually running?Steve
-
@stephenw10 said in PF sense crashed after upstream ISP upgrade . Fixed but , working strangely .:
127.0.0.1
It was a DNS issue , the PF sense had been inheriting DNS from the upstream ISP ( Virgin ) . There is something wrong since the upgrade with DNS , working with PF sense .
I re-entered DNS addresses 8.8.8.8 & 1.1.1.1
I changed the DNS settings , to and unchecked " DNS to be overwritten by DHCP WAN"
I then set DNS Resolution Behavior tp 'Use local DNS , and ignore remote DNS "
Seems to be working again now
