pfsense router behind a ZTE H1600
-
The WAN monitoring IP by default is the upstream gateway IP as shown in the logs there. However you can change that in System > Routing > Gateways, edit the WAN.
It's usually more useful to monitor something further upstream like 8.8.8.8. That way if your ISP has some connectivity issue you see it even if the link between you and them remains up.
So I would do that first and make sure it's logging the monitoring data for the gateway.That sendto error implies it's lost a route to the gateway which I would only expect to happen when the PPPoE session reconnects. That would be in the ppp log though.
It's not an authentication issue. It would never connect at all if it was.
Steve
-
@stephenw10 said in pfsense router behind a ZTE H1600:
The WAN monitoring IP by default is the upstream gateway IP as shown in the logs there. However you can change that in System > Routing > Gateways, edit the WAN.
It's usually more useful to monitor something further upstream like 8.8.8.8. That way if your ISP has some connectivity issue you see it even if the link between you and them remains up.
So I would do that first and make sure it's logging the monitoring data for the gateway.hat sendto error implies it's lost a route to the gateway which I would only expect to happen when the PPPoE session reconnects. That would be in the ppp log though.
It's not an authentication issue. It would never connect at all if it was.
Steve
Got it.
I will edit the monitoring IP to Google 8.8.8.8 and see what the logs report back. Then I will post my findings.Thank you so much Steve.
-
@stephenw10 said in pfsense router behind a ZTE H1600:
The WAN monitoring IP by default is the upstream gateway IP as shown in the logs there. However you can change that in System > Routing > Gateways, edit the WAN.
It's usually more useful to monitor something further upstream like 8.8.8.8. That way if your ISP has some connectivity issue you see it even if the link between you and them remains up.
So I would do that first and make sure it's logging the monitoring data for the gateway.That sendto error implies it's lost a route to the gateway which I would only expect to happen when the PPPoE session reconnects. That would be in the ppp log though.
It's not an authentication issue. It would never connect at all if it was.
Steve
Hey Steve,
Here are some of my Gateway logs
Oct 19 12:30:36 dpinger 19498 WAN_PPPOE 8.8.8.8: Alarm latency 42752us stddev 9438us loss 21% Oct 19 13:11:33 dpinger 19498 WAN_PPPOE 8.8.8.8: Alarm latency 44275us stddev 16872us loss 21% Oct 19 13:25:11 dpinger 19498 WAN_PPPOE 8.8.8.8: Alarm latency 57022us stddev 27156us loss 21% Oct 19 13:23:22 dpinger 19498 WAN_PPPOE 8.8.8.8: Alarm latency 58050us stddev 22253us loss 21% Oct 19 13:14:02 dpinger 19498 WAN_PPPOE 8.8.8.8: Alarm latency 61951us stddev 22204us loss 21% Oct 19 12:23:24 dpinger 4156 WAN_PPPOE 8.8.8.8: Alarm latency 68757us stddev 6234us loss 21% Oct 19 12:21:29 dpinger 4156 WAN_PPPOE 8.8.8.8: Alarm latency 73096us stddev 33525us loss 21% Oct 19 12:31:33 dpinger 19498 WAN_PPPOE 8.8.8.8: Clear latency 42567us stddev 8611us loss 5% Oct 19 13:20:57 dpinger 19498 WAN_PPPOE 8.8.8.8: Clear latency 45311us stddev 30738us loss 10% Oct 19 13:24:20 dpinger 19498 WAN_PPPOE 8.8.8.8: Clear latency 50155us stddev 18800us loss code_text -
Looks like those logs are not in time order but that looks like real latency on the WAN though.
Check the Status > Monitoring graphs to see how it varies over time.
-
@stephenw10 said in pfsense router behind a ZTE H1600:
Looks like those logs are not in time order but that looks like real latency on the WAN though.
Check the Status > Monitoring graphs to see how it varies over time.
Hey Steve. Thought I'd report back about my issue.
It looks like that ''double NAT'' was causing that latency problem.
I disabled VDSL NAT within ZTE settings leaving pfsense to do the job. I think I haven't had any problem ever since I changed that.Could that be what was causing the problem?
-
Hmm, I wouldn't expect that to introduce any significant latency to be honest. Unless it was hitting some limit in the ZTE router. Commonly that can be a state limit with low end routers but I wouldn;t expect that to hit gateway monitoring as it's one of the first states created.
Steve
-
@stephenw10 said in pfsense router behind a ZTE H1600:
Hmm, I wouldn't expect that to introduce any significant latency to be honest. Unless it was hitting some limit in the ZTE router. Commonly that can be a state limit with low end routers but I wouldn;t expect that to hit gateway monitoring as it's one of the first states created.
Steve
I was expecting / hoping that was the problem. :(
I will keep an eye out if the problem's still there in the next few hours. -
It could be you are bypassing some other features in the ZTE router by passing the connection through. It might have some traffic shaping for example.
-
Hi Steve,
Just wanted to update my situation.
An electrician came in to check the line and wiring and also changed the phone socket however nothing's changed unfortunately. It might be slightly better but I'm still getting latency alerts here and there.Would a roll-back to a previous depreciated pfsense version help my situation? There's a video on youtube on which the user ended going back to 2.4.4 - that helped to mitigate the problem.
-
I would not expect it to. And it's almost impossible to recommend doing something like that from a security stand point. Except maybe purely as a test.
Steve
