2.4.4.a.20180626.1951 - PPPOE via VLAN Bug



  • Hi, after some problems with unbound i've upgraded now to 2.4.4.a.20180626.1951. But now my PPPOE Link does not work anymore like with stable 2.4.3. With the developer version from april the PPPOE worked like before with 2.3. The VLAN Tag is done by the Vigor130.

    So whats the problem with PPPOE? Once it is working with a stable, then not, then with the dev then not again.

    Jun 27 03:36:14	ppp		[opt11_link0] PPPoE: Connecting to ''
    Jun 27 03:36:14	ppp		[opt11_link0] Link: reconnection attempt 139
    Jun 27 03:36:11	ppp		[opt11_link0] Link: reconnection attempt 139 in 3 seconds
    Jun 27 03:36:11	ppp		[opt11_link0] LCP: Down event
    Jun 27 03:36:11	ppp		[opt11_link0] Link: DOWN event
    Jun 27 03:36:11	ppp		[opt11_link0] PPPoE connection timeout after 9 seconds
    Jun 27 03:36:02	ppp		[opt11_link0] PPPoE: Connecting to ''
    Jun 27 03:36:02	ppp		[opt11_link0] Link: reconnection attempt 138
    Jun 27 03:36:01	ppp		[opt11_link0] Link: reconnection attempt 138 in 1 seconds
    Jun 27 03:36:01	ppp		[opt11_link0] LCP: Down event
    Jun 27 03:36:01	ppp		[opt11_link0] Link: DOWN event
    Jun 27 03:36:01	ppp		[opt11_link0] PPPoE connection timeout after 9 seconds
    Jun 27 03:35:52	ppp		[opt11_link0] PPPoE: Connecting to ''
    Jun 27 03:35:52	ppp		[opt11_link0] Link: reconnection attempt 137
    Jun 27 03:35:51	ppp		[opt11_link0] Link: reconnection attempt 137 in 1 seconds
    Jun 27 03:35:51	ppp		[opt11_link0] LCP: Down event
    Jun 27 03:35:51	ppp		[opt11_link0] Link: DOWN event
    Jun 27 03:35:51	ppp		[opt11_link0] PPPoE connection timeout after 9 seconds
    


  • Reviewing this in the morning again with a fresh mind.

    I think there is a problem with the definition of the interface after the upgrade.

    Shouldn't be this with an interface name?

    PPPoE: Connecting to ''
    

    So how can this be empty after the upgrade?

    Revising it manually to the right interface results in this:

    Jun 27 10:12:24	kernel		ng_ether_attach: can't name node bge0_2
    

    So i assume it is again the same issue like reported (and already fixed 8 months ago) here:

    https://redmine.pfsense.org/issues/7981


  • Rebel Alliance Developer Netgate

    I see the same here when I try to setup a PPPoE VLAN WAN. I opened https://redmine.pfsense.org/issues/8603 to track it. Thanks for letting us know!



  • Thanks for your quick reply. I've also tried to open an issue and registered an account. But i never got the confirmation email to activate my account. So thanks for opening that issue.

    Hope there will be a quick hotfix. I have a MWAN Setup but would like to use that PPPOE Line, of course. Or do you suggest to downgrade to another version?


  • Rebel Alliance Developer Netgate

    It's difficult to say how long that might be until it's fixed. If you need access to that WAN soon, you should probably move to a stable version like 2.4.3-p1. Though you might need to use an older config.xml backup if you downgrade.



  • Uhm that's bad, i was a bit lazy with backing up the config (because pfsense is sooo stable, of course :) ) The only one i could use is from 2016 and i've changed a lot in the meantime. So my bad. I will try to be patient or use a router for the meantime.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy