PfSense randomly stops passing traffic
-
I'd been using m0n0wall for awhile without issues, then at random times I'd be unable to get any traffic out from my LAN - no one could browse or anything else. The only clue I found in the logs was "dhclient: No working leases in persistent database - sleeping." Rebooting my cable modem did not help, rebooting m0n0wall did not help. I had to do both to fix the issue. I tried swapping my WAN and LAN interfaces but it did not help.
I decided to try pfSense so I installed it on the same machine. This morning I again could not browse so had to reboot the cable modem and the pfSense machine. Maybe my cable is going flaky. Can anyone help me diagnose? Should I try another computer as my pfSense box?
-
It could be a problem with your hardware, since you used the same hardware there's no way to rule that out. It could also be a problem with your cable modem.
I would start by trying a different computer to install pfSense on.
-
@Cry:
It could be a problem with your hardware, since you used the same hardware there's no way to rule that out. It could also be a problem with your cable modem.
I would start by trying a different computer to install pfSense on.
Installing on a different machine did not help. After more Googling, I see others having this issue. Based on what I've read, I added a cron job to renew the WAN DHCP lease every 15 min. So far so good…. I'll update this thread if I come up with anything more worth sharing.
-
Presumably it's specific to your ISP since it if was specific to pfSense this forum would have been flooded with other posts (and I wouldn't have been online for a long time).
-
@Cry:
Presumably it's specific to your ISP since it if was specific to pfSense this forum would have been flooded with other posts (and I wouldn't have been online for a long time).
Could well be - I use Time Warner cable with a dynamic IP. At work I have Time Warner with a static IP and have had no issue. The cron job seems to have fixed the problem for me and others. I'd be glad to provide more details to anyone interested in looking into/correcting the issue.
