[2.3.x] - WAN PPPoE connection problem (bridged modem).



  • I have a problem with PPPoE connection: i report here with a new thread (https://forum.pfsense.org/index.php?topic=112169.0), and i saw many user with the same problem with 2.3.x release.
    In my config with 2.2.6, i have a 2.2.6 WAN connection PPPoE with bridget modem. pfSense made authentication and get public IP address without any problem. With 2.3.0 and 2.3.1 after install PPPoE does'nt goes up, and i haven't routing from LAN to WAN. So no internet, no ping, no external access. Sometimes disconnect/reconnect WAN interface solve the issues, sometimes it doesn't.

    With 2.3.2 snapshot and fresh install i get PPPoE working, but if i try to restore 2.2.6 backup (one area only or all area), PPPoE goes down and i cannot restart.

    I read many thread of users with PPPoE problems, but i have not read yet a reply from pfSense team (this solution doesn't work at all; https://forum.pfsense.org/index.php?topic=110043.0). There is a bug with PPPoE in 2.3.x , there is a fix i can try to overcome this issue? pfSense 2.3 is fantastic when it works, and i'd like to install not only in my home, but i'd like to upgrade from 2.2.6 in my office too.  :)



  • anyone?



  • I had the same problem with failed PPPoE on 2.3.1 with a vigor 130 modem which only allowed pass-though PPP

    I could not get PPPoE to work at all! I gave up on ppp on the Pfsense box

    The answer for me was to flash the modem with old FW which allowed PPPoE on the modem removing the need for authentication on  the Pfsense box

    Work perfectly now



  • @fin100:

    Work perfectly now

    Yes, but this way you use a double nat instead of only one. I'd like NATting only from pfSense, with public IP on WAN.



  • I use a Vigor120 as modem, bridged to pfSense which does PPP authentication. My ISP (Tiscali S.p.A. Italy) uses PPPoA and Vigor120 has the feature to convert PPPoA<->PPPoE.
    I have this configuration since 2.2 beta and works pretty fine and stable.

    Modem has a fixed IP 10.0.0.5, while LAN has 192.168.101.0/24, VPN 192.168.102.0/24 and DMZ 192.168.103.0/24. I use a fake Interface (10.0.0.1) to access the Modem GUI.



  • I hadn't thought of the double NAT -  Juts gave up on PPPoE on the box after hours of failure. For me the upside was being able to reboot and alter the Pfsense box without killing the DSL session.

    Also my adsl was unstable so keeping authentication on the modem made for easier diagnosis BUT thinking about it now it could be that my inability to get a ppp session on the Pfsense box COULD be due to a internet supply problem as the fault I've been having was an inability to start a PPP session even with a stable DSL sync.

    I've just left running from the modem now as its been stable for a few days so maybe the problem was not with the Pfsense build?