Project

General

Profile

Actions
Copy link

Bug #6120

closed
PB RB

Password protect, baud on console menu not initially set post-upgrade on nanobsd and 2.3->2.3

Bug #6120: Password protect, baud on console menu not initially set post-upgrade on nanobsd and 2.3->2.3

Added by Pi Ba over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Console Menu
Target version:
2.3.1
Start date:
04/12/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:

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

Download all files
upgrade_log.txt (8.15 KB) upgrade_log.txt Chris Buechler, 04/22/2016 03:52 AM
IMAG0865.jpg (1.61 MB) IMAG0865.jpg Greg M, 05/09/2016 12:03 PM

JT Updated by Jim Thompson over 10 years ago Actions
Copy link
 #1

  • Assignee set to Renato Botelho

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #2

  • 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.

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #3

  • 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

SB Updated by Sam Bingner over 10 years ago Actions
Copy link
 #4

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.

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #5

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:14277cd6a309f73a9339344d688e220d5f3cb0d3.

PB Updated by Pi Ba over 10 years ago Actions
Copy link
 #6

Will it help for 'full' installs?

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #7

I'm testing full install right now and will let you know

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #8

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

GM Updated by Greg M over 10 years ago Actions
Copy link
 #9

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.

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #10

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?

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #11

  • 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.

PB Updated by Pi Ba over 10 years ago Actions
Copy link
 #12

@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.

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #13

  • Status changed from Confirmed to Feedback

Applied in changeset commit:4cbe0b132f0d60b71a20052fae1155210a1f5a16.

GM Updated by Greg M over 10 years ago Actions
Copy link
 #14

See attached screen..
This happens on latest snap, maybe related?

RB Updated by Renato Botelho over 10 years ago Actions
Copy link
 #15

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

GM Updated by Greg M over 10 years ago Actions
Copy link
 #16

Thanks, I can confirm working...

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #17

  • 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

Actions
Copy link

Also available in: Atom