Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Upgrade to 2.7.0 stop PPPoE working

    Scheduled Pinned Locked Moved General pfSense Questions
    12 Posts 4 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      IanJanus
      last edited by

      I have just upgraded from pfsense version 2.6.0 to 2.7.0 and when pfsense restarted my WAN PPPoE interface remained down.

      pfsense is connect to a Vigor 130 modem which has been working fine for years. Interrogating the modem, appears to show it up and connected but pfsense interface is down.

      The interface appear to attempt to connect, it gets an ip and then goes down again, this keeps on repeating.

      I can only connect to the internet by putting another PPPoE router between pfsense and the vigor 130, and configuring pfsense to use a static IP for the WAN.

      I attach a copy of the upgrade log.upgrade_log_latest.txt

      fireodoF 1 Reply Last reply Reply Quote 1
      • fireodoF
        fireodo @IanJanus
        last edited by

        @IanJanus said in Upgrade to 2.7.0 stop PPPoE working:

        The interface appear to attempt to connect, it gets an ip and then goes down again, this keeps on repeating.

        Take a look at the ppp log - this should be more helpful ...

        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
        pfsense 2.8.0 CE
        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

        I 1 Reply Last reply Reply Quote 0
        • I
          IanJanus @fireodo
          last edited by

          @fireodo

          I have had a look at the log...but I don't understand most of it.

          I attach a copy of it. ppp_log.txt

          fireodoF 1 Reply Last reply Reply Quote 0
          • fireodoF
            fireodo @IanJanus
            last edited by

            @IanJanus said in Upgrade to 2.7.0 stop PPPoE working:

            I have had a look at the log...but I don't understand most of it.

            I am not a specialist but overlooking I do not see something that pops out ...

            Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
            SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
            pfsense 2.8.0 CE
            Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

            I 1 Reply Last reply Reply Quote 0
            • I
              IanJanus @fireodo
              last edited by

              @fireodo the only thing I thought was curious was "Jul 1 12:36:02 ppp 74415 caught fatal signal TERM"

              though I have no idea quite what it means or what I need to do?

              fireodoF 1 Reply Last reply Reply Quote 0
              • fireodoF
                fireodo @IanJanus
                last edited by

                @IanJanus said in Upgrade to 2.7.0 stop PPPoE working:

                the only thing I thought was curious was "Jul 1 12:36:02 ppp 74415 caught fatal signal TERM"

                Thats normal when pppoe is restarting

                Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                pfsense 2.8.0 CE
                Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                P 1 Reply Last reply Reply Quote 0
                • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
                • P
                  pvandaln @fireodo
                  last edited by

                  Did you ever figure this out? Having exact same problem. Can ping from pppoe interface out to google but nothing internal after reboot. If i restore config it comes back to life until a reboot. Thanks

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Check it still has a default route. Check it has the auto NAT rules in place if you can ping from pfSense but not client behind it.

                    P 1 Reply Last reply Reply Quote 1
                    • P
                      pvandaln @stephenw10
                      last edited by

                      Thanks Stephen. That was the issue. Not enough coffee today obviously. Default route was missing so definitely not a version issue. Thanks again i owe you one of the missing coffees :)

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        That could still be a bug. The default route should be automatically set when the PPPoE WAN comes up. Unless it was set to something else statically perhaps?

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          pvandaln @stephenw10
                          last edited by

                          Thanks Stephen. It was actually the default gateway setting (I've never had to set a static route). I've always left it as automatic (worked flawlessly since i installed it on my watchguard xtm5 years ago). All of a sudden after the update, traffic would only route past pppoe gateway if I manually set the default gateway to my pppoe interface. I could ping the ISP gateway but not past it, unless i manually set it. Maybe i should have chosen manual from day 1? Either way works great now like it did before. Another change i did was set the outbound Nat to automatic instead of hybrid. Hope this helps anyone else with similar issues.

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            If you have more than one gateway defined, like a VPN gateway or an internal LAN gateway, you should definitely set WAN_PPPoE as default rather than automatic. Otherwise it may default to one of the others and that's almost always invalid.

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.