Bug #6120
closed
Password protect, baud on console menu not initially set post-upgrade on nanobsd and 2.3->2.3
100%
Description
Password protect the console menu, not effective after upgrade
After saving system/advanced settings again, the console locks itself. So easy to fix, but something to check..
Files
Updated by 
Updated by Chris Buechler over 8 years ago
- File upgrade_log.txt upgrade_log.txt added
- Subject changed from Password protect the console menu, not effective after upgrade to Password protect the console menu not initially set post-upgrade on nanobsd
- Category set to Console Menu
- Status changed from New to Confirmed
This is specific to nanobsd, and looks like it may have always happened in that situation. You end up with the default console setting until something triggers setup_serial_port().
post_upgrade_command.php doesn't appear to be running (successfully at least), nothing it logs ends up in upgrade_log.txt. Example attached. That's where it's intended to be set post-upgrade to ensure you don't have this situation.
Updated by Chris Buechler over 8 years ago
- Subject changed from Password protect the console menu not initially set post-upgrade on nanobsd to Password protect, baud on console menu not initially set post-upgrade on nanobsd
Updated by Sam Bingner over 8 years ago
I don't think this is specific to nanobsd as I always used -full and have seen the same problem on all 4 firewalls I updated. Hitting save again fixes it as said in the initial report.
Updated by Renato Botelho over 8 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset 14277cd6a309f73a9339344d688e220d5f3cb0d3.
Updated by Renato Botelho over 8 years ago
I'm testing full install right now and will let you know
Updated by Renato Botelho over 8 years ago
Pi Ba wrote:
Will it help for 'full' installs?
I couldn't reproduce it on full install. I had a 2.2.5 VM with serial speed set to 9600, password protected console, ...
After upgrade to recent 2.3.1-devel snapshot all config worked as expected on first boot
Updated by Greg M over 8 years ago
Hi!
It happens also on full install just tested it.
I have to save advanced settings then it prompts for login (on vga monitor, not console).
Then I do another snapshot update and it`s passwordless again.
Updated by Renato Botelho over 8 years ago
Greg M wrote:
Hi!
It happens also on full install just tested it.
I have to save advanced settings then it prompts for login (on vga monitor, not console).
Then I do another snapshot update and it`s passwordless again.
Can you please provide more details about how to reproduce?
- What version should I install first?
- What settings I need to chose?
- What version I need to update to?
Updated by Chris Buechler over 8 years ago
- Status changed from Feedback to Confirmed
It happens on full installs going from 2.3->2.3.1 as well, just not from 2.2.x or earlier to 2.3.x.
Updated by Pi Ba over 8 years ago
@Renato, for your reference yesterday evening i was testing and discussing with Chris with a fresh installation of pfSense-CE-2.3.1-DEVELOPMENT-amd64-20160505-0520.iso in a Virtualbox VM with 4 nics, 512MB memory, 4GB disk.
Installed pfSense with all default settings, locked console, then updated to new snapshot of 0506.1020 after reboot the console was unlocked.
The file /var/etc/disableconsole still exists, also the config option <disableconsolemenu/> is still there, only the /etc/ttys contains the wrong "al.Pc" value for ttyv0. Hope it helps fix this issue.
Updated by Renato Botelho over 8 years ago
- Status changed from Confirmed to Feedback
Applied in changeset 4cbe0b132f0d60b71a20052fae1155210a1f5a16.
Updated by Greg M over 8 years ago
- File IMAG0865.jpg IMAG0865.jpg added
See attached screen..
This happens on latest snap, maybe related?
Updated by Renato Botelho over 8 years ago
Greg M wrote:
See attached screen..
This happens on latest snap, maybe related?
Yes, I reverted a commit on master and forgot RELENG_2_3. Fixed now, next snapshot should be OK
Updated by Chris Buechler over 8 years ago
- Subject changed from Password protect, baud on console menu not initially set post-upgrade on nanobsd to Password protect, baud on console menu not initially set post-upgrade on nanobsd and 2.3->2.3
- Status changed from Feedback to Resolved
all works now