Bug #829
closed
WAN stays assigned to pppoe0 interface after switching type from PPPoE to Static
Added by Paul K over 13 years ago. Updated about 10 years ago.
0%
Description
To reproduce:
- configure WAN as PPPoE
- switch WAN from PPPoE to Static
- go to 'Interface Assignments' page and you will see that WAN is still assigned to pppoe0 interface
Using embedded i386 snap from Sun Aug 15 10:26:54 EDT 2010
Files
| config-pfSense.local-20100820012816_pppoe.xml (16.2 KB) config-pfSense.local-20100820012816_pppoe.xml | file 1 | Paul K, 08/19/2010 09:32 PM | |
| config-pfSense.local-20100820012924_static.xml (16.3 KB) config-pfSense.local-20100820012924_static.xml | file 2 | Paul K, 08/19/2010 09:33 PM | |
| config-pfSense.local-20100820013059_static_corrected.xml (16.3 KB) config-pfSense.local-20100820013059_static_corrected.xml | file 3 | Paul K, 08/19/2010 09:39 PM |
Updated by Ermal Luçi over 13 years ago
Can you please provide more details on this.
If possible the config.xml file before and after the issues shows.
To be clear you have assigned a pppoe interface create on interface->assignment->ppp or you have just configured pppoe on the Interface->wan interface while the assignment is a normal interface?
Updated by Paul K over 13 years ago
PPPoE was configured on the Interface->wan page by selecting type = pppoe. I will try to reproduce it on a VM box and attach config files.
Updated by Paul K over 13 years ago
- File config-pfSense.local-20100820012816_pppoe.xml config-pfSense.local-20100820012816_pppoe.xml added
I just reproduced it on VM running 'Aug 18 21:58:53 EDT 2010 ' snappy.
3 files attached:
Updated by Paul K over 13 years ago
Updated by Paul K over 13 years ago
- File config-pfSense.local-20100820013059_static_corrected.xml config-pfSense.local-20100820013059_static_corrected.xml added
file 1 - PPPoE config
file 2 - WAN changed from PPPoE to static
file 3 - static config after I manually changed WAN assignment from pppoe0 to em0
Updated by Ermal Luçi over 13 years ago
- Status changed from New to Feedback
I investigated this and for now i just put a warning message there to tell you that you have to reassign the interface.
For 2.1 this will need to be fix together with some other things which are not trivial at the moment.
Thank you for reporting this and for the feedback.
Updated by Paul K over 13 years ago
Hi Ermal, I tried testing it, but could not get it to work.
My WAN is configured as PPPoE to begin with:
- I go to Interfaces WAN and change type from PPPoE to Static, enter IP and click save -> error message shows up 'You have to reassign the interface to be able to configure as static.' I guess that's an expected behaviour.
- Now I go to Interfaces -> assign and change WAN from PPPoE(vr1) to vr1 and click save -> page just keeps loading (I waited 5 min and it was still loading); If I compare backup before this step and after I see that WAN was reassigned from pppoe0 to vr1
- I now go back to WAN page and see that all my PPPoE settings are blank (good sign I guess), change type to static, click save and I am presented with the error message again.
- go back to interfaces assign page and WAN is assigned vr1; so I am kind of stuck in a loop.
Updated by Alexandre Paradis over 13 years ago
I have the same problem from pppoe to DHCP.
2.0-BETA4 (i386)
built on Fri Dec 3 15:21:00 EST 2010
Updated by Chris Buechler over 13 years ago
- Status changed from Feedback to New
Updated by Alexandre Paradis over 13 years ago
Right now it seems to work, but my pppoe was on a OPT1 interface, i will try again on another box with pppoe as primary wan interface.
Updated by Alexandre Paradis over 13 years ago
Alexandre Paradis wrote:
Right now it seems to work, but my pppoe was on a OPT1 interface, i will try again on another box with pppoe as primary wan interface.
but my pppoe IS on a OPT1 interface
fixed. sorry for the typo.
Updated by Ermal Luçi over 13 years ago
It does not matter really if it was WAN/LAN/OPT# ... Just test if it works as you expect.
Updated by Alexandre Paradis over 13 years ago
Ermal Luçi wrote:
It does not matter really if it was WAN/LAN/OPT# ... Just test if it works as you expect.
then it should be fixed. it was probably fixed with another fix during december.
Updated by Ermal Luçi over 13 years ago
- Status changed from Feedback to Resolved
Updated by o s over 10 years ago
Pfsense 2.1-RELEASE (amd64)
built on Wed Sep 11 18:17:37 EDT 2013
FreeBSD 8.3-RELEASE-p11
This exact bug just happend to me right now, seems not resolved anymore.
Updated by Caesar Caesar over 10 years ago
Same issue on 2.1-RELEASE (i386)
built on Wed Sep 11 18:16:50 EDT 2013
FreeBSD 8.3-RELEASE-p11
Updated by Caesar Caesar over 10 years ago
It seems a workaround is to set the interface to static, type an IP, then submit the changes. Once you do this, you can set it to DHCP.
Updated by James Simas over 10 years ago
Hello,
I just experienced this issue. My pfSense build is:
2.1-RELEASE (i386)
built on Wed Sep 11 18:16:50 EDT 2013
FreeBSD 8.3-RELEASE-p11
I was able to work around this issue using the steps which Caesar Caesar mentioned in comment #19.
James
Updated by Chris Buechler over 10 years ago
- Status changed from Resolved to New
- Target version changed from 2.0 to 2.1.1
- Affected Version changed from 2.0 to 2.1
Updated by Ermal Luçi about 10 years ago
- Status changed from New to Feedback
I cannot reproduce this.
And there is already code taking care of this since:
commit 8b1e7d04da1a2e1cefbad4b595033cedff4685e5
Author: Ermal <eri@pfsense.org>
Date: Wed May 4 21:54:10 2011 +0000
Correct wrong key for checking if a interface type switched. Ticket #1420
Updated by Chris Buechler about 10 years ago
- Status changed from Feedback to Resolved
this works as it should