Project

General

Profile

Actions

Bug #1621

closed
JS

Switching WAN from type PPP to other leaves former port assigned

Bug #1621: Switching WAN from type PPP to other leaves former port assigned

Added by Joao Seabra about 15 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
PPP Interfaces
Target version:
Start date:
06/26/2011
Due date:
% Done:

0%

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

Description

replacing description with actual problem found by Evgeny:

Whenever you set up WAN to PPP section <ppps><ppp><ports> in config.xml changes to whatever you shoos in "modem port" - for example /dev/cuau0. Then it is always presented in <input name="ppp_port" type="hidden" value="/dev/cuau0"> in interfaces.php. From now on you can't properly change WAN to PPTP or PPPoE as you can't get back em1 (or other ethernet interface), the page just does not provide you a choice for that.
I think "modem port" was wrongly introduced on this page interfaces.php as it links logical interface WAN-PPP to physical interface /dev/cuau0. All logical-physical links are defined under Interfaces->(assign), so this should go there as well. Or another way: physical part should be brought ino interfaces.php for PPTP and PPPoE.

CB Updated by Chris Buechler about 15 years ago Actions #1

  • Priority changed from Urgent to Normal

attach your config or can email it to me (cmb at pfsense dot org)

CB Updated by Chris Buechler about 15 years ago Actions #2

  • Status changed from New to Feedback

You have it configured to use /dev/cuau0 so no, it won't use re0 since it's not configured to do so. You must have edited the PPPoE configuration and incorrectly set the interface

JS Updated by Joao Seabra about 15 years ago Actions #3

No,I din't configure pfsense to use /dev/cua0.What happened was that I changed WAN type to DHCP,PPP,etc and saved those configurations and then tried to set it back to PPPoE to see if it would fix it.
Unfortunately it didn't...

EY Updated by Evgeny Yurchenko about 15 years ago Actions #4

Indeed if you change from PPP to PPPoE you'll have /dev/cuau0 remained in <ports></ports>.

EY Updated by Evgeny Yurchenko about 15 years ago Actions #5

Whenever you set up WAN to PPP section <ppps><ppp><ports> in config.xml changes to whatever you shoos in "modem port" - for example /dev/cuau0. Then it is always presented in <input name="ppp_port" type="hidden" value="/dev/cuau0"> in interfaces.php. From now on you can't properly change WAN to PPTP or PPPoE as you can't get back em1 (or other ethernet interface), the page just does not provide you a choice for that.
I think "modem port" was wrongly introduced on this page interfaces.php as it links logical interface WAN-PPP to physical interface /dev/cuau0. All logical-physical links are defined under Interfaces->(assign), so this should go there as well. Or another way: physical part should be brought ino interfaces.php for PPTP and PPPoE.

CB Updated by Chris Buechler about 15 years ago Actions #6

  • Subject changed from PPPoE config error after update to Switching WAN from type PPP to other leaves former port assigned
  • Status changed from Feedback to New
  • Target version changed from 2.0 to 2.1

updated with the real cause, though this isn't ideal and should be improved in the future, its cause is user error, not a bug. Can revisit in the future.

EY Updated by Evgeny Yurchenko about 15 years ago Actions #7

Forgot to mention: now user can always fix the mess he got after several reassignments by going to Interfaces->(assign) and choosing proper interface.

JS Updated by Joao Seabra about 15 years ago Actions #8

Sorry to insist but the problem showed up after a change in config.I deactivated the interface and when I activated it it never worked again.The switch with the interfaces was later when I was changed WAN type to see if it would fix it.
The original change that cause the problem was NOT change of WAN type!

EY Updated by Evgeny Yurchenko about 15 years ago Actions #9

Then create separate Bug report describing the problem.

JS Updated by Joao Seabra about 15 years ago Actions #10

I created this bug describing my problem and its enough for me.
I will wait for the new release.
Thanks

EL Updated by Ermal Luçi over 13 years ago Actions #11

  • Status changed from New to Feedback

Can you please try new snapshots.
This hsould not be happening anymore.

CB Updated by Chris Buechler about 13 years ago Actions #12

  • Target version changed from 2.1 to 2.2

CB Updated by Chris Buechler almost 12 years ago Actions #13

  • Status changed from Feedback to Closed
Actions

Also available in: Atom