192.168.1.1 is your modem/router in front of psense or like in your netwrok map "in the wall", right ?
192.168.1.1 is the IP of the box running pfSense. The IP I get from the wall is a normal ISP-type IP, 85.XXX.XXX.XXX (hiding it for obvious reasons).
Do you have high latency or packet loss on this WAN connection ? You could try to increase the "high latency to 500ms - 800ms and the packet loss to 30%-50% and member down to 20s - just for testing.
I've had to turn apinger off completely. The reason for this is the time issue I've posted about in another thread
. pfSense's clock runs entirely too fast, so apinger is constantly thinking the WAN interface is down. It was causing filters to reload nearly every second, disconnecting me from everything all the time. (At least, I think that was the issue.)
However, speed/latency tests I have done (bredbandskollen.se and pingtest.net) show a latency around 0-20ms, and little to no packet loss.
Further if you do not have any connection to the internet, can you ping something on the net like 184.108.40.206 and 220.127.116.11 ? So is it just a DNS issue or something else.
Last time this happened, I was unable to ping 18.104.22.168, which is what I tried. I couldn't ping it from my computer or pfSense's web GUI.
Rebooting the thing fixes the problem. Though I'd rather not have to reboot it every day.Edit:
I found I was being bombarded by the same IP on the same port at the time of the disconnection. The IP was similar to mine, and I'm unsure of whether it's malicious or something my ISP is purposefully doing.. Interestingly, it was an IP that I could ping and get response packets from, rather than just packet loss.Edit #2:
I'm beginning to suspect that this isn't a fault with pfSense, but that something's going horrendously wrong at my ISP. I can connect to and ping other computers within my /24 block.