Internet slow, webpage content delay response loading pages

[rcoleman-netgate]

@cxcmax With no internet connection (see line #1 -- your PPPoE isn't connecting it appears) you cannot get DNS updates to happen and time won't sync, either, since it's reliant on a DNS name.

Check on your gateway section to make sure you're up.

If you are online and you're zeroing out a 172.x.x.x gateway... you're not really helping yourself here brecause it makes it appear as though it's completely offline.

Does Status->Gateways show BT_WAN_PPOE is online or offline? What's the monitoring IP?

[NogBadTheBad]

@cxcmax Re the clock out by -1 hour GMT.

Is your Timezone set to /Etc/UTC rather than Europe/London ?

[rcoleman-netgate]

@nogbadthebad Shouldn't keep PPPoE from connecting.
dpinger is showing here that the gateways are both down.

[NogBadTheBad]

@rcoleman-netgate said in Internet slow, webpage content delay response loading pages:

@nogbadthebad Shouldn't keep PPPoE from connecting.
dpinger is showing here that the gateways are both down.

Not saying it won't, but it's misleading in the logs

[NogBadTheBad]

Looks like BT provide IPv6 over the IPv4 connectivity, so yes the PPPOE would be an issue if its down.

https://community.bt.com/t5/Home-setup-Wi-Fi-network/IPv6-amp-pfSense-with-BT-FTTP/m-p/2081157#M178789

[cxcmax]

@rcoleman-netgate

Hi
This is what I have, am I needing to change this?

Apology, @NogBadTheBad - time zone changed and now working.

Problems reply to individual posts

Chris

[rcoleman-netgate]

@cxcmax Check the logs -- if you're not getting a routable IP via the PPPoE it's a config issue.
You can also check with BT to see if they're stopping something.

But first I would change your Monitor IP for the BT_WAN_PPPOE gateway to something not the default/blank which will use your next step upstream. Find a public IP you can ping without recourse (Google DNS or CloudFlare works) and have that monitor.
After doing that reboot your firewall. This is the fastest way to clear out the dpinger monitor.

[stephenw10]

BT's gateways do not respond to ping generally. Set an external monitoring IP like 8.8.8.8.

[cxcmax]

Hi All

Just to say things are looking much better and thankyou for all the advise.

I managed to change the 'Monitor IP' via 'System / Routing / Gateways' The IPv6 option, I could not find a direct answer for this; Google search, so I assume for now it just the IPv4 I need to focus on. One other aspect, the Graphs that show the traffic are looking a lot better, I can see a bit clearly now what is going through my WAN side compared to LAN side; there is more of a detailed view for the LAN side and more of summary for the WAN if that makes any sense. A sample below what I mean:

Again thanks for the help.

Chris

[rcoleman-netgate]

@cxcmax You could presume that if IPv4 is running with BT that IPv6 is as well since it is running over a IPv4 relay and then just turn off the "Gateway Monitoring Action" in the BT_WAN_DHCP6 interface.

[stephenw10]

The BT link-local IPv6 gateway generally does respond to ping:

So you may have something misconfigured there.

Steve

[rcoleman-netgate]

@stephenw10
Looks like his suffix is different

[stephenw10]

Mmm, well spotted. Possibly 'Use IPv4 connectivity as parent interface' is not set and should be.

Steve

[cxcmax]

@stephenw10 said in Internet slow, webpage content delay response loading pages:

Use IPv4 connectivity as parent interface

Hi Noted and apology, just can see how I change "Use IPv4 connectivity as parent interface"
Chris

[stephenw10]

Can or can't see it? It's here in the DHCP6 client config section for the WAN. Here's what I have:

Steve

[cxcmax]

@stephenw10

I think I am being stupid here, for the life me I can not see this. Should it be easy to locate on the 2100 netgate?

[cxcmax]

Ignore me, it was starring in the face.

[cxcmax]

@stephenw10

Re: [Internet slow](webpage content delay response loading pages)

Eureka, got there in the end

I appreciate the help and patience, I will now go and back up the system before I start making an further changes.

I made the change via 'Interfaces / WAN (pppoe0), under 'DHCP Client Configuration' section

Chris

[stephenw10]

Nice. If you have LAN set to track WAN with a prefix value set you should also now see a valid public /64 applied to it.