Bug #1696: Panic when finishing setup wizard with PPPoE WAN - pfSense - pfSense bugtracker

Actions

Copy link

Bug #1696

closed

Panic when finishing setup wizard with PPPoE WAN

Added by Chris Buechler almost 13 years ago. Updated over 12 years ago.

Status:

Resolved

Priority:

High

Assignee:

Category:

Operating System

Target version:

2.0

Start date:

07/19/2011

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

By going through the setup wizard and changing the WAN type to PPPoE, or just changing the PPPoE username and password, after clicking reload at the end of the setup wizard the system will panic as shown in the attached.

Files

Download all files

pppoepanic.png (8.14 KB) pppoepanic.png		Chris Buechler, 07/19/2011 01:31 AM
pppoepanic-bt.png (11.9 KB) pppoepanic-bt.png		Chris Buechler, 07/19/2011 01:31 AM
pppoepanic2-bt.png (15.2 KB) pppoepanic2-bt.png		Chris Buechler, 09/06/2011 09:44 PM

Actions

Copy link

Updated by Jim Pingle over 12 years ago

Does this happen on current snapshots? I can't reproduce this in a VM.

Actions

Copy link

Updated by Chris Buechler over 12 years ago

I can still replicate this. If the WAN is set to PPPoE and you run through the setup wizard leaving the same settings, it panics after reloading at the last step of the wizard.

Actions

Copy link

Updated by Jim Pingle over 12 years ago

I was finally able to reproduce this in a VM, even when the WAN was initially set for DHCP. Same panic message/backtrace.

Actions

Copy link

Updated by Ermal Luçi over 12 years ago

Status changed from New to Feedback
% Done changed from 0 to 100

Applied in changeset commit:db74464bf6f980c5c5845d53624d4c6f1b139fa7.

Actions

Copy link

Updated by Chris Buechler over 12 years ago

File pppoepanic2-bt.png pppoepanic2-bt.png added
Status changed from Feedback to New

no change

Actions

Copy link

Updated by Ermal Luçi over 12 years ago

Status changed from New to Feedback

Applied in changeset 43d8f1cc9cd5190858ed7220339c0a147cc68dd2.

Actions

Copy link

Updated by Ermal Luçi over 12 years ago

Applied in changeset 851083bd2f9c382dc513d4a10608f5dc840efc01.

Actions

Copy link

Updated by Jim Pingle over 12 years ago

Status changed from Feedback to New

Panic still happens even after a gitsync picking up these changes. First run through the wizard (going from DHCP to PPPoE) worked for me, second run that was PPPoE to start and ended PPPoE resulted in a crash.

After reboot, doing a single run again (PPPoE to PPPoE) still crashes.

Actions

Copy link