Gateway alarm: WAN_PPPOE
-
@stephenw10 said in Gateway alarm: WAN_PPPOE:
I would suggest trying a different modem but those are like gold dust. I know!
That seems to hit the bull's eye here.
@wheelhouse20 said in Gateway alarm: WAN_PPPOE:
also im looking for why the connect lost if the fist place ie pfblocker/rc.update_urltables.
I cannot see any relation with pfBlockerNG in the logs.
-
@wheelhouse20 said in Gateway alarm: WAN_PPPOE:
modem was installed by bt-openreach
Lucky, they'd stopped giving those out by the time I got g.fast.
Yeah, this is nothing to do with pfBlocker updates.
The remote side of the DSL stops responding to LCP 15mins after the update.
There's nothing pfSense can do about that except kill the ppp session and start over.Steve
-
@wheelhouse20 You're experiencing the same dpinger issue...I get those alarms as well. Here is snapshot last time mine happened:
Clear latency 8561us stddev 5618us loss 15%
Feb 23 09:04:51 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Alarm latency 11829us stddev 8213us loss 21%
Feb 23 09:05:17 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Clear latency 11452us stddev 8133us loss 20%
Feb 23 09:05:31 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Alarm latency 10222us stddev 6298us loss 21%
Feb 23 09:05:48 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Clear latency 8644us stddev 5458us loss 14%
Feb 23 10:04:10 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Alarm latency 9920us stddev 6204us loss 21%
Feb 23 10:05:20 dpinger 55934 WAN_DHCP xx.xxx.xxx.1: Clear latency 8879us stddev 4871us loss 20% -
That's a different cause though since you're using DHCP and this is a failure at the LCP level.
-
Dpinger
Dpinger.txt -
This post is deleted! -
@stephenw10 said in Gateway alarm: WAN_PPPOE:
That's a different cause though since you're using DHCP and this is a failure at the LCP level.
Okay.
-
my WAN has been UP for 4 days then get an rc.gateway_alarm again must be something todo with with dpinger.
Mar 9 20:29:02 rc.gateway_alarm 70547 >>> Gateway alarm: WAN_PPPOE (Addr:15.14.12.10 Alarm:1 RTT:7.122ms RTTsd:.307ms Loss:21%)
-
@wheelhouse20 said in Gateway alarm: WAN_PPPOE:
Loss:21%
Yup, the default packet loss alarm threshold is 20% so it should throw an alarm when it hits 21%. We can see from previous logs that you have not changed it from that default so that's correct.
I would expect to probably see the same LCP echo timeouts in the ppp log?
I note the mt992 g.fast modem seems to have got a lot cheaper since I bought one. I think I paid well north of £100 at the time.
So if you are seeing LCP issues you might consider swapping it out but it's probably an upsteam issue. Either way there nothing pfSense can do there except restart the connection process.Steve
-
@stephenw10 what was i ment to change ?
-
I was suggesting you might change the modem if you can find one cheap enough. There have been some MT992s sold on ebay for <£20 recently. However I still think this is an upstream issue and that probably won't help.
Steve
-
@stephenw10 would my isp be able to fix the issue ?
-
Yes, they should be able to. Do you see the modem lose link when the LCP errors happen?
Might be difficult to log that with no modem access.
The ISP should be able to see the PPP connection failing. They can probably also see line stats including DSL link failures if they actually look.Steve
-
@stephenw10 My isp has said they havent seen any erros on the line and keep refering me to use there fritz box,i also have a broadband quality monitor with thinkbroadband which only shows drops when i have reboot the system.
do you think you could spare 5-10 mins to have a look at my set-up ? via discord or teamviewer
-
Are you still seeing the LCP timeouts in the PPP log when it fails?
Where did you get the MT992 modem from? Perhaps it's bad?
Try setting up a PPPoE sesion from something else using it and see if you still get disconnected.Try putting the Fritzbox back and see if that has disconnects at all.
I can't do live support here, we have paid support for that. But in this case they would tell you the same thing: LCP timeouts like that are the other end failing to respond. pfSense can do nothing about that.
Steve
