@stephenw10

Your suggestion seemed very logical as it might explain the crash after the online update.

I removed the line in the configuration file and I also tried changing the line to designate "video" rather than "serial". Both gave the same result. Before the changes, the boot up stopped with a blank screen with a blinking cursor. After the changes, the boot up stopped with an alphanumeric graphic of the pfSense logo and a flashing cursor. The boot did not complete.

Since I am not seeing complaints from others, it looks like this is issue may be the result of a 10 year old bios in my Gigbox units. It appears that something is destroying the UEFI file when I do the configuration file restore.

I'll stick with bios. It will be interesting to see what happens during the next pfSense update.

Thanks for your suggestion and help.

Nice. I can only dream of those speeds.

Ok, without rebooting I went back to the Starlink interface, disabled IPv6 again, then re-enabled it again and the NTP IPv6 socket error has stopped. I can't reboot now to test if the error returns with a reboot but will try later.

Seems flaky.

Well if it's not actually in bridge more I'd expect pfSense to pull a private IP on it's WAN as long as it's set to DHCP.

You probably would have to power cycle to modem to be sure it isn't locked to the MAC address of whatever client you had connected there initially. Or spoof that MAC address in pfSense.

It's an upstream compatibility issue. If it gets corrected and we are able to compile it we will add back the package. The effort required to allow it is non-trivial though. Several of our developers have looked at it and concluded the task is likely beyond anything we can commit to at this point for an EoS architecture ourselves. So I really can't say when or if it might be done.

Steve

I have resolve it by reseting NTopNg pkg

First try disabling CPU power saving modes in the BIOS and see if that changes anything.

I tried the console factory default on the same 2100, with a valid Internet connection. It had no delay.

I then installed apcupsd via the GUI, and reset to defaults again. Afterwards the package was not installed. So, not sure what the difference was between yesterday and today.

I doubt the hardware (and hence ADI vs Arm) matters. Possibly, is an Internet connection required to remove a package? (callback to my 4m delay above) Or "many" packages or certain packages are handled differently than one package (seems unlikely)?

@jimp said in zfs on SG5100?:

but for most people the defaults are OK.

Great. The warning sort of surprised me and I wanted to make sure since my appliance is a bit older.

@stephenw10 said in Strange issue in correlation of newwanip:

Ok did you test with any other language selected other than German? (or English)

Only German and English

@JKnott you have to add the file yourself, to add it it's under NTP configuration under leap second area.

https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-s2s.html

-Rico

@rcoleman-netgate said in /var is low on disk space:

If, yes. If this is the case, and you are in the United States, and you are interested in having it used for a testing/trial process LMK and I can open DMs for you.

I'd like to discuss this with you.
jon

I just recently did this - now mind you I only have a hand full of devices..

I still had a few years left out of the 10 years on my CA, and server cert, etc.. But in another thread about openvpn I got reminded that my certs were using old RSA stuff.. So I updated everything to ecdsa..

But yeah @stephenw10 has the right path - fire up a new instance.. And migrate your clients over to the new instance using the new CA and certs.. This way you can do few clients at a time, and can always fall back to the old instance. Once your all migrated you can kill off the old instance..

But the migration really should be as simple as just changing the certs used on the instance you fire up, and then getting the clients the new certs.. Which is the hard part, especially if you have lots and lots of clients.

Especially if it's monitoring the default gateway IP. ISP gateways often prioritise ping replies pretty low. Try setting an external monitoring IP to get a better idea of real connectivity.

Steve

@stephenw10

Well, I've just switched to virtio again, rebooted all of them, and it works... weird indeed.

@stephenw10 said in 23.01 - Internal speaker no longer works - "Device "spkr" is Giant locked":

The speaker is likely just the last thing it shows and nothing to do with what it's halting on.

What image did you use to install from exactly?

Does it fail to boot the installer or after installing?

You used USB NICs?

Steve

I've used the USB installer (VGA) build from Pfsense website. It failed at installation part where it shows that error message. I'm not using any USB nics aside from the internal one from the mobo. I'll try to screenshot the whole thing so I can better explain myself 😅.

@stephenw10 thank you.

How exactly does it appear when this happens? Where are you logging in?

What is logged when that happens?

What pfSense version are you running?

Steve