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

    WAN Down - Unable to connect.

    Scheduled Pinned Locked Moved General pfSense Questions
    19 Posts 3 Posters 1.7k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Not really. It looks like the other end is just not responding.

      Are you running 2.4.4p2? If not upgrade to that.

      Steve

      1 Reply Last reply Reply Quote 0
      • Z
        zMaliz
        last edited by

        Thanks

        I'm currently running 2.4.4, its just happened again so will upgrade later this evening to 2.4.4p2

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

          Ah, OK. There were issues in 2.4.4 most of which were corrected in p1 but, yeah, upgrade before digging further this might well be fixed already.

          Steve

          Z 1 Reply Last reply Reply Quote 1
          • Z
            zMaliz @stephenw10
            last edited by

            @stephenw10 thanks for the reply.

            I've updated to 2.4.4p2 and will see how things go.

            1 Reply Last reply Reply Quote 0
            • Z
              zMaliz
              last edited by

              Hi.

              This has happened again. When it did I meant to check the phone line to ensure I'd got dial tone, but I forgot.
              The only way to get this working again was to reboot my pfSense box.

              I'm running 2.4.4p2.

              Gateway.log showed:

              Feb  5 22:15:14 pfSense dpinger: OPT3PIA_VPNV4 8.8.8.8: Alarm latency 16145us stddev 2343us loss 22%
Feb  5 22:15:17 pfSense dpinger: WAN_PPPOE 212.Y.Y.Y: Alarm latency 13419us stddev 893us loss 21%
Feb  5 22:17:11 pfSense dpinger: OPT3PIA_VPNV4 8.8.8.8: Clear latency 16182us stddev 2241us loss 10%
Feb  5 22:17:11 pfSense dpinger: WAN_PPPOE 212.Y.Y.Y: Clear latency 13463us stddev 873us loss 7%
Feb  5 22:17:46 pfSense dpinger: OPT3PIA_VPNV4 8.8.8.8: Alarm latency 16336us stddev 4056us loss 21%
Feb  5 22:17:58 pfSense dpinger: WAN_PPPOE 212.Y.Y.Y: Alarm latency 14359us stddev 5503us loss 21%
Feb  5 22:19:36 pfSense dpinger: WAN_PPPOE 212.Y.Y.Y: Clear latency 15778us stddev 9835us loss 10%
Feb  5 22:19:38 pfSense dpinger: OPT3PIA_VPNV4 8.8.8.8: Clear latency 18087us stddev 8345us loss 10%
Feb  5 22:21:00 pfSense dpinger: OPT3PIA_VPNV4 8.8.8.8: Alarm latency 21399us stddev 15991us loss 21%
Feb  5 22:21:01 pfSense dpinger: WAN_PPPOE 212.Y.Y.Y: Alarm latency 17491us stddev 14501us loss 21%
Feb  5 22:33:02 pfSense dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 212.Y.Y.Y  bind_addr 91.X.X.X  identifier "WAN_PPPOE "
Feb  5 22:33:04 pfSense dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 212.Y.Y.Y  bind_addr 91.X.X.X  identifier "WAN_PPPOE "
Feb  5 22:33:11 pfSense dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 212.Y.Y.Y  bind_addr 91.X.X.X  identifier "WAN_PPPOE "
Feb  5 22:33:11 pfSense dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 8.8.8.8  bind_addr 10.Z.Z.Z  identifier "PIA_VPNV4 "

              The ppp.log has the correct timestamp on the file, but is only shows the following:

              Feb  2 15:51:40 pfSense ppp: [wan_link0] LCP: LayerDown
Feb  2 15:51:40 pfSense ppp: [wan_link0] LCP: SendConfigReq #6
Feb  2 15:51:40 pfSense ppp: [wan_link0]   MRU 1492
Feb  2 15:51:40 pfSense ppp: [wan_link0]   MAGICNUM 0x60ac7bda
Feb  2 15:51:40 pfSense ppp: [wan_link0] LCP: SendConfigAck #113
Feb  2 15:51:40 pfSense ppp: [wan_link0]   MRU 1492
Feb  2 15:51:40 pfSense ppp: [wan_link0]   AUTHPROTO CHAP MD5
Feb  2 15:51:40 pfSense ppp: [wan_link0]   MAGICNUM 0x3f0936dc
Feb  2 15:51:40 pfSense ppp: [wan_link0] LCP: state change Opened --> Ack-Sent
Feb  2 15:51:40 pfSenseCLOG<▒▒▒^C

544 -rw-------   1 root   wheel   500K Feb  5 22:33 ppp.log

stat ppp.log
116 160561 -rw------- 1 root wheel 333272 511488 "Feb  5 22:39:36 2019" "Feb  5 22:33:09 2019" "Feb  5 22:33:09 2019" "Jun 22 18:23:22 2018" 32768 1088 0 ppp.log

              Which I think is around the last time it happened.
              How do I resolve this and how do I get a working ppp.log ?

              Thanks

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

                Looks like you are trying to view the the circular log files (clog) as plain text.
                https://docs.netgate.com/pfsense/en/latest/monitoring/working-with-binary-circular-logs-clog.html

                Steve

                1 Reply Last reply Reply Quote 0
                • Z
                  zMaliz
                  last edited by

                  Thanks
                  I've now got the log, but each time I try to post it the message is being flagged as spam.

                  Any way I can get this to you ?

                  Thanks

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

                    Try posting it in </> code brackets or as an attachment. Or link to pastebin etc maybe.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zMaliz
                      last edited by

                      Hi stephenw10

                      This is the pastebin to the log.
                      https://pastebin.com/Jutdw1cr

                      91 address is my static
                      212 address is the ISP

                      Thanks for taking a look at this.

                      Regards

                      1 Reply Last reply Reply Quote 1
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        Lets see if marks me as spam... Here is post from your pastebin

                        I don't get spam, I get
                        Please enter a shorter post. Posts can't be longer than 32767 character(s).

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • Z
                          zMaliz
                          last edited by

                          My initial reply did get the message about the number of characters. I shortened it and then got the spam message.

                          I've attached the link to the output, hopefully it will show what's going on!

                          Thanks

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

                            It looks like it fails to authorise until this:

                            Feb  6 00:01:35 pfSense ppp: [wan_link0] LCP: LayerUp
Feb  6 00:01:35 pfSense ppp: [wan_link0] CHAP: rec'd CHALLENGE #2 len: 29
Feb  6 00:01:35 pfSense ppp: [wan_link0]   Name: "IDNetLNS"
Feb  6 00:01:35 pfSense ppp: [wan_link0] CHAP: Using authname "000000@ISP.COM"
Feb  6 00:01:35 pfSense ppp: [wan_link0] CHAP: sending RESPONSE #2 len: 38
Feb  6 00:01:35 pfSense ppp: [wan_link0] CHAP: rec'd SUCCESS #2 len: 4
Feb  6 00:01:35 pfSense ppp: [wan_link0] LCP: authorization successful

                            It tries other against other 'Names' and fails.

                            It also looks like the other end is closing the link:

                            Feb  5 22:33:01 pfSense ppp: [wan] IPCP: state change Ack-Sent --> Opened
Feb  5 22:33:01 pfSense ppp: [wan] IPCP: LayerUp
Feb  5 22:33:01 pfSense ppp: [wan]   91.X.X.X -> 212.Y.Y.Y
Feb  6 00:01:04 pfSense ppp: [wan_link0] LCP: rec'd Terminate Request #3 (Opened)
Feb  6 00:01:04 pfSense ppp: [wan_link0] LCP: state change Opened --> Stopping

                            I assume you did nothing at that point?

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • Z
                              zMaliz
                              last edited by

                              The issue originally happened around 10:25 and I restarted my box at about 10:30/10:35

                              While this was happening I checked the phone, I had dial tone and a quiet line test sounded fine.

                              After the reboot the connection was up, I wasn't aware it had gone down again at 00:01

                              When this happens a reboot normally resolves it.. is there anything I can apart from reboot ?

                              My ISP can't see anything wrong and have suggested I try a different router.

                              My setup is:
                              BT OpenReach connected directly to BT master socket.
                              CAT5e connection to my pfSense box. This cable runs through a roof space to the other side of the house where my pfSense box is. I have a couple of other cables running this way for wireless access points and I've not had any drop outs from them so I don't think it's a cabling issue..

                              Any ideas, it happening quiet often.

                              Thanks

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

                                Ah well that's interesting, so you didn't notice the drop at 'Feb 6 00:01:04'?

                                Is that ADSL or VDSL/FTTC? I have used both and they worked fine. I am close to an exchange which helps.

                                If you're using FTTC with the Openreach modem is it the Huawei or ECI model? I had to swap out the Huawei modem I had as it seems very susceptible to overheating. The ECI has been rock solid.

                                Steve

                                1 Reply Last reply Reply Quote 0
                                • Z
                                  zMaliz
                                  last edited by

                                  Hi

                                  I didn't notice the drop at 00:01:04 as I was in bed !

                                  This is UK FTTC, the exchange is quite a distance a way, but I'm less than 100 mtrs from the cabinet.
                                  Connection on the Huawei HG612 is showing solid at the max of 80/20

                                  When this happens a restart of the HG612 doesn't help. I do have a ECI I could try if you think that will help.

                                  Thanks

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

                                    Well I can tell you struggled for a while with the HG612 and eventually swapped it out for an ECI and never looked back.

                                    When it failed it usually stopped passing traffic completely so the PPPoE would go down. All the LEDs just remained solid on
                                    it.

                                    I had thought you might be hitting this: https://redmine.pfsense.org/issues/9148

                                    I saw that a few times in 2.4.4 but have not seen that since that patch was included in 2.4.4p1. I don't see that in your logs specifically either.

                                    Unfortunately we can't see what happened that started the failure at 10.25. The first log entry shows the PPP session closing already:
                                    Feb 5 22:27:14 pfSense ppp: [wan_link0] PPPoE: connection closed

                                    However the failure at 00.01 was initiated from the remote side. It came back up by itself though.

                                    If we can get the log showing the connection fail that might help. Not guarantied though.

                                    I have nothing special set here and it "just works".

                                    Steve

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