https://forum.pfsense.org/index.php?topic=109778.msg611744#msg611744 https://forum.pfsense.org/index.php?topic=8640.msg48501#msg48501

Chris: Thanks for the feedback. When I loose connectivity with the ISP it shows up in the gateway log and the graphical display with 200ms.loss.The system can go for hours and then we have the issue every two hours. I am a gold member and really like Pfsense. It been a big learning process for me. I though nginx might be causing thse gateway burst disconnects. I will take you suggestion and make the changes. I am sure the many issues will be resolved. We all need to be patient. Best Regards, Howard

No problem, I know the feeling when something that should be easy, just stares at you….. Just for an off hand diagnostic test, it might be worth trying a 2.2.6 (or <gasp>even 2.1.5) load on the box. FreeBSD has undergone a number of updates that show up in the pfSense revisions. Could be a quick test to pinpoint where things have gone awry.</gasp>

FYI - to close the loop, found the install at /usr/local/bin. Thanks!

The stacktrace seems to mention havp package. Perhaps some leftover files?

"Its the only port permitted directly out of work" That sure wouldn't be standard now would it.. Openvpn bounces off a proxy just fine by the way..

I used winscp to connect via SCP and used the command windows to execute "pkg update" but it does nothing. Says everything is up to date, yet I can't check packages or check if there is a system update.

I would wait.

In reading that it makes sense.  I remember 2.1 -> 2.2.  duh!  on me.  lol With that said, would upgrading a Backup pfSense with CARP have issues then?  An example; after upgrading my Backup pfSense with CARP configured it stalls at 'WARNING: / was not properly dismounted' and sometimes 'dumps'.  When it reboots more often than not I get 'WARNING: /: mount pending error: blocks {numbers} files {number(s)}' then just sits there and does nothing.  Thought it was hardware or config related but using different hardware (same hardware specs) and even different backup config it does the same. Is CARP causing an issue? Thanks for your input!

I've completely removed pfBlockerNG (and all other packages) and still having lockup issues. Obviously not pfBlockerNG issue.

Hi, @dusan: You may want to have a look at https://forum.pfsense.org/index.php?topic=110070.0 thanks a lot for that hint! As suggest I removed the IPSec dashlet - that's ok for me, I don't need it. No problems since then!  :) Greets Stephan

Have you checked: https://forum.pfsense.org/index.php?topic=110043.0

Thank you. I'm not worried about the disk space; just wanted to ensure when I re-install, everything will be reinstalled. I've already cleaned out the cron tasks.

I don't know what's happened but this problem (very slow GUI until rebooted) has gone away after I did a bunch of reconfiguring and cleaning up this morning.  Since the problem seemed related to editing the firewall rules I deleted everything including the NATs and re-created all of the rules from scratch using exactly the same incantations In the process I also moved the main Internet feed from Igb3 to Igb1 - the LAN side has always been on Igb0 with another Internet feed on Igb2.  Igb1 used to be the main feed a while back but we changed providers and configured the new ISP on Igb3 - so for a while we've been running with internet access via Igb2 and Igb3 without using Igb1 at all - that's the configuration that was giving us problems. The response time is now sweet and so far everything is running well. So these are just questions for the developers to think about 1. Is there something magic about the interface called "WAN" that REQUIRES that it is present even if the firewall rules and configuration do not use it? 2. When an interface is deleted, what happens to the rules associated with the interface?  I think they get left in place but since there's not interface associated with them you can't see them.

Thanks your further help and fast response. Followed your instructions to apply the patch.  Got the error "Patch can NOT be applied cleanly", which I noted, then continued. The patch works, the checkbox "Disable automatic dashboard auto-update check" does now stop WAN activity on dashboard page refresh, and can be toggled,  which then results in  WAN activity and I assume  allows the auto update to take place. I've only done brief testing and not checked for anything else affected, however it looks like the fix is OK here. J.

+1 for Rufus, works with every single ISO I've used it to put on a USB drive and boot/install from. Clonezilla, centos, xenserver, windows 7, etc etc. Dead simple to use to, just choose iso file and click go

That fix was merged, it'll be in 2.3.1.

Nope.  Something wasn't updated to change the installation screen back to the dashboard.