Installing new Branch via console (command line)
-
We have automation that issues
pfSense-upgrade -U -d -yWe'd like to be able to have that command upgrade the version of pfsense (currently at 23.09.1) to the newer available version of 24.11, but it appears to be set on the 23.09.1 brance
The web interface allows me to change the Branch to 24.11, but can I do that via the console (command line)? We could do this by updating specific files too.
In addition, any negative consequences upgrading from 23.09.1 > 24.11?
-
@bigbmn said in Installing new Branch via console (command line):
can I do that via the console (command line)?
Not yet. https://redmine.pfsense.org/issues/15476
Yes you should be able to upgrade from 23.09.1 to 24.11 directly.
-
@stephenw10
Sorry I don't understand the response.
If you can set the branch from the webgui, what are the corresponding steps I would use to do that from the console, so that the command pfSense-upgrade -U -d -y would upgrade from 23.09.1 >> 24.11 -
There is no direct command to set the update branch from the CLI currently. There is a feature request open to add it because it is now a required step during the upgrade and some users, like you, would like to do that entirely from the CLI.
-
@stephenw10 Got it, thanks.
If the GUI sets the branch, and I assume updates some configuration files.
Are there a set of files that we can modify via the console, or symbolic links, that can manually set the branch version, so we can then issue pfSense-upgrade -U -d -y -
Man this one got me today. I was in a datacenter trying to get out of that freezing noisy environment asap. Trying to get a 2nd 7100 ready to HA pair with the first. It was on 26.03 and the new unit was 26.03.1. I had only console access because we were mid-way configuring the interfaces and the switch /VLAN config on the 7100 is a bit insane.
I thought by now this might have been possible from the console somehow... would have saved a chunk of time & frustration for sure
-
You could manually update the config file and reboot like:
- <pkg_repo_conf_path>26_03</pkg_repo_conf_path> + <pkg_repo_conf_path>26_03_1</pkg_repo_conf_path>
Privacy Policy · Cookie Policy