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

    PPPoE issues since 2.4

    Scheduled Pinned Locked Moved General pfSense Questions
    20 Posts 8 Posters 3.5k 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.
    • GertjanG
      Gertjan
      last edited by

      Hi,
      This line at the top is the most recent line, right ?

      Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1

      If so, you showed a perfect example of a successful pppoe connection establishment - IPv6 included.
      The link is up - all seems fine to me.

      If something made drop the connection, it happens later on.

      No "help me" PM's please. Use the forum, the community will thank you.
      Edit : and where are the logs ??

      1 Reply Last reply Reply Quote 0
      • S
        Stealth1081
        last edited by

        Thanks for the reply.

        I thought that showed a complete drop to a reconnect below is the current connection up until it starts getting IP info.

        Feb 3 12:20:46 is when i lost the connection again. Posted 2 line from previous log for comparison.

        I still don't know why there is any IPv6 because it is disable.

        Feb 3 12:20:57 ppp [wan] IPCP: rec'd Configure Request #142 (Req-Sent)
        Feb 3 12:20:57 ppp [wan] IPV6CP: state change Req-Sent –> Ack-Sent
        Feb 3 12:20:57 ppp [wan] IPV6CP: SendConfigAck #246
        Feb 3 12:20:57 ppp [wan] IPV6CP: rec'd Configure Request #246 (Req-Sent)
        Feb 3 12:20:57 ppp [wan] IPV6CP: SendConfigReq #3
        Feb 3 12:20:57 ppp [wan] IPV6CP: state change Starting –> Req-Sent
        Feb 3 12:20:57 ppp [wan] IPV6CP: Up event
        Feb 3 12:20:57 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
        Feb 3 12:20:57 ppp [wan] IPADDR 0.0.0.0
        Feb 3 12:20:57 ppp [wan] IPCP: SendConfigReq #5
        Feb 3 12:20:57 ppp [wan] IPCP: state change Starting –> Req-Sent
        Feb 3 12:20:57 ppp [wan] IPCP: Up event
        Feb 3 12:20:57 ppp [wan] IPV6CP: LayerStart
        Feb 3 12:20:57 ppp [wan] IPV6CP: state change Initial –> Starting
        Feb 3 12:20:57 ppp [wan] IPV6CP: Open event
        Feb 3 12:20:57 ppp [wan] IPCP: LayerStart
        Feb 3 12:20:57 ppp [wan] IPCP: state change Initial –> Starting
        Feb 3 12:20:57 ppp [wan] IPCP: Open event
        Feb 3 12:20:57 ppp [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
        Feb 3 12:20:57 ppp [wan_link0] Link: Join bundle "wan"
        Feb 3 12:20:57 ppp [wan_link0] Link: Matched action 'bundle "wan" ""'
        Feb 3 12:20:57 ppp [wan_link0] LCP: authorization successful
        Feb 3 12:20:57 ppp [wan_link0] MESG: CHAP authentication success
        Feb 3 12:20:57 ppp [wan_link0] CHAP: rec'd SUCCESS #1 len: 31
        Feb 3 12:20:57 ppp [wan_link0] CHAP: sending RESPONSE #1 len: 45
        Feb 3 12:20:57 ppp [wan_link0] CHAP: Using authname "bthomehub@btinternet.com"
        Feb 3 12:20:57 ppp [wan_link0] Name: "acc-aln1.do"
        Feb 3 12:20:57 ppp [wan_link0] CHAP: rec'd CHALLENGE #1 len: 53
        Feb 3 12:20:57 ppp [wan_link0] LCP: LayerUp
        Feb 3 12:20:57 ppp [wan_link0] LCP: auth: peer wants CHAP, I want nothing
        Feb 3 12:20:57 ppp [wan_link0] LCP: state change Ack-Sent –> Opened
        Feb 3 12:20:57 ppp [wan_link0] MAGICNUM 0xe9801181
        Feb 3 12:20:57 ppp [wan_link0] MRU 1492
        Feb 3 12:20:57 ppp [wan_link0] LCP: rec'd Configure Ack #4 (Ack-Sent)
        Feb 3 12:20:57 ppp [wan_link0] MAGICNUM 0xe9801181
        Feb 3 12:20:57 ppp [wan_link0] MRU 1492
        Feb 3 12:20:57 ppp [wan_link0] LCP: SendConfigReq #4
        Feb 3 12:20:57 ppp [wan_link0] PROTOCOMP
        Feb 3 12:20:57 ppp [wan_link0] LCP: rec'd Configure Reject #3 (Ack-Sent)
        Feb 3 12:20:57 ppp [wan_link0] LCP: state change Req-Sent –> Ack-Sent
        Feb 3 12:20:57 ppp [wan_link0] MAGICNUM 0x0562dfdd
        Feb 3 12:20:57 ppp [wan_link0] AUTHPROTO CHAP MD5
        Feb 3 12:20:57 ppp [wan_link0] MRU 1492
        Feb 3 12:20:57 ppp [wan_link0] LCP: SendConfigAck #223
        Feb 3 12:20:57 ppp [wan_link0] MAGICNUM 0x0562dfdd
        Feb 3 12:20:57 ppp [wan_link0] AUTHPROTO CHAP MD5
        Feb 3 12:20:57 ppp [wan_link0] MRU 1492
        Feb 3 12:20:57 ppp [wan_link0] LCP: rec'd Configure Request #223 (Req-Sent)
        Feb 3 12:20:57 ppp [wan_link0] MAGICNUM 0xe9801181
        Feb 3 12:20:57 ppp [wan_link0] MRU 1492
        Feb 3 12:20:57 ppp [wan_link0] PROTOCOMP
        Feb 3 12:20:57 ppp [wan_link0] LCP: SendConfigReq #3
        Feb 3 12:20:57 ppp [wan_link0] LCP: state change Starting –> Req-Sent
        Feb 3 12:20:57 ppp [wan_link0] LCP: Up event
        Feb 3 12:20:57 ppp [wan_link0] Link: UP event
        Feb 3 12:20:57 ppp [wan_link0] PPPoE: connection successful
        Feb 3 12:20:57 ppp PPPoE: rec'd ACNAME "acc-aln1.do"
        Feb 3 12:20:51 ppp [wan_link0] PPPoE: Connecting to ''
        Feb 3 12:20:51 ppp [wan_link0] Link: reconnection attempt 1
        Feb 3 12:20:47 ppp [wan_link0] Link: reconnection attempt 1 in 4 seconds
        Feb 3 12:20:47 ppp [wan_link0] LCP: LayerDown
        Feb 3 12:20:47 ppp [wan] IPV6CP: state change Closing –> Initial
        Feb 3 12:20:47 ppp [wan] Bundle: No NCPs left. Closing links…
        Feb 3 12:20:47 ppp [wan] IPV6CP: LayerFinish
        Feb 3 12:20:47 ppp [wan] IPV6CP: Down event
        Feb 3 12:20:47 ppp [wan] IPCP: state change Closing –> Initial
        Feb 3 12:20:47 ppp [wan] IPCP: LayerFinish
        Feb 3 12:20:47 ppp [wan] IPCP: Down event
        Feb 3 12:20:47 ppp [wan] IFACE: Rename interface pppoe0 to pppoe0
        Feb 3 12:20:47 ppp [wan] IFACE: Down event
        Feb 3 12:20:46 ppp [wan] IPV6CP: LayerDown
        Feb 3 12:20:46 ppp [wan] IPV6CP: SendTerminateReq #2
        Feb 3 12:20:46 ppp [wan] IPV6CP: state change Opened –> Closing
        Feb 3 12:20:46 ppp [wan] IPV6CP: Close event
        Feb 3 12:20:46 ppp [wan] IPCP: LayerDown
        Feb 3 12:20:46 ppp [wan] IPCP: SendTerminateReq #4
        Feb 3 12:20:46 ppp [wan] IPCP: state change Opened –> Closing
        Feb 3 12:20:46 ppp [wan] IPCP: Close event
        Feb 3 12:20:46 ppp [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
        Feb 3 12:20:46 ppp [wan_link0] Link: Leave bundle "wan"
        Feb 3 12:20:46 ppp [wan_link0] LCP: state change Opened –> Starting
        Feb 3 12:20:46 ppp [wan_link0] LCP: Down event
        Feb 3 12:20:46 ppp [wan_link0] Link: DOWN event
        Feb 3 12:20:46 ppp [wan_link0] PPPoE: connection closed
        Feb 3 12:17:39 ppp [wan] 217.42.170.107 -> 172.16.14.1
        Feb 3 12:17:39 ppp [wan] IPCP: LayerUp

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan
          last edited by

          At the bottom, inversed  :

          Feb 3 12:17:39   ppp      [wan] IPCP: LayerUp
Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1

          Connection ok for 3 minutes.
          And then :

          Feb 3 12:20:46   ppp      [wan_link0] PPPoE: connection closed

          I don't know why the connection was closed. I mean, if this is a programmed "clean" shutdown, or the result of a 'modem' that runs out of sync, bad line, etc.

          I used a pppoe connection for many years - and my ISP send a "connection shut down command" every 7 days sharp - pfSense rebuild the connection straight away, and I was good for another week.

          edit : possible to look closely at your "modem" to see if it has any "carrier" or "sync" led ? Has it a GUI - I could access my modem back then, I assigned it an IP like 10.0.0.1 on iy's LAN and put an IP like 10.0.0.138 on the WAN NIC of pfSense, some NAT rules (if I remember well) and I could checkout the GUI of my modem which had some indication about dB, line noise, sync speed, errors, etc.

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          1 Reply Last reply Reply Quote 0
          • S
            Stealth1081
            last edited by

            Thanks for the reply.

            I have recently replaced the modem with a vigor 130 as i thought my old openreach modem was on its last legs but they both do the same thing.

            Line stats from Vigor

            vdsl status

            –-------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
              Running Mode            :      17A      State                : SHOWTIME
              DS Actual Rate          : 32324000 bps  US Actual Rate      :  6633000 bps
              DS Attainable Rate      : 38224168 bps  US Attainable Rate  :  6888420 bps
              DS Path Mode            :  Interleave    US Path Mode        :        Fast
              DS Interleave Depth    :      471      US Interleave Depth  :        1
              NE Current Attenuation  :      22 dB    Cur SNR Margin      :        5  dB
              DS actual PSD          :    5. 6 dB    US actual PSD        :    5. 7  dB
              NE CRC Count            :      461      FE CRC Count        :      185
              NE ES Count            :      145      FE  ES Count        :      178
              Xdsl Reset Times        :        0      Xdsl Link  Times    :        1
              ITU Version[0]          : b5004946      ITU Version[1]      : 544e0000
              VDSL Firmware Version  : 05-07-06-0D-01-07  [with Vectoring support]
              Power Management Mode  : DSL_G997_PMS_L0
              Test Mode              : DISABLE
              –------------------------------ ATU-C Info ---------------------------------
              Far Current Attenuation :      30 dB    Far SNR Margin      :        6  dB
              CO ITU Version[0]      : b5004946      CO ITU Version[1]    : 544eb206
              DSLAM CHIPSET VENDOR    : < IFTN >

            I mention the IPv6 because i have not had a problem up until it started appearing in the logs. It wasn't uncommon to have my connection up for over 30 days.

            In Interfaces/WAN

            IPv6 Configuration Type - None

            I don't use it on my LAN either

            I may just have to connect the BT home hub and run dual NAT for awhile then fight BT as they have been there usual helpful selves.

            1 Reply Last reply Reply Quote 0
            • S
              Stealth1081
              last edited by

              Edit

              I have yet to figure out how to view how long the modem has been synced so i could see if they drop at the same time.

              1 Reply Last reply Reply Quote 0
              • H
                hda
                last edited by

                Strange. Is private 172.16.14.1 the gateway of your ISP ? Where is that number located.
                Do you have the DrayTek Vigor130 doing the PPPoE and the again PPPoE from pfSense to Vigor ?

                But can't you put the Vigor130 in bridge mode and pass-through,
                then have PPPoE public 217.xy.abc.107 to pfSense-WAN with a public gateway ?

                1 Reply Last reply Reply Quote 0
                • S
                  Stealth1081
                  last edited by

                  Thanks for the reply.

                  No idea why that address is appearing as you say it's a private address range. May have something to do with openvpn but don't know enough about it.

                  As for the vigor it is set to bridge mode. Pfsense does the pppoe stuff.

                  Either there is a line issue or starting to think something got messed up in the upgrade to 2.4.

                  Just found a box to drop all ipv6 in the advanced section will see if it helps but the ppp log still shows it getting an ipv6 address.

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sysyphus
                    last edited by

                    The Vigor130 has a Web GUI front-end this should show the uptime of the modem.

                    Do you need IPv6, have you tried just using IPv4 until everything is "settled"?

                    1 Reply Last reply Reply Quote 0
                    • S
                      Stealth1081
                      last edited by

                      Thanks for the reply

                      Which section is that under in the vigor. I must of missed it as don't see it.

                      As for IPv6 I don't currently need it which is why it is already set to none on the lan and wan. Yet the wan still gets an IPv6 address.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sysyphus
                        last edited by

                        You need to setup an outband NAT in pfSense to access the modem - Click here

                        Once you logon to the Vigor 130 modem, you will be at the dashboard, you will see the uptime in hours-minutes-seconds,another point is to make sure that you have the most up-to-date firmware.

                        From the dashboard you can navigate on the left to Online Status -> Physical Connection

                        [01]_Dashboard_1.png
                        [01]_Dashboard_1.png_thumb
                        [02]_Physical_Connection_1.png
                        [02]_Physical_Connection_1.png_thumb

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sysyphus
                          last edited by

                          Additionally, from a telnet session to the Vigor 130, type the command:  show status

                          The first line of the output will show the uptime

                          Vigor130_CLI.PNG
                          Vigor130_CLI.PNG_thumb

                          1 Reply Last reply Reply Quote 0
                          • GrimsonG
                            Grimson Banned
                            last edited by

                            Uptime is how long the Vigor is running, it is not affected by the DSL sync.

                            You can send syslog messages, with DSL information, to a device on your network, then you can filter them and see when DSL goes through a resync.

                            1 Reply Last reply Reply Quote 0
                            • ?
                              A Former User
                              last edited by

                              I would run a tcpdump (Diagnostics->Packet Capture) on the WAN interface of the pfSense while this fault is happening.

                              Posting that to a pastebin where we can look at it would be helpful (you'll have to scrub any passwords etc, be careful here before just blindly pasting)

                              1 Reply Last reply Reply Quote 0
                              • S
                                Stealth1081
                                last edited by

                                Thanks for the reply's.

                                Been very busy the last week and most of next week.

                                Will have to put up with it for awile untill I can try out your suggestions and get the log files.

                                Will post again when have them.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Stealth1081
                                  last edited by

                                  Just posting an update.

                                  I had some time last weekend and decided to rebuild my router and do a fresh install with 2.4.

                                  Only change i made from my old setup was to enable IPv6 on the BT connection right from the start during the PPPoE setup.

                                  So far my connection has been up for 6 days.

                                  My guess would be something got messed up when i upgraded to 2.4 from 2.3. As in it was trying to use the IPv6 even though it was disabled.

                                  Thanks for all your help and suggestions.

                                  1 Reply Last reply Reply Quote 0
                                  • I
                                    IssueHaver
                                    last edited by

                                    Just had a same issue with "IPV6CP: rec'd Configure Ack" messages appearing even though IPV6CP is disabled on the WAN interface.

                                    It didnt appear again on the PPPoE reconnect.

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

                                      And you are seeing PPPoE disconnect?

                                      1 Reply Last reply Reply Quote 0
                                      • I
                                        IssueHaver
                                        last edited by IssueHaver

                                        This probably happened on/after daily PPPoE reconnect. Everything worked normally except the DDNS client that didn't update properly (different issue: https://forum.netgate.com/topic/142719/ddns-client-skipped-ip-update/5). But I dont know why I have IPv6 messages on an interface where IPv6 is disabled.
                                        After reconnecting PPPoE WAN again, the messages didnt start appearing again.

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

                                          If the ISP supports v6 is may have sent that ACK in repsonce to a config request. If your interface is not configured for v6 it would just have ignored it.
                                          Unless you are actually seeing a connections problem there I would ignore that. I looks like a harmless response.

                                          Steve

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