Unable to update/reinstall kernel

[newsense]

We forgave Scrhodinger because he has/had a nice cat...



System-Settings-General  --- Is "Prefer to use IPv4 even if IPv6 is available" checked ?

Firewall-Settings-Advanced  --- Uncheck "Allow IPv6"


Alternatively, can you could try disabling IPv6 on the WAN interface


For Franco, what would explain fetch kernel URL works but opnsense-update consistently(apparently) hangs ? Does it ignore or is not aware of the Prefer IPv4 directive ?

[franco]

It might be part of the firmware runtime environment being slightly off, but I have no clue why. A plain fetch working better in general is what I have seen as well.

The FreeBSD package manager will actually move to a slimmed down version of curl in contrast to using libfetch which is what is currently being used. We also use libfetch through fetch utility.


Cheers,
Franco

[patrick3000]

Newsense, your latest suggestions have allowed me to successfully update the kernel to 23.1.11. Hopefully I will now also be able to upgrade to 23.7 through the web UI. I will report back after attempting to do so.

For the record, I made the following changes:

System-Settings-General  --- checked "Prefer to use IPv4 even if IPv6 is available"

Firewall-Settings-Advanced  --- unchecked "Allow IPv6"

Additionally, I disabled IPV6 on WAN, which I never use and was only set up because my ISP gives me both an IPV4 and IPV6 public address. (I wish I'd remembered this yesterday when you asked about IPV6, but since I never use it, I forgot that it was even enabled.)

After these changes, the kernel successfully updated through the package manager in the web UI.

[patrick3000]

The upgrade to 23.7 was successful once I got the kernel package updated. Thanks everyone for your help!

I do wonder if I should re-enable IPV6 on WAN. I'm leaning toward doing so because there might be some reason to have a public IPV6 address.

[newsense]

Amazon recently announced they'll start charging $0.005/hour for an IPv4 address, so IPv6 is unavoidable no matter how messy it is.

Glad everything worked out for you

https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/