PPPoE fails to authenitcate



  • Pfsense 2.3.1 on 60gb ssd
    Running Vigor 130 (the crippled type with no internal authentication just dumb modem  >:( )  to fixed ip  (set by isp) ADSL.

    All interfaces are allowed in NAT and firewall.

    Modem GUI accessible from pfsense box thru OPT interface.

    firstly if the  setup wizard is used to set up the PPPoE when its accessed for a second time the PPPoE user mane  and password have reverted to the box admin ones. But they are correct on the WAN interface page.

    There seems NO way to get the WAN PPoE  to authenticate the ADSL connection on the Pfsense box (its connected on the modem GUI but not authenticated and shows sync rate an s/n)

    The WAN interface is always down and wont restart (its working ok when set as DHCP to an already on router)

    Now either I'm missing something? Or there is no way to get a authenticated connection from a virgor 130 to the Pfsense WAN.

    Has anyone got an idea what the problem is?



  • I have a similar problem (https://forum.pfsense.org/index.php?topic=112169.0) with PPPoE in my configuration (2.3.1).



  • Sounds like I have the same problem  :(

    dpinger status on dashboard is x - WAN is down and wont start . For me its all made worse by an unreliable connection to ISP and keeps dropping out.

    Beginning to think returning to pre 2.3 as I've spent way too much time getting nowhere including a factory reset an manual re do of all the settings

    It may just be the Vigor 130 which has been crippled by removing the ppoe/ppoa sign on/registration from the modem GUI forcing it to the router WAN settings



  • This may be of interest to anyone in the UK using Vigor 130 modem.

    Before Firmware Version: 3.7.6 Release Date: August 22, 2014 Applied Models: Vigor130  Your device was a full spec router/firewall modem.

    After that date - from Vigor release notes for FW 3.7.6

    "UK Version. If the country code of your router is UK, there'll be a special customization."

    The "special customization" is you  loose all of the router features and your device becomes a "dumb modem". Looks like Draytek think folks in the UK are too stupid type a user name and password into a modem GUI - even the early ones had bridge mode to pass PPP setting on to the router.

    I just bought one of these things and was going crazy trying to get it to connect via PPPoE to my service.

    Happily the  solution is to use FW pre 3.7.6 - Now its running well on pfsense 2.3.1 (otherwise buy a German one)



  • @fin100:

    The "special customization" is you  loose all of the router features and your device becomes a "dumb modem". Looks like Draytek think folks in the UK are too stupid type a user name and password into a modem GUI - even the early ones had bridge mode to pass PPP setting on to the router.

    Well…
    What they simply did was: Remove a Feature that nobody used to forcing you to authenticate the PPPoE Session from your router. (Why use a Modem-Router in the first place if you have your own router behind it?)
    If the Vigor is set to pure Modem/Bridge mode then it is fully transparent and acts only as a "converter" between Ethernet and your DSL connection.
    If you can't get it to authenticate then the problem is not the modem but the router behind it...



  • Exactly, - Choice is a good thing tho - A fully authenticated session via the modem as on DOCSIS is useful - unpiug the router plug in something else - and if you've ever had problems with Comcast connections you'll appreciate this ability. I just find it very odd that for the UK and UK alone your product gets downgraded without your consent. And, on pf 2.3.1. there was no PPPoE/A working so if you have a UK V130 re-flash to earlier FW and it will connect.

    I bought what I believed was single port modem with built in authentication. It has many uses - router goes tits up an you've still got a connection - router goes tits up with dumb modem and your screwed till you fix or replace it

    Anyways, some my find the info useful