Wrong ADI firmware uploaded to firmware.netgate.com

mwp821

The 2.2.5 firmware available at https://firmware.netgate.com/auto-update/ADI/amd64/ is the i386 version. Unfortunately, I found out the hard way:

[2.2.5-RELEASE][mwp@XXXXX]/home/mwp: uname -a
FreeBSD XXXXX 10.1-RELEASE-p24 FreeBSD 10.1-RELEASE-p24 #0 f27a67c(releng/10.1)-dirty: Thu Nov 5 10:59:55 CST 2015 root@factory22-i386-builder.pfmechanics.com:/usr/obj.RELENG_2_2.i386/usr/pfSensesrc/src.RELENG_2_2/sys/pfSense_SMP.10 i386

Taking a look at the sha256 sum:

mwp@YYYYY:~$ curl https://firmware.netgate.com/auto-update/ADI/amd64/latest.tgz | shasum -a 256
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 94.2M 100 94.2M 0 0 9.7M 0 0:00:09 0:00:09 –:--:-- 10.6M
0a3bf70851de81aa8fae3c91e5ec65884505d503847fe952784bace945902c4d -
mwp@YYYYY:~$ curl https://firmware.netgate.com/auto-update/ADI/amd64/latest.tgz.sha256
SHA256 (netgate-2.2.5-RELEASE-Full-Update-i386.tgz) = 0a3bf70851de81aa8fae3c91e5ec65884505d503847fe952784bace945902c4d

I manually applied a full install from https://firmware.netgate.com/auto-update/full_install/amd64/ and it didn't seem to work, because it didn't auto-reboot and I couldn't run any commands on the command-line. I waited about 30 minutes before forcefully rebooting it, rationalizing that if the firmware upgrade got far enough, there would be a new kernel and userspace binaries and the system would hopefully come back up. Miracle of miracles, it did. I'm reapplying the full install again just to be sure everything is clean and then I'll see what state my config is in. I was able to recover config.xml and all the backups so worst case scenario I can restore to an earlier point in time. Whew!

KOM

IIRC, the config.xml backup is platform-agnostic. Do a backup, wipe and install with x64 then restore.

Derelict

How is that even possible?

mwp821

@KOM:

IIRC, the config.xml backup is platform-agnostic. Do a backup, wipe and install with x64 then restore.

Thanks KOM. I wasn't able to retrieve config.xml and the web console was not usable (it showed the maintenance message). I think I'm all set now.

mwp821

@Derelict:

How is that even possible?

How is what even possible? That someone uploaded the wrong file to an FTP server?

cmb

Fixed, sorry for the trouble. Most installs don't pull from there, but fixed for future updates as well for those that do.

The upgrade you did to get it back to 64 bit should be fine, you just have to power cycle it afterwards since the 64 bit reboot command can't run on the 32 bit kernel.

mwp821

@cmb:

Fixed, sorry for the trouble. Most installs don't pull from there, but fixed for future updates as well for those that do.

No worries, it happens. ;) Should I be using a different URL? I have the RCC-VE 2440.

@cmb:

The upgrade you did to get it back to 64 bit should be fine, you just have to power cycle it afterwards since the 64 bit reboot command can't run on the 32 bit kernel.

Yes, spot on. That's exactly what I had to do. Thank you for confirming my approach!

cmb

It's fine to leave it to that URL. I updated the release file prep scripts to make sure it gets copied into place correctly (I just manually copied that one before and obviously didn't pay close enough attention to what I was doing).