Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

The cli tool as you said is great as it has no browser overheads or manipulation to mess with it.

Carl like you I have a 10gbit pfSense VM on a server, and behind that is another VM connected on a virtual switch hosting some game mod files which can push over 1gbit of second traffic fed by spindles.

This doesnt really surprise me, the fault response is kind of dumbed down largely because of cost constraints imposed by ofcom, and also the enforced separation between openreach and consumer, which then means you have to traverse the CP triage system as well and hope they dont muddle the message by the time it gets to openreach, I can imagine all these fault reports were treated as individual faults instead as a collective until a very late stage.

diapers

Bishop as the

torn ticket inspector

algebraic

party streamers

Yes. 

(And the marmalade.    )

parodies

If you are using the HG612 as a modem then ping and traceroute may not work as it wont necessarily have a gateway defined and is generally not advised to do so (the modem has no need for an Internet connection).

The only thing that might be useful is configuring NTP on the HG612 to get the time from pfSense (the LAN IP).  NTP Server can simply be enabled from Services -> NTP, you shouldn't need to change the default configuration except to make sure Interface is the LAN interface and possibly the HG612 port, if you haven't bridged the LAN and HG612 ports into a single network.

That makes sense - though I'd enabled NTP autosync on the HG612 and the time had changed in the log entries, so it had found a way out to the internet somehow. That said, the diag ping to 127.0.0.1 and local ip were the only destinations I could find to pass!

But meantime I think I've found the issue. If I disable the pfSense OPT1 interface (connected to the LAN2 port) then internet service resumes. So I guess some routing tables got updated and internet traffic was routed away from the WAN PPPoE interface .... odd that it takes such a variable amount of time for that to happen ... will have to do some more digging.