Ok. So that gives me a fresh install with the complete configuration and rrd data restored. Packages are referenced in the configuration but not installed after this, right? In the documentation in https://doc.pfsense.org/index.php/Configuration_Backup_and_Restore it says: 'This page also contains two useful package functions: Reinstall Packages: This button initiates a re-installation of all currently installed packages.' That sounds promising but I can't see this (pfSense Version 2.2.6). Is the documentation outdated or is this feature available starting from pfSense 2.3? If this feature is available: After a fresh install with an old configuration file would I be able to reinstall all packages from here which are referenced in the configuration? -flo-

No worries, in return, a thank you to all involved for the awesome work on the project.

https://forum.pfsense.org/index.php?topic=109513.msg609705#msg609705 an untagged vlan means the client (in your case pfsense) is unaware of it, and shouldn't need any configuration

That's exactly the sort of changes I was expecting! The "pfSense-compact-red.css" theme is not perfect (yet), but is a great example of what is reasonable to accomplish with the new 2.3 structure. Dare I say you're going to need a "Web-GUI-Themes" forum some time soon? (probably jumping the gun…..) Kudos on 2.3, again!

Thanks everyone the issue has been solved.  It was the USB flash drives, possibly in conjunction with the application I was using to make the installer. That YouTube video was an eye opener and I also used rufus. I have always used unetbootin with success plus Kingston USB flash drives.  Not sure why it started failing but now that I have switched to a 4GB verbatim drive I had kicking around and everything works 100%.

@naniam: – Miss the old RRD graphs. The new method works and is interesting but requires a constant changing of parameters to get what I want whereas before I just viewed an area and had everything. The RRD Graphs were one my most used features and gave me quick overview on the installed system. The new way of displaying data is completely unusable, ugly and missing lots of data, that were available before. Please rework this anoying hipster failure.  >:(

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