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

    Pfsense PPPoE no Internet after dropout even though it gets IP Address

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 2.1k 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.
    • V Offline
      vesikk
      last edited by

      Hey guys, So basically I have this problem that other people also seem to have with pfsense. I have my billion 7800NL modem in bridge mode giving pfsense the PPPoE authentication. Everything works and is fine until my modem either drops connection, manually disconnected or restarted. Pfsense does the job of getting the new IP address but no internet connection.

      Rebooting pfsense doesn't seem to fix it, it just gets a new IP address and wont allows Lan to access internet.

      Does anyone know how to fix this problem?

      thanks :)

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

        Are you getting a connection on the pfSense box itself? Can you ping sites from Diagnostics > Ping?

        Steve

        1 Reply Last reply Reply Quote 0
        • V Offline
          vesikk
          last edited by

          Pfsense obtains a new IP, my ISP's website shows me that pfsense has the new IP but trying to go to google.com or any website times out. I ahall check the ping from pfsense itself right now.

          1 Reply Last reply Reply Quote 0
          • V Offline
            vesikk
            last edited by

            @stephenw10:

            Are you getting a connection on the pfSense box itself? Can you ping sites from Diagnostics > Ping?

            Steve

            Sorry for the long wait. Pfsense is now having trouble getting a stable PPPoE connection, it keeps dropping. I did manage to try and ping but was unsuccessful, I can see in the firewall logs that all local IP's are failing to connect "cannot resolve" the connection.

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

              Hmm, you're seeing the traffic blocked in the firewall log?
              I assume you have rules on LAN to allow it?

              If you can't ping from diagnostics then there's no chance of accessing anything from LAN.
              Check the ppp log.

              Steve

              1 Reply Last reply Reply Quote 0
              • V Offline
                vesikk
                last edited by

                @stephenw10:

                Hmm, you're seeing the traffic blocked in the firewall log?
                I assume you have rules on LAN to allow it?

                If you can't ping from diagnostics then there's no chance of accessing anything from LAN.
                Check the ppp log.

                Steve

                Here is my ppp log.

                Jun 25 21:32:25 ppp: [wan] IPV6CP: Open event
                Jun 25 21:32:25 ppp: [wan] IPV6CP: state change Initial –> Starting
                Jun 25 21:32:25 ppp: [wan] IPV6CP: LayerStart
                Jun 25 21:32:25 ppp: [wan] IPCP: Up event
                Jun 25 21:32:25 ppp: [wan] IPCP: state change Starting –> Req-Sent
                Jun 25 21:32:25 ppp: [wan] IPCP: SendConfigReq #1
                Jun 25 21:32:25 ppp: [wan] IPADDR 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
                Jun 25 21:32:25 ppp: [wan] PRIDNS 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] SECDNS 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] IPV6CP: Up event
                Jun 25 21:32:25 ppp: [wan] IPV6CP: state change Starting –> Req-Sent
                Jun 25 21:32:25 ppp: [wan] IPV6CP: SendConfigReq #1
                Jun 25 21:32:25 ppp: [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
                Jun 25 21:32:25 ppp: [wan] IPADDR 150.101.199.219
                Jun 25 21:32:25 ppp: [wan] 150.101.199.219 is OK
                Jun 25 21:32:25 ppp: [wan] IPCP: SendConfigAck #1
                Jun 25 21:32:25 ppp: [wan] IPADDR 150.101.199.219
                Jun 25 21:32:25 ppp: [wan] IPCP: state change Req-Sent –> Ack-Sent
                Jun 25 21:32:25 ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
                Jun 25 21:32:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
                Jun 25 21:32:25 ppp: [wan] IPCP: SendConfigReq #2
                Jun 25 21:32:25 ppp: [wan] IPADDR 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] PRIDNS 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] SECDNS 0.0.0.0
                Jun 25 21:32:25 ppp: [wan] IPV6CP: rec'd Configure Request #1 (Req-Sent)
                Jun 25 21:32:25 ppp: [wan] IPV6CP: SendConfigAck #1
                Jun 25 21:32:25 ppp: [wan] IPV6CP: state change Req-Sent –> Ack-Sent
                Jun 25 21:32:25 ppp: [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
                Jun 25 21:32:25 ppp: [wan] IPV6CP: state change Ack-Sent –> Opened
                Jun 25 21:32:25 ppp: [wan] IPV6CP: LayerUp
                Jun 25 21:32:25 ppp: [wan] 98dc:de48:e85a:af62 -> 0224:14ff:fe9a:b910
                Jun 25 21:32:26 ppp: [wan] IFACE: Up event
                Jun 25 21:32:26 ppp: [wan] IFACE: Rename interface ng0 to pppoe0
                Jun 25 21:32:26 ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
                Jun 25 21:32:26 ppp: [wan] IPADDR 121.44.201.118
                Jun 25 21:32:26 ppp: [wan] 121.44.201.118 is OK
                Jun 25 21:32:26 ppp: [wan] PRIDNS 192.231.203.132
                Jun 25 21:32:26 ppp: [wan] SECDNS 192.231.203.3
                Jun 25 21:32:26 ppp: [wan] IPCP: SendConfigReq #3
                Jun 25 21:32:26 ppp: [wan] IPADDR 121.44.201.118
                Jun 25 21:32:26 ppp: [wan] PRIDNS 192.231.203.132
                Jun 25 21:32:26 ppp: [wan] SECDNS 192.231.203.3
                Jun 25 21:32:26 ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
                Jun 25 21:32:26 ppp: [wan] IPADDR 121.44.201.118
                Jun 25 21:32:26 ppp: [wan] PRIDNS 192.231.203.132
                Jun 25 21:32:26 ppp: [wan] SECDNS 192.231.203.3
                Jun 25 21:32:26 ppp: [wan] IPCP: state change Ack-Sent –> Opened
                Jun 25 21:32:26 ppp: [wan] IPCP: LayerUp
                Jun 25 21:32:26 ppp: [wan] 121.44.201.118 -> 150.101.199.219

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