You're right. The cert the firewall attempted to use is missing. Login SSH, restore the configuration prior to the upgrade. Rebooted back on RELEASE 24.03, Login to the GUI and removed the missing cert ... upgrade from 24.03 to 24.11 again ... and voila, upgrade is successful!!

Ah, nice result!

Yes if you had some other router that resolved to the same IP and then use that same URL after swapping in pfSense it will show a rebind error.

@jmmm Were you ever able to solve your IPv6 issues while bypassing the ATT modem? I followed the pfSense recipe. IPv4 works great, but IPv6 devices cannot access DNS nor can the pfSense instance access the Netgate servers for updates and packages.

I mean it could be the device testing from has it set incorrectly. Just seeing IPs from two halves of the /24 like that (assuming it is) screams subnet mask to me.

I assume you have that lib but it's the wrong version?

You probably need to upgrade mongodb since installing an old lib is unlikely to work IMO.

Mmm, I would expect it to sometimes end up on the 2.5G link if you repeat the test though.

However bridged connections can behave oddly.

Yes that's true, the on-board switch only supports load-balance LAGGs which is not useful in that situation. The NIC connected to it cannot pass the additional bandwidth and it doesn't provide any redundancy.

The only way you could do it would be using the WAN port and one of the LANs with VLANs run over it. But that's also unlikely to give you anything useful!

Ah, it's an 1100? You're probably hitting a RAM limit.

Try uninstalling any packages before upgrading. You can re-install them afterwards and the settings will be retained.

What version did you upgrade from?

@xvicarious said in Upgrade Heck, left with a broken ICU, package itself broken:

it points of course to libicuio.so.73.2. And that... Is only there in spirit.

You don't see ibicuio.so.73.2 either on your system or in the pkg?

It should be there.

Yes it's common to get a delegation only on the WAN directly. So you can use that on internal interfaces but the WAN only ever as a link local address to route it across.

OK so it's a GPON module. Those can present issues in pfSense since they often only accept one link rate but present as a something else to the NIC.

If it's a 1G link I would try to get a 1G SFP NIC as that is most likely to work without issues.

Though since it's probably running OpenWRT you may be able to force it. https://hack-gpon.org/ont-huawei-ma5671a/

Ah, yes. Been a while I guess. 😉

@stephenw10 said in [ Bug? ] 24.11 web GUI cannot enable L2TP server ( while the service is just working fine in the background ):

3487972e11dc8d096f97c2a2e5a0e86d7f179002

Hi,

Thank you. Had fix it.

@stephenw10 I reported it as (possible) spam (category 'other) yesterday.

@Gblenn said in CPU pegged at 100%:

I have seen a lot of complaints about 24.11 consuming a lot of CPU resources for some reason?

CPU Usage - pfSense 24.11 on a 4100.

edit : true, I didn't activate every bell and whistle and I'm more a log watcher guy, the dashboard isn't my thing.

@Gertjan ok thanks. I'll continue to update via my spare ssd. Not had any issues so far with previous updates. Just for clarity it's an on board x710 sfp port rather than a card.

The basic transparent setup mode should work for you, the first thing to check is that your status LED is solid white.
https://www.quantumfiber.com/support/equipment/user-guides/c5500xk-smartnid.html

The pfSense Wan interface is plain IPv4 DHCP:
47870cfc-d952-42e3-89ad-82cf02c29f47-image.png

Centurylink and Quantum (at least) don't offer IPv6 connections in most areas. They do offer a very poor 6RD option to get v6 over the v4 connection.

Mmm, I'd be amazed if your ISP was using anything other than 1500.