Solved: Is a direct (unproxied) Internet Connection needed to upgrade to 2.3 ??

robi

+1 for a way to update systems offline!

Scenarios when this is required:

when internal pfSense systems can't see the internet, only through proxy (like above)
when upgrading spare (second) hardware offline first, and replacing in production environment just by plugging the cables between the old and the new, to ensure minimal downtime and 100% working previous state

I would imagine something like a utility to analyze the configuration first, and evaluate if it's possible or not to do the update offline (meaning: no direct internet connection available at the moment when the system boots up first time after the upgrade).
For offline update, offer the possibility to download the package files somehow manually, and be able to give them to the firewall during the first boot after the update, to be able to finish it properly.
Like a gzipped file containing all that's needed for package reinstallation, pretty much like Dropbox does.

GuruNot

@YonNomNom:

I have attempted to add a proxy to the pkg configuration but that has not helped it does not even attempt to contact the proxy.

pkg_env: {
http_proxy: "http://10.xxx.xxx.xxx:8080"
}

As I was watching the console, I hadnt realised the upgrade had actually worked and the GUI was accessible.

So , taking your lead I CTRL+C to break in to the console, copied pkg.conf.sample to pkg.conf and modified the pkg_env sections as follows:

pkg_env: {
http_proxy=http://proxy:port
https_proxy=http://proxy:port
HTTP_PROXY=http://proxy:port
HTTPS_PROXY=http://proxy:port
}

Obviously replacing the proxy and port with my details.

Rebooted and all is good it pulled down the packages. Not sure if it is the upper case or the https entries that helped, but it is working and it wont hurt to keep both in the file.

YonNomNom

@GuruNot:

So , taking your lead I CTRL+C to break in to the console, copied pkg.conf.sample to pkg.conf and modified the pkg_env sections as follows:

So how do we get this fixed for the next release?

jimp

It was working at one point earlier in 2.3, but may have regressed. We're looking into it again. https://redmine.pfsense.org/issues/6149

robi

Just created a new ticket: https://redmine.pfsense.org/issues/6151
Edit: we were working both in the same time ???

jimp

@robi:

Just created a new ticket: https://redmine.pfsense.org/issues/6151

See my message just above yours. I'd already created a ticket for it. :-)

robi

Lots of tickets these days, isn't it :-\

xhark

@GuruNot:

So , taking your lead I CTRL+C to break in to the console, copied pkg.conf.sample to pkg.conf and modified the pkg_env sections

For people who read this, path is /usr/local/etc/pkg.conf :)

No need to copy pkg.conf.sample, juste create pkg.conf and add

@GuruNot:

pkg_env: {
http_proxy=http://proxy:port
https_proxy=http://proxy:port
HTTP_PROXY=http://proxy:port
HTTPS_PROXY=http://proxy:port
}

Rebooted and all is good it pulled down the packages.

jimp

Editing that file is kind of ugly.

Try the patch I just added to https://redmine.pfsense.org/issues/6149

kernel-panic

What would be the right time to apply this patch without having trouble in the update process from the previous version?

regards

McGlenn

the patch from https://redmine.pfsense.org/issues/6149 worked for me, but only after changing the uppercase HTTP_PROXY to lowercase http_proxy