Config settings from older versions of pfSense are automagically upgraded/converted as needed when the old config is restored to the newer system and the system reboots. You can even come from a 1.* config or an old m0n0wall config.

Yes, if you gitsync or wait for the next snapshot or manually put the latest /usr/local/www/system_advanced_firewall.php onto your system it will be fixed.

PR has been merged. So this will be fixed with a gitsync or the next snapshot.

@Dustin:

Submitted to redmine. Bug #7213

Great, thanks for posting. I'll be watching for the response.

@oben:

Not everyone is interested or motivated enough to get into the software development system. I have an account here that I relay pfsense related things.

I don't want to create another account to add to the hundreds needed these days.

You would think that there would be one company person who could relay these things to the right people or system to bring it to the attention of them.

The thread I posted has all the info I can provide and posting it on redmine wont make it suddenly more detailed than what I have posted here.

What is the sense in duplicating my efforts?

Is the forum here just to frivolously talk?

Please don't shoot the messenger.  The official way of reporting bugs/issues/feature request is via redmine.  BTW That is not the software development system, its a database for tracking bugs.  The forum is for support and should be used to ensure that issues are verified before going into the bug reporting system which you did.  You need to take the next step if you want the bug to be resolved.  If you don't want to use it, that's fine, but don't complain when your issue isn't fixed.  In the time it took you to post the above in two separate threads, you could have had a new issue posted in redmine.

I guess when it comes down to it, if you want to run the betas and want to get things fixed then you have an obligation to use the tools/processes provided to get those bugs fixed.  If not then maybe stick to the release versions.

@oben:

Not everyone is interested or motivated enough to get into the software development system. I have an account here that I relay pfsense related things.

I don't want to create another account to add to the hundreds needed these days.

You would think that there would be one company person who could relay these things to the right people or system to bring it to the attention of them.

The thread I posted has all the info I can provide and posting it on redmine wont make it suddenly more detailed than what I have posted here.

What is the sense in duplicating my efforts?

Is the forum here just to frivolously talk?

Maybe just create a bug report on Redmine & link it over here if you don't have the time to copy everything over?

Has anyone had any luck running squid without it causing massive load and extremely slow responses?
From my experience with squid on the SG-1000 I'd say it's not usable - unless you are on dial up.
I'm toying with the idea of using a Pi3 for squid etc. and just keeping the SG-1000 as the firewall (which it's doing really well)

From the latest version that I just upgraded to:

[2.4.0-BETA][root@pf240.localdomain]/etc: cat version.lastcommit 5ea71ebda681dbab323ccdb44ab3bfdea7c0f5d6

https://github.com/pfsense/pfsense/commit/5ea71ebda681dbab323ccdb44ab3bfdea7c0f5d6

And that takes me to the commit.
The commit id should always be one that is a commit in master (or RELENG_2_3_ branch. and those commits should exist "forever".

I removed the entry in loader.conf.local and rebooted.

After days of no restarts at all it decided to reboot at 4am this morning. The log says the root user did a restart 15, whatever that means.

It's been running for the last few hours without a panic though and I'll leave it running for a day or so.

Tim

Is it possible, Yes.

Is it advisable?  No, You really don't want too much to be saved, the more hard disk space the more ram you use.  The more ram you use the slower the device will be.

In general terms.

Might be fixed now: https://redmine.pfsense.org/issues/7149

Clean install with ZFS works now on recent snapshots. Installer hung after selecting reboot but after killing power it booted fine. First boot came to mountroot prompt but was able to load zroot manually. Added kern.cam.boot_delay="10000"  to loader.conf and it loads after every reboot.

I hear you on the not having a console - if it had actually rebooted then I'd have been able to see the console (it's on some kind of timeout and never comes back) but the web interface said it was done and was rebooting…  I'll have to look into that some more when I get time.

Something like that yeah.. With happy ending and some 'travarica' on the end, you get it doc 😁

Development snapshots are always of the community edition (CE). The official versions for your hardware should be available when 2.4 is released, or shortly thereafter.

Thanks re igb. As I mentioned it has locked up once since back on 2.4 (did not crash for 1 week on 2.3.2). I have just re-enabled some stuff so I want to see if it goes down again. If it does and there is no log or other info I will try your suggestion but just waiting to see if it crashes with the other settings re-enabled…

Cheers