cancel
Showing results for 
Search instead for 
Did you mean: 
Guru
Guru
920 Views
Message 91 of 336

Re: Slow page browsing

Go to solution

Dear all,

 

If you are able to, below are some steps which may help BT Consumer and BT Wholesale.

 

2) If you can post a traceroute to bbc.co.uk. This is incase it is a particular node/router within the BT Wholesale network that is causing the issues.

 

Unix/Linix based OS: go to Terminal and type traceroute bbc.co.uk 

Windows based OS: go to cmd and type tracert bbc.co.uk 

 

disregard this - Issue with TCP not ICMP or UDP.

If you know how to use wireshark, try a wireshark capture. There should be a 3 way handshake, data request, acknowledgements, ect..

 

A connection over a secure socket (eg HTTPS) will also have the authentication exchange.

 

3) Please also provide your exchange name. You can find your exchange name by going to https://www.btwholesale.com/includes/adsl/main.html


jac_95 | BT.com Help Site | BT Service Status
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Try a Search
See if someone in the community had the same problem and how they got it resolved.
0 Ratings
MikeZ
Contributor
885 Views
Message 92 of 336

Re: Slow page browsing

Go to solution

@jac_95 wrote:

Dear all,

 

If you are able to, below are some steps which may help BT Consumer and BT Wholesale.

 


No, it won't really help. We've already established that it's TCP connections that are timing out - UDP and ICMP appear unaffected, so traceroutes aren't a useful diagnostic. Also, my IPv6 tunnel is fine (IP protocol 41), as are IPSec VPNs.

 

We've also explained that speed is not the issue, so speed tests aren't going to help.

 

Also, it's "Linux", not "Linix".

0 Ratings
MikeyC123
Contributor
1,011 Views
Message 93 of 336

Re: Slow page browsing

Go to solution
I'd love to but the diagnostics page is like any other, it hangs when you click submit and refreshing it just brings up the blank page again, tried about 5 times, no joy.
0 Ratings
MikeyC123
Contributor
992 Views
Message 94 of 336

Re: Slow page browsing

Go to solution
Ok, so what's your money on for something to be affecting so many people on a national scale all from different corners of the country ? One dodgy switch somewhere with a bad card ? An upgrade patch that has been distributed but messed up lots of switches. But why would some protocols be okay over others ? Which makes it very specific !
0 Ratings
Guru
Guru
987 Views
Message 95 of 336

Re: Slow page browsing

Go to solution

@MikeZ

 

Have you tried a wireshark capture test? Wonder if the handshake completes or not. The HTTPS connections carry more overheads so will be worse.

 

Sorry hit the i instead of u for Linux.


jac_95 | BT.com Help Site | BT Service Status
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Try a Search
See if someone in the community had the same problem and how they got it resolved.
0 Ratings
MikeZ
Contributor
921 Views
Message 96 of 336

Re: Slow page browsing

Go to solution
Yes, I've been looking at TCP handshakes and they are sometimes failing to complete. This is why IPv6 browsing doesn't appear to be affected - everything is wrapped in a protocol 41 packet and is bypassing whatever is causing this problem.

My own feeling is that the problems are connected with some part of the infrastructure that manipulates sessions in some way, e.g. transparent proxying or load balancing. I don't think it's a routing problem - they tend to affect more than just one protocol.
0 Ratings
wglidster
Beginner
904 Views
Message 97 of 336

Re: Poor browsing speed even with a connection speed of 40mb

Go to solution
Same here all day - does work if you hit the website twice , Usually reloads second time. It is obviously a BT Servers problem. we live in hope
0 Ratings
Guru
Guru
871 Views
Message 98 of 336

Re: Slow page browsing

Go to solution

@MikeZ

 

Just reinstalling my wireshark and x11 now, OSX 10.10.4 seems to have removed some of the x11 libraries.

Trying to reproduce the problem, though my BT broadband (ADSL) doesn't seem to be effected. 

 

The reason I said about the exchanges was to see what is in common between those who are effected.

The traceroute, until you pointed out it was only effecting TCP connections again my fault for not reading properly, was to see if they passed the same node.

 

Also are those effected just on a FTTC/P connection or are they also on a ADSL connection. Probably not related though.

 

The IP sessions are managed by the Radius servers which connects the user to the ISPs network/Home gateway.

 

 


jac_95 | BT.com Help Site | BT Service Status
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Try a Search
See if someone in the community had the same problem and how they got it resolved.
0 Ratings
MikeyC123
Contributor
843 Views
Message 99 of 336

Re: Slow page browsing

Go to solution
I don't know I relevant but I did a trace route to BBC web responses below, when I try an doing the first hop it works, but as soon as I use mtu size 1492 and don't fragment flag it fails, what I don't know is does it normally fragment or not, I'm guessing it doesn't seeing as this is recommended mtu size for bt fibre connection.

I'm afraid that's the extent of my comms tech knowledge,.....

Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

1 18 ms 13 ms 3 ms VIGOR2760 [192.168.0.1]
2 * * * Request timed out.
3 * 19 ms 19 ms 31.55.186.133
4 30 ms 19 ms 19 ms 31.55.186.156
5 19 ms 30 ms 20 ms 195.99.127.38
6 19 ms 30 ms 54 ms peer2-et-1-1-0.telehouse.ukcore.bt.net [213.121.193.163]
7 34 ms 34 ms 18 ms 194.74.65.42
8 * * * Request timed out.
9 20 ms 34 ms 34 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 22 ms 21 ms 21 ms 132.185.255.165
11 35 ms 34 ms 30 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.

Tracing route to www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

1 13 ms 3 ms 13 ms VIGOR2760 [192.168.0.1]
2 * * * Request timed out.
3 * 19 ms 19 ms 31.55.186.133
4 31 ms 19 ms 19 ms 31.55.186.164
5 19 ms 19 ms 29 ms core3-hu0-1-0-1.faraday.ukcore.bt.net [195.99.127.34]
6 19 ms 19 ms 31 ms peer2-et-1-1-0.telehouse.ukcore.bt.net [213.121.193.163]
7 19 ms 36 ms 29 ms 194.74.65.42
8 * * * Request timed out.
9 31 ms 20 ms 20 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 32 ms 21 ms 21 ms 132.185.255.165
11 31 ms 35 ms 20 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

Tracing route to www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms VIGOR2760 [192.168.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 19 ms 21 ms 21 ms 31.55.186.164
5 18 ms 19 ms 19 ms core3-hu0-1-0-1.faraday.ukcore.bt.net [195.99.127.34]
6 19 ms 19 ms 30 ms peer2-et-1-1-0.telehouse.ukcore.bt.net [213.121.193.163]
7 22 ms 19 ms 29 ms 194.74.65.42
8 * * * Request timed out.
9 20 ms 35 ms 31 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 21 ms 21 ms 21 ms 132.185.255.165
11 20 ms 19 ms 20 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

Pinging www.bbc.net.uk [212.58.244.67] with 1024 bytes of data:
Reply from 212.58.244.67: bytes=1024 time=36ms TTL=53
Reply from 212.58.244.67: bytes=1024 time=37ms TTL=53
Reply from 212.58.244.67: bytes=1024 time=36ms TTL=53
Reply from 212.58.244.67: bytes=1024 time=36ms TTL=53

Ping statistics for 212.58.244.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms

Pinging www.bbc.net.uk [212.58.244.67] with 1124 bytes of data:
Reply from 212.58.244.67: bytes=1124 time=39ms TTL=53
Reply from 212.58.244.67: bytes=1124 time=31ms TTL=53
Reply from 212.58.244.67: bytes=1124 time=31ms TTL=53
Reply from 212.58.244.67: bytes=1124 time=36ms TTL=53

Ping statistics for 212.58.244.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 39ms, Average = 34ms

Pinging www.bbc.net.uk [212.58.244.67] with 1224 bytes of data:
Reply from 212.58.244.67: bytes=1224 time=38ms TTL=53
Reply from 212.58.244.67: bytes=1224 time=36ms TTL=53
Reply from 212.58.244.67: bytes=1224 time=31ms TTL=53
Reply from 212.58.244.67: bytes=1224 time=37ms TTL=53

Ping statistics for 212.58.244.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 38ms, Average = 35ms
Value must be supplied for option -l324.

Pinging www.bbc.net.uk [212.58.244.66] with 1324 bytes of data:
Reply from 212.58.244.66: bytes=1324 time=39ms TTL=53
Reply from 212.58.244.66: bytes=1324 time=31ms TTL=53
Reply from 212.58.244.66: bytes=1324 time=37ms TTL=53
Reply from 212.58.244.66: bytes=1324 time=31ms TTL=53

Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 39ms, Average = 34ms

Pinging www.bbc.net.uk [212.58.244.66] with 1424 bytes of data:
Reply from 212.58.244.66: bytes=1424 time=37ms TTL=53
Reply from 212.58.244.66: bytes=1424 time=37ms TTL=53
Reply from 212.58.244.66: bytes=1424 time=32ms TTL=53
Reply from 212.58.244.66: bytes=1424 time=31ms TTL=53

Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 37ms, Average = 34ms

Pinging www.bbc.net.uk [212.58.244.66] with 1492 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ping request could not find host 213.121193.163. Please check the name and try again.

Pinging 213.121.193.163 with 1492 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 213.121.193.163:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
0 Ratings
mcjay669
Beginner
803 Views
Message 100 of 336

Weird issue with infinity 2

Go to solution
Hey guys over the last 24 hours I've been having this weird issue with my internet. For some reason no pages will load the first time round, I have to hit reload then it'll work. I have tried this over multiple devices and have reset everything but the issue still persists. Any one ever heard of this before/have any clue what could be causing it ?

Details: BT infinity 2 FTTC, BT Home Hub 3.
Tags (1)
0 Ratings