So it sounds like I'll need to do another console update from last night's commit for GUI upgrades to work again?

They should work if you're running an image from after that point.

It may be a good idea to reflash anyhow since the image sizes were all adjusted a bit. They're a tad lower than they were before, so they should still work, but it wouldn't hurt to play it safe in that regard.

Hi,
I tried to do a web upgrade on nanobsd 1.2.3-RC3 built on Fri Sep 11 03:48:31 UTC 2009
–-->>
A new version is now available
New version: Sat Sep 12 04:47:40 UTC 2009
Current version: 1.2.3-RC3
Update source: http://updates.pfSense.com/_updaters

Manual upgrade should work. Be advised that the part of the upgrade that flashes the other slice can take a LONG time (6+ minutes for a 4GB card), so don't panic if you don't see any activity for a while. If you have a serial connection available, you can:

tail -f /cf/conf/upgrade_log.txt

…before you upload the new firmware to the router and watch the whole process, including the reboot of the newly flashed slice.

I haven't heard anything from the developers about plans to fix auto update on nanobsd. I'm just grateful there's at least some way to upgrade my ALIX that doesn't require a screwdriver. ;D

Hi, probably a silly question, but it is the first time I partizipate in the pfsense "beta".
Q: After doing a manual update the System/Package Manger/Installed Packages: blinkled was gone. I had to reinstall it again. Is this normal?

Hi, probably a silly question, but it is the first time I partizipate in the pfsense "beta".
Q: After doing a manual update the System/Package Manger/Installed Packages: blinkled was gone. I had to reinstall it again. Is this normal?

Hi, probably a silly question, but it is the first time I partizipate in the pfsense "beta".
Q: After doing a manual update the System/Package Manger/Installed Packages: blinkled was gone. I had to reinstall it again. Is this normal?

Best regards jakob

This is normal on NanoBSD. The upgrade gets written to a second slice (sort of like another partition on windows) that is normally dormant.
Because this second slice has not been touched, the package is not installed on there, and must be reinstalled after switching slices.

It works this way in case the upgrade fails, so you can always go back and boot the other slice and return to a working system instead of being stuck with a brick and having to reflash the CF :)

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.