Project

General

Profile

Bug #1439

WAN PPPoE config dropped on update from 1.2.3 (nanobsd) to 2.0-RC1 (snapshot 20110415-1518)

Added by Malte Stretz over 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
04/16/2011
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:
i386

Description

I just upgraded a firewall from 1.2.3 to todays snapshot, using pfSense-2.0-RC1-4g-i386-20110415-1518-nanobsd-upgrade.img.gz. Everything looked fine but after the reboot, my PPPoE WAN link was down. The credentials were cleared out. I'll post the relevant parts of the old and the new config later when I had some time to clear them up from personal data.

pfsense-upgrade.log (312 KB) pfsense-upgrade.log upgrade log Malte Stretz, 04/16/2011 11:36 AM
config-a-20110310200759.xml (20 KB) config-a-20110310200759.xml old config (1.2.3) Malte Stretz, 04/18/2011 04:38 PM
config-b-20110416162902.xml (22.3 KB) config-b-20110416162902.xml new config (2.0-rc1) Malte Stretz, 04/18/2011 04:38 PM

Associated revisions

Revision 1f0c76cf (diff)
Added by Jim Pingle about 8 years ago

Fix PPPoE upgrade, the <pppoe> tag is considered an array these days and the upgrade code wasn't treating it properly, accessing it directly instead of using the first entry ([0]). Fixes #1439 - PPPoE credentials upgrade properly now.

History

#2 Updated by Jim Pingle over 8 years ago

  • Status changed from New to Feedback

The upgrade log won't tell us anything relevant here. We need the before and after upgrade versions of your config.xml - if you want to change the passwords, mask them out (all x's or some other character) but don't empty them out as it might confuse the issue.

Thanks!

#3 Updated by Malte Stretz over 8 years ago

Here's the old and the new config. I replaced passwords and usernames, also removed some settings like firewall filters.

In the old file, the PPPoE user is yyy, the password is xxx. You won't find this in the new config.

The new config is not the pristine new one, I changed some setting I can't remember before I pulled this backup.

#4 Updated by Jim Pingle about 8 years ago

  • % Done changed from 0 to 100

#5 Updated by Chris Buechler almost 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF