Managed to do it, merged snapshots, mounted in windows, used an EFS file explorer, found original config was 0bytes, used a backup recurring file, restored config - all back up :)

Thanks for your answer.

I will check it when the new device is delivered.

I have managed to export/import most of the configs that I need from the old one to the new one, so I'm not too worried about this problem anymore.

Thank you, I disabled the corresponding trigger in Zabbix.

I read that same reasoning would apply, in general, to computers with SSD. Better have plenty of memory.

A ticket for older release? https://soft.uclv.edu.cu/pfSense/ Thank you Google for helping us out!

Guys,

Mystery solved.

All my fault, plus assistance from the H/W manufacturer ...

Seems that port0 MAC ended :0b and port1 ended :0a, so I basically had them labeled the wrong way around. PfBlockerNG was set up on the 'outside' port, hence what I was seeing.

Like I said - all my fault, but I'd still love to have a minute with the olympic class ^%$ head that designed it this way.

Hope someone else benefits from this experience.

Chip

pfSense.

-Rico

Hi,

2.4.1 ? The one from 3 years old ?
That's dangerous. Security wise - and from the fact that installing a simple package that contains core lib upgrades (PHP7.x etc) can break everything.

You executed step 0 : a boot just before starting the upgrade. https://www.netgate.com/blog/pfsense-2-4-5-release-now-available.html
Any issues at this point will indicate bad starting position ... like a hosed file system.

Step 1 was : you backed up the config.
Don't bother repairing, take the short cut that will help ou out in 5 minutes : download a copy, build the bootable USB stick and install "from scratch". Activate WAN by hand using the GUI. Import settings. Done.
See the manual for the entire procedure.

Resolved the issue. I had to reset the trunking for the NIC after upgrade. I have no idea why an update inside of a VM would affect the network configuration of the VM in the host, but the following command fixed the issue:

Get-VMNetworkAdapter -vmname "pfsenserouter" | ? macaddress -eq "<mac address of NIC used>" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-1000" -NativeVlanId 1

Got the password reset. Thanks for the assistance. Very much appreciated!!!

Thanks. I did some searching and I wasn't the only one to get this problem. I use a cookie manager and can't see any cookies I could associate with Netgate, but I'll check my firewall logs for outgoing traffic. I don't exactly know what FF means by 'Private Browsing', but my Chrome has all its leaky vanilla defaults and that didn't provoke the same login error.

This thread didn't seem to get much discussion, but I'll give his Clone*illa method a try although I expect it will be slow writing to a USB flash drive, although my Pfsense isn't huge. IMHO the only safe backup/restore after a disc, OS, or mini pc crash is a sector copy image. When you have used Microsoft OS as long as I have you learn.

https://forum.netgate.com/topic/97141/dirty-how-to-cloning-pfsense-hard-disk/2

I'm reassured my previous xml settings backup worked for this update, but might no assume the same miracle for 2.5.* Using a data file as a recovery source won't work if the disc format or files it was written for are incompatible. Maybe one day an api to clone a Pfsense box to an external drive and restore from it could be built in? A small part of a recovery routine can sit on a hosts protected partition (which a fresh install won't reformat!) whilst the saved image and the rest on an external usb drive, flash or other?

Thanks again for your help.

@Rico Hi Rico,
Thank you.
I tried changing the LAN IP from the web configurator but that just locked me out.
I reset to factory default from the CLI set it up again and everything is working fine now.

@prfoks perfect solution. You are superman bro. Thank you

Hello again,

Thanks for the replies. You have some very valid concerns there Rico, and I totally agree.
However this kind of feature sounded good to me as I was thinking in the lines of the MSSP business.
Not for businessclients, but for customers at home that needs help to secure their own environment.
The easier this is for the end-user the better in my opinion, but loading the correct config before shipping as teamits suggested solves this.
That removes the complexity and risk of having a secure deploymentenvironment that also can fail :-)
Thanks!

-Øystein

@hawkbh said in PFsense logs are not being stored:

@bmeeks said in PFsense logs are not being stored:

Okay, just to be sure I am clear on your symptoms --

When you go to STATUS > SYSTEM LOGS and click the System tab, do you see logs then or is that screen also blank?

What your screenshot is showing is that Firewall logs have been selected. There are at least two reasons you might not have firewall logs. One would be you don't have any rules selected for logging; another would be you have accidentally clicked the option to disable the packet filter (and thus the firewall engine).

Post up a screenshot of some of your firewall rules from the FIREWALL > RULES menu.

The physical log files exist in /var/log on the firewall. You can see them either via a direct console connection or remotely via an SSH connection.

Thank you buddy. Now it's working!

Good deal. When I submitted my reply above I was for some reason thinking you had already tried the Reset Log Files button without success. Otherwise I would have mentioned it. Reading over your posts again showed that you had not tried that, so my bad for overlooking.

@jimp caught it, though!

https://forum.netgate.com/topic/152551/downgrade-from-2-4-5-to-2-4-4p3

-Rico

Internal scan is only if your service provider... And you sure and the hell do not need to make the web gui of pfsense available on the networks that are involved in the PCI..

For example - we are service provider, we host stuff that is PCI for customers... We don't need to scan the management vlan, only need to scan the networks that are directly involved in the processing of the payments..

We are not scanning every single network in the company... You only need to scan the network related to your pci environment.. If your switches and or routers and firewall interfaces are available on your pci networks - your doing it wrong!

Try disabling UEFI boot on that last screen, see if it helps.

Glad you have it working now.

-Rico