No worries. It is a legitimate bug. You should just be able to import it. But because it's already fixed it's unlikely to see much traction in 2.7.2. At least there's a relatively easy workaround. 😉

@mircea-manea The NDI changes if you change NICs. If you contact Netgate I believe they will move the license, possibly a limited number of times.

Or remove the NIC...

Hmm, so what changed? Were you using the non-serial memstick previously?

It depends what OVH wants.

1:1 NAT is useful if one that one host will ever use the IP address. Just remember there are no firewall rules added automatically. You need to add rules for everything required.

@stephenw10

thanks for your support.

I install it from scratch and import the config and it is working fine know.
I don't know what was wrong.

my advice to everyone is that to make daily or weekly backup at least if you don't change the config a lot to save your life .

Same here. Thank you @jimp

That's how Hyper-V works. You need 2 External switches.

If we summarize the three modes of Hyper-V switches are capable for:

External switch: It links to a physical card of the Hyper-V host and enables network access.

Internal switch: The switch isolates the VM but enables network switching between the Hyper-V host and the VMs.

Private Switch: It completely isolates the network from VMs.

EDIT - Don't confuse Internal/External with LAN/WAN.

Yesterday, I installed the stable version of pfSense on the stable version of VirtualBox without any problems. Apparently, a bug has been fixed

You might be running into this? https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-shrink.html

Yes, thank you and Stephen, I see I can recover almost 6GB of space.

@hockeyfreak said in Really confused about upgrade:

I would be tarred and feathered

Ha best avoid that then! And yes reinstalling is the better option here if you can. 👍

@stephenw10
Fun is more positive than my reaction!

@HansWerner3dit said in No packages in available packages list:

I am not skilled enough to restore the current setup from scratch [Wireguard, WAN Backup, Gateways, VLAN, DHCP6

You are ^^ and it's easy to understand why.

Always keep a recent copy of the pfSense config : Diagnostics > Backup & Restore When you re create or re install pfSense on the same device (same hardware, or to be more precise : same network interface NICs) then all you have to do is : import the pfSense config (same place Diagnostics > Backup & Restore), and your setup is done.

Example, one or two versions ago, the filesystem changed. This means the partitions on the drive being used have to be altered. A simple GUI or console 'upgrade' can't do this.
You need to get the firmware on an USB drive and see pfSense Documentation, look for the word 'Etcher'. Also find the doc about installing pfSense with 'ZFS'.
When pfSense starts, do a minimal WAN/LAN manual config.
Ones in the GUI, import your backed up config.
Done.

Updated four to 24.11 yesterday and all four ran into this. All I had to do was wait 3-10 minutes [depending on device speed?] until the message disappeared upon refreshing the page. I noticed the log shows the time gap:

Feb 4 19:49:24 pkg-static 47515 pkg upgraded: 1.20.9_1 -> 1.21.3_4 Feb 4 19:42:38 check_reload_status 759 Syncing firewall Feb 4 19:42:38 php-fpm 5569 /pkg_mgr_install.php: Configuration Change: admin@10.x.x.x (Local Database): Saved firmware branch setting.

The upgrades seemed normal after that.

@stephenw10 Thanks again, I so appreciate you taking the time!

And I'll comb through the XML file next.

You can install old pkgs but, as I said, you must set the repo to running version before doing so. If you do not it will probably pull in pkgs from the wrong repo and break the install.

@Snailkhan said in Unable to retrieve package information.:

The phones use SHA1

Can you elaborate on that? I assume you mean they use a VPN of some sort?

To be fair here pfSense's handling of filled disks has never been good. But the new ZFS upgrade process is way better in that respect.

@patient0 said in DEC740 Desktop Security Appliance - Cannot proceed with installation of PfSense:

@logan5247 said in DEC740 Desktop Security Appliance - Cannot proceed with installation of PfSense:

Hey, how is the DEC740 working out for you? Wanted to get an opinion before I drop $800+ on this thing

I'm pretty happy with it, I did have to upgrade to pfSense Plus. Have to try to remember why :/ ... I think for the support of the 10G ports.

Performance wise I get about 5-6Gbit iperf3 out of it on my Fiber (not PPPoE), no IDS running.
I would compare it to a Netgate 6100 MAX (don't go for the eMMC based models) which may give equal or better performance.

Thanks for sharing!

This is a FANTASTIC group! I followed directions which was to complete the interface assignments during setup, let my backup install (which was added at time of install) and my 2nd -NEW- box is up and running with 2.7.2 without any apparent issues! I have not swapped out boxes as of yet, but the main idea was to have a redundant box on standby incase of hardware failure etc. THANKS!!

Ah, that's probably just the gui device list lagging the driver.

https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/includes/functions.inc.php#L340

You could try adding the ID(s) there as a test.

@stephenw10 My system is back-up and running as the main firewall, but I am happy to help in figuring out or gathering any useful information.