Have I set this up right or am I being stupid?
-
@stephenw10 The gateway changes between 2, 244 and 243. 244 seems to never respond yet 243 does. My ISP has advised these are gateways to their network not the internet breakout.
I never actually set the gateway it appears to be picked up from PPPoE.
I've added as you suggest and will see what happens.
-
Yeah, the ISPs gateway does not have to respond to ping. My own connections, with BT, do not. Setting an external monitor gives better data anyway.
The gateway should only ever change between PPPoE sessions. If you are seeing it change that implies the PPP session is bouncing which would definitely break open connections.
Steve
-
@stephenw10 Well I'll run it like this and see what happens. The missus plays Sea of Thieves and i don't think i can take anymore "IT'S DONE IT AGAIN!!" conversations lol.
We do have an AltNet threating to install symmetric 1Gbps fibre which would be a godsend for the ISOs i have to send around and means i can drop a point of failure (the Vigor166) out of the network loop.
As an aside this is what my TBB quality check looks like when pfsense shows the 244 gateway.
That to me looks like congestion but my ISP assures me that is just TBB just misreporting. -
Are you on g.fast? Is that an imported V166? When I was looking into this (which was a while back!) Draytek hadn't started selling those in the UK yet.
Yeah that graph looks bad. See what the pfSense monitoring graphs look like against 8.8.8.8 after a while. I wouldn't really expect any packet loss unless you're filling the WAN entirely.
Steve
-
@stephenw10 No not on g.fast and i bought it in the UK
-
Mmm, interesting. Let's see what pfSense shows against 8.8.8.8 then.
This is what my WANs look like over 2 days:
0% loss on both and minimal latency change. WAN is standard FTTC VDSL, WAN2 is g.fast.
That's monitoring against 8.8.8.8 and 8.8.4.4.Steve
-
@stephenw10 Where is that graph hiding? I'm still getting used to the interface
-
In Status > Monitoring. Hit the 'wrench' icon to configure the graph.
-
@stephenw10 Thank you again for your help, i'll report back in a few days :)
-
So ran it with your suggested change for 2 days.
That is just a 80/20 FTTC connection but i think i have been banded as my Draytek show interleaving on the down stream.
Hopefully DLM will kick in after a few days and sort it out.
-
If you enable the WAN traffic graph on the other axis you can check to see if you were moving a lot of traffic when you saw the packet loss and latency. I don't really expect to see any loss.
I still use an old HG612 there and my line looks similar:
# xdslcmd info --state --stats xdslcmd: ADSL driver and PHY status Status: Showtime Retrain Reason: 0 Last initialization procedure status: 0 Max: Upstream rate = 26292 Kbps, Downstream rate = 73580 Kbps Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 66999 Kbps Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps Link Power State: L0 Mode: VDSL2 Annex B VDSL2 Profile: Profile 17a TPS-TC: PTM Mode(0x0) Trellis: U:ON /D:ON Line Status: No Defect Training Status: Showtime Down Up SNR (dB): 8.1 15.3 Attn(dB): 13.6 0.0 Pwr(dBm): 14.0 3.0 -
@stephenw10 I see a few spikes (I expect steam updating)
-
Sorry for the delayed response been away for work.
It appears whatever was the cause has gone. Been over a week and no connection drops.
-
Nice, something upstream then. Good result.
-
@stephenw10 Afraid to say about 10:30am the internet died. This was followed by the usual unimpressed look from the wife as she was knee deep the the latest season of the witcher.
From the pfsense dashboard the WAN interface shows down
I can connect to the web GUI of the modem and that looks good.
From here i've done the usual tests.
VDSL Status
ping and nslookup from desktop
DNS lookup from pfsense
Monitoring from pfsense
Then I tried to even force it
Ultimately I went to the logs.
I rebooted pfsense, nothing. Rebooted the Draytek Vigor 166 modem and it came back to life. I'm kinda stumped at this point so going to ask Draytek support incase i've missed some sort of logging their box does but if you guys see anything i've missed please let me know.
-
Hmm, does it comes back up if you only reboot pfSense and not the modem?
You can see in the logs that it is seeing at least some response from Vodaphone's servers so the connection is making it that far.
If you manually close the connection while it is working correctly and then try to reconnect does it fail?
Steve
-
@stephenw10 Thanks for the response on a sunday, if i just reboot the pfsense VM the connection is still down which is why I may be leaning towards the modem now and have raised a support case with Draytek.
I'll try killing the connection later on today, I dare not get between her and Henry Cavill lol
-
Ha, yeah best avoid that!
-
@stephenw10 So from the status > interfaces section i downed the connection waited 10 seconds (why is it always 10 seconds in IT) then reconnected. Worked fine.
Just waiting on Draytek now.
-
Yeah, that seems to rule out some of the PPP issues I've seen in the past.
I guess you could try just rebooting the modem, that would seem to confirm it if it comes back up without doing anything in pfSense.
Steve
