pfSense 2.6 wan drops
-
I hope someone can help me solve a frustrating issue with pfsense that started with 2.5 a few weeks ago that still exists after 2.6 upgrade. I would get random internet drops but it would come back on in a few minutes, 30 minutes at most and it would happen a few times a day. Now it happens once every other day but does not fix itself. I have been using pfsense on Qotom mini since 2019 and have had few problems. I am not a networking professional and sometimes it can be a challenge to get things working. I recently upgraded my Xfintity broadband to At&t gig fiber that included a At&t BGW320 that I am doing passthrough on since ONT is integrated. I also swapped out my Qotom for same J3160 mini that Protectli sells as the FW4B for almost half the cost via Alibaba and Nanling. I added a 8gb ram and 64gb msata drive.
My set up is three wired lans, one for home PCs, wifi and various devices, a second for a Blue Iris ip cam server, a third for Helium hotspot miner. I have an TP-Link Omada OC200 controller and three eap225 access points for wifi. Wife and I both work remote and our son streams his gaming on Twitch so lots of need for reliable internet. I have a rack server in my basement with dumb switches to mange it all.
Here are my issues and questions. First of all, after setting up fiber modem and turning off all firewall and wifi features of BWG320. I have this showing in pfSense
My public ip shows as WANGW and when searched but I have another WAN_DHCP address that is different. I have been having WAN drop out and get dpinger error 65. I am not that good with reading logs or know all the terms used in these forums. I have turned off ip monitor actions on both WAN ip's in routing. I added a Cronjob that one site recommended. I changed ip being monitored to 8.8.8.8 on WANGW and 1.1.1.1 on WAN_DHCP. The other suggestion I don't know how to implement, see below. I woke up this morning to internet being down since 3am and restarts of ONT Gateway and pfsense did not fix. pfSense went into panic mode and would stop on loading wan then screen would fly by so fast you could not read it. I followed instructions to fix issue in the shell in single user mode.
How do you install this below I copied from another site?
I found that the true issue was caused by a missing directory (/var/run/dhclient) creating this directory as the admin user ( mkdir /var/run/dhclient ) with the default rights also seemed to do the trick for me, I commented out the inital crontab, but ofcourse you can decide which of these two routes you want to go.
All very frustrating. would appreciate any advice given in layman's terms. Thanks in advance for taking time to read my rant.
-
One of those WAN gateways it probably left over config from an earlier setup and should be removed. I assume it's WAN_DHCP since it appears to be working with WANGW as the default.
Do you have the System IPv4 gateway set to automatic still? If so it's probably switching to the bad gateway and not switching back unless it all goes down.
You should see the default gateway switching in the system logs when it happens though.
Steve
-
Thanks for the reply. I had default set to WANGW not Automatic. Instead of deleting other WAN entry, I disabled it first in case it quit working. I seems fine.
This morning my internet went out again. I went into pfsense console because when this happens I cannot reach pfsense gui or gui of At&t fiber modem. I can see in At&t app that i am online. Pfsense shows a my public ip but no internet. I am not good with reading logs. Not sure which to look at and then how to decipher. I did just add syslogng package so can send logs remote. I rebooted and did file check in pfsense, reloaded prior saved configuration and robooted fiber modem and finally the internet came backup. I dont know what is happening to make it drop or come back up other than multiple reboots. Very bad issue since we both work from home. I appreciate an advice you might have. Especially on how to diagnose problem.
-
If you're unable to reach the pfSense webgui that sounds like either an issue LAN side or some routing conflict, like maybe your modem lost sync and came up with an IP the same as the LAN subnet?
Did you try connecting out from the console directly?
That's what I would do, determine exactly what is failed so:
Check the interface addresses, at the command line:
ifconfig -a
Try to ping out by IP address and by fqdn.
Check the routing table:
netstat -rn
Steve