Nice 👍

@johnpoz Hello and thanks for your message,
Thank you very much for your message and the time you took to answer.
Finally, I decided to remove the ClearOS box and connected PFSense directly to the modem/routeur and it worked.
Thanks again for your time :)
Best Regards

@stephenw10 said in Dashboard unable to report current version.:

In 2.7.0 run: certctl rehash

Then recheck.

Thanks! That fixed the issue.

It's already fixed though, just waiting for the next release.

@stephenw10 I know that recommendation. I did the upgrade from the serial console and it also failed.

The beta7 installer?

There is a newer installer available if so. But you can also just try the legacy installer images.

Good day, @stephenw10

Thought I would put the period on this post.

I used the "pfSense-CE-memstick-2.7.2-RELEASE-amd64.img.gz".

I was able to connect via the serial cable during POST, catch the BIOS and enable USB booting. From there, everything has gone very smoothly. I'm very happy with the hardware and software. I have several Noctua fans, 16 GB of DDR4 ECC RAM and a i7-7700T CPU heading my way after reading this epic forum ballad.

This seems like a really great forum and I am grateful that such a altruistic resource is available, and well moderated, for professionals and home-labbers alike. Thank you all!

@jc1976

You saw all the other recent (last 24 hours) 'pfBlockerng' and 'pfblockerng-devel' forum posts ?

@stephenw10

Many thanks for the post. Reinstall and restore worked a treat. Life saver😃👍

That will only be valid for a week but you can always open a ticket to request the current image.

@doncarajo and @stephenw10
I would like to thank you both for your assistance. My pfSense router is now up and running.

Indeed it should look like:

[2.7.2-RELEASE][admin@t70.stevew.lan]/root: pfSense-upgrade -d Messages: Your TAC Subscription expired on 2023-07-08 05:00:00. Please renew your TAC Subscription or purchase a pfSense+ subscription by visiting the <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a>. >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ......... done Processing entries: .......... done pfSense repository update completed. 550 packages processed. All repositories are up to date. Your packages are up to date

You may or may not have a message in there. That test instance previously had a TAC subscription.

You alsomost certainly want a 2.7.2 memstick image. If that device has a serial console use the memstick serial image otherwise use the regular memstick image for a video console.

@stephenw10
Many thanks, I deleted old Boot Environments and upgrade to last version is O.K.

I encountered an issue with my DNS settings, but surprisingly, my internet connection was still functioning. After resolving the DNS problem, I noticed that version 24.03 was available as an upgrade. While I'm aware that the 3100 model has reached its End of Life (EoL) status, I'm not particularly concerned since I don't use any of the packages that are no longer supported.

Thanks for the assistance.

@Gertjan Yup I setup CRON to run every night.

That's a different issue to the problem the installer in VBox. Though the error message may be similar.

@veptune said in PfSense : i get "cannot connect to installer daemon" when the install begin:

cannot calculate the system NDI
failed to load the system settings

Ah, OK. It has no NICs it can even read the MAC address from. So, yes, you would need to add some NIC to allow that.

What is the NIC in that?

@stephenw10

Thanks for getting back to me so fast, for some reason on options in the menu worked and all external connectivity was lost.

In the end, I downloaded the pfsense installer from Netgate and did a clean install, which seems to have solved everything and kept my config intact.

Thankfully, all was not lost, bar some pride and some relationship points with the 'misses'.

Problem solved, and all in all a simple enough fix!

Thanks

When it's ready. 😉
There are a lot of big changes in it and getting them working smoothly is taking time.