Does Auto Update work on Nano?

[jwrascoe]

Hello Everyone,

If I press the "Invoke Auto Upgrade" Button on the "Diagnostics: Firmware: Auto Update" screen I end up with the following message….

The digital signature on this image is invalid.
Update cannot continue

Is this just not working yet or does it not work on NANO?

Was wondering if I can use this method rather than re-flashing the CF card...

Below are the progress details...

Thanks for your help.

Jim

A new version is now available

New version:    Wed Jan  6 10:18:40 EST 2010
Current version: 2.0-BETA1
Update source:  http://snapshots.pfsense.org/FreeBSD_RELENG_8_0/i386/pfSense_HEAD/.updaters/

Auto Update Download Status

Latest Version  : Wed Jan  6 10:18:40 EST 2010
  Current Version : 2.0-BETA1
  File size      : 76676333
  Downloaded      : 46628737
  Percent        : 61%

pfSense download complete.

The digital signature on this image is invalid.
Update cannot continue

[cmb]

You have to use manual or console update with nano right now.

[xbipin]

i tried upgrading from 30th dec to 7th jan using console didnt work so i did a manual firmware update from the web gui and that worked.

[clarknova]

@cmb:

You have to use manual or console update with nano right now.

Is this still the case? I'm guessing yes, as it was prompting me to update from a May 2010 version to a January 2010 version. I manually changed the URL to http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/ and it's showing me a current version, but the date on it does not match the dates on the nano snapshots I'm seeing on the server.

Just wondering if I'm doing it wrong, or if I'm trying to use a feature that just isn't there.

[Clouseau]

@cmb:

You have to use manual or console update with nano right now.

This has been the case all the time. What's the real problem behind of this? There must be some good reason why this simple url issue has not been fixed. This is just stupid that you can't use automatic update even those there are updates available…

[Efonnes]

As far as I know, the correct update URL for 2.0 NanoBSD snapshots would be http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/nanobsd/.updaters
However, nothing exists there.  In other words, there is no update URL for checking for newer 2.0 NanoBSD snapshots yet.

[cmb]

@Clouseau:

This has been the case all the time. What's the real problem behind of this? There must be some good reason why this simple url issue has not been fixed. This is just stupid that you can't use automatic update even those there are updates available…

Because it isn't a simple URL issue, there isn't any way to differentiate between the different nanobsd sizes in the auto update at this time.

[Clouseau]

@cmb:

@Clouseau:

This has been the case all the time. What's the real problem behind of this? There must be some good reason why this simple url issue has not been fixed. This is just stupid that you can't use automatic update even those there are updates available…

Because it isn't a simple URL issue, there isn't any way to differentiate between the different nanobsd sizes in the auto update at this time.

So why not do several then like this:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/512/
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/1g/
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/2g/
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/4g/
http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/full/

I know that this is just a workaround, but anyway this would help as long this problem is solved.

[cmb]

@Clouseau:

So why not do several then like this:

that would be fine - patches welcome.

[Efonnes]

It is going to be made part of the path to the files in some way at least.  Jim-p's idea was to just have the file names different for each size and have the update checker look for files with its size as part of the name.