WAN Down - Unable to connect.

stephenw10

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

zMaliz

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

stephenw10

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

Steve

zMaliz

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

johnpoz

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).

zMaliz

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

stephenw10

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

zMaliz

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

stephenw10

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

zMaliz

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

stephenw10

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