Other than an update of pfsense actual version, there should never be a reason to have to reboot pfsense.

Common issue where people believe this is the case in change in firewall rules, and not working as they think... This is most likely related to existing "state" for whatever trying your trying to change what happens with. And the reboot clears all this. But if you do have an existing state causing a rule not to function as you believe - you can either kill that specific state, kill all the states or just wait for them to time out on their own, etc.

@kiokoman said in How take out configuration file from corrupted disk ?:

from console if you are able to get there, mount a usb stick and copy the file ?
Thank You for help!

This is the first tough that come in to my head after I push "Post" button in this forum :)

Thanks for that... I had seen the DNS hostname boxes, but must've missed the text below indicating that they're related to DoT. Something might want to be mentioned on the DNS Resolver page at the SSL/TLS checkbox too, that for best security the hostnames for the servers should be entered on System > General.

The entire running config can be backed up from Diag > Backup/Restore.

The file is /conf/config.xml if you're digging through the filesystem directly.

https://docs.netgate.com/pfsense/en/latest/backup/index.html

Steve

Hey all.

I hate to dig up a long dead thread, but I was wondering if this ever got resolved (other than reinstalling Pfsense and restoring from a working config.

Having a similar issue actually on my machine.
Little more background: these issues started with an attempted install of a freeRadius package. It was having trouble, giving similar "assigning address" errors (didn't screenshot at the time. apologies). I gave up, thought nothing of it, and removed the freeradius package and then my pfblockerng dns blacklist started giving me trouble. I restored to a config that I knew was working, but that also did not solve the problem. I've tried reinstalling pfblocker, totally deleting the config, and resetting it up, rebooting the whole pfsense box, and continue to get the same error.

I still could reinstall pfsense from scratch, and then restore that config file, but have there been any updates?

Thank you so much!

Mmm, I agree it seems odd. Have you been able to test it in FreeBSD directly?

If it is something we are doing in pfSense we could dig into it but if it's something FreeBSD does it would need to be reported upstream really.

Steve

Hmm, well if you use Squid/Squidguard to do web filtering I would want to see 2 cores there really, at least.

Steve

After spending time on this that I'd rather have back, I found that the root cause could have been any one or all of the widgets on the dashboard. After removing all the widgets on the source host and then redeploying the "All" configuration on the new host, the issue went away. The crash seemed to be triggered by clicking any link on the UI while the dashboard was present.

Sure you can do that. I've done exactly that myself.

There would be a few things to consider when importing the config. The interface names will be different, em* in VB and igb* on the 2440. When you import the config in the GUI is should ask you to re-assign the interfaces at that point but you should be sure to have console access to the 2440 in case there is still an interface mismatch and it asks you there.

The VB install will almost certainly not have a serial console by default. That should be overridden when you import it to the 2440 but you might want to enable dual consoles in System > Advanced > Admin Access tab.

You should always enable PowerD on an SG-2440 config to get the full CPU speed in System > Advanced > Miscellaneous tab. That obviously doesn't do much in VB.

However restoring a config is pretty easy using the ECL:
https://www.netgate.com/docs/pfsense/backup/automatically-restore-during-install.html?highlight=ecl#external-configuration-locator-ecl

If you manage to break the config sufficiently on the 2440 you can always restore a backup by simply rebooting with a USB stick containing it attached.

Steve