Coreboot replaced with firmware upgrade?

johnpoz

I don't have anything against a name change - it was kind of my own shooting myself in the foot sort of thing. I did a clean install with restore from previous config.

It seems fair that code to check if old package was listed by menu item only, and package not installed would of been a bit much to ask for.

Its cleared up now, simple edit of the xml to remove the erroneous menu item that got left over.

But its possible with how many installs are out there, and how many people might do clean install while restoring previous version config - someone else might see this. I noticed someone else already posted a thread related to the coreboot thing..

I got my system back and running, on clean install now on zfs with min effort and time..

If I would make any suggestion to anyone - if wanting to do a clean install for zfs like I did, prob be to upgrade the system to current version your wanting to clean install. So that the update system can clean out any say old stuff that has been changed, removed, etc. Prob should of done it that way with hindsight being 20/20 ;)

NogBadTheBad

https://github.com/pfsense/FreeBSD-ports/commits/devel/sysutils/pfSense-pkg-Netgate_Firmware_Upgrade

I smell new hardware

Update 6100 firmware to CORDOBA-02.01.00.00t-uc-10.fd

bmeeks

Did the new Netgate_Firmware_Upgrade package auto-install for you guys? I have an SG-5100, and that package did not auto-install. The old package (Coreboot) was removed, but the new one was not installed. I do see it listed as an installable package under the Available Packages tab. So should I manually install it?

My box did something very weird with DNS during this upgrade. First time I've ever seen this. Granted I was updating from 2.4.5_p1 straight to 21.02.2, because I had held off on the 21.02 updates initially. My local firewall itself could not resolve any DNS lookups. Strangely, unbound was running just fine. I even stopped and restarted it a couple of times trying to kickstart DNS lookups, but no dice. Even more strange, I have my Windows AD DNS forwarding to unbound on pfSense for external lookups. Those worked! Any LAN client could lookup anything, but any lookup on pfSense itself failed with a cryptic error message from net.c and sendmsg() failed. The check for updates on the dashboard also failed. I finally had to reboot the firewall, then everything worked properly. Snort reinstalled, downloaded updates and my ARP Table display populated with hostnames to match the IP addresses. Before the reboot, the ARP table page had only the IP addresses (no hostnames listed).

So back to my original question, should I manually install the Firmware Update package on the assumption my post-upgrade DNS failure led to it not getting auto-installed?

johnpoz

@bmeeks said in Coreboot replaced with firmware upgrade?:

should I manually install the Firmware Update package

If you feel there might be an update ;) At some point? ;)

Not really a required package.. Unless you hear about an update being available.

bmeeks

@johnpoz said in Coreboot replaced with firmware upgrade?:

@bmeeks said in Coreboot replaced with firmware upgrade?:

should I manually install the Firmware Update package

If you feel there might be an update ;) At some point? ;)

Not really a required package.. Unless you hear about an update being available.

Okay. I think I will install it. I'm thinking it probably wanted to install during the upgrade, but something clobbered the resolver client on the firewall itself. It was not unbound. It was running fine the entire time, and like I said, my LAN clients could do lookups. Only lookups local on the firewall were failing. Nothing about this was logged, either. I finally discovered what was happening by trying dig and nslookup at the CLI.

gfeiner

@nogbadthebad said in Coreboot replaced with firmware upgrade?:

https://github.com/pfsense/FreeBSD-ports/commits/devel/sysutils/pfSense-pkg-Netgate_Firmware_Upgrade

I smell new hardware

Update 6100 firmware to CORDOBA-02.01.00.00t-uc-10.fd

Hmm, indeed.

jimp

Gosh, I have no idea whatever that might be.

KOM

@nogbadthebad said in Coreboot replaced with firmware upgrade?:

Update 6100 firmware to CORDOBA-02.01.00.00t-uc-10.fd

Ricardo Montalban would approve.

SteveITS

@bmeeks said in Coreboot replaced with firmware upgrade?:

I have my Windows AD DNS forwarding to unbound on pfSense for external lookups. Those worked!

I saw this thread mentioning Unbound doesn't work on 127.0.0.1 after upgrade.

Cool_Corona

@steveits Wrong config. They manually added 127.0.0.1 in DNS and it was there allready