Technical Discussion
  >> Technical Issues


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User kirbyan
(newbie) Sun 09-Feb-14 14:11:43
Print Post

BT traffic problem?


[link to this post]
 
Symptoms:

Most noticeably, accessing shared hosting sites such as www.marlowcc.org becomes very slow. There's 60-80% packet loss between me and the server.

PING marlowcc.org (64.34.157.150): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 64.34.157.150: icmp_seq=3 ttl=47 time=111.811 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 64.34.157.150: icmp_seq=6 ttl=47 time=110.837 ms
Request timeout for icmp_seq 7
64 bytes from 64.34.157.150: icmp_seq=8 ttl=47 time=110.842 ms
64 bytes from 64.34.157.150: icmp_seq=9 ttl=47 time=110.851 ms
64 bytes from 64.34.157.150: icmp_seq=10 ttl=47 time=111.227 ms
64 bytes from 64.34.157.150: icmp_seq=11 ttl=47 time=110.421 ms
64 bytes from 64.34.157.150: icmp_seq=12 ttl=47 time=110.008 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 64.34.157.150: icmp_seq=15 ttl=47 time=110.550 ms
64 bytes from 64.34.157.150: icmp_seq=16 ttl=47 time=110.362 ms
Request timeout for icmp_seq 17
64 bytes from 64.34.157.150: icmp_seq=18 ttl=47 time=110.290 ms
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 64.34.157.150: icmp_seq=22 ttl=47 time=112.711 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
64 bytes from 64.34.157.150: icmp_seq=27 ttl=47 time=180.673 ms
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32

Traceroute seems to get only as far as linx (hop11)...

traceroute to marlowcc.org (64.34.157.150), 64 hops max, 52 byte packets
1 bthomehub (192.168.1.254) 1.051 ms 0.727 ms 0.720 ms
2 172.16.14.4 (172.16.14.4) 14.516 ms 13.796 ms 13.142 ms
3 * 213.120.158.174 (213.120.158.174) 18.115 ms 17.677 ms
4 213.120.158.173 (213.120.158.173) 13.938 ms 14.382 ms 15.497 ms
5 212.140.206.98 (212.140.206.98) 17.627 ms 18.067 ms 17.780 ms
6 217.41.169.211 (217.41.169.211) 17.763 ms 17.781 ms 17.739 ms
7 217.41.169.109 (217.41.169.109) 19.014 ms 17.975 ms 18.155 ms
8 acc2-xe-1-3-0.sf.21cn-ipp.bt.net (109.159.251.203) 17.870 ms
acc2-xe-0-0-3.sf.21cn-ipp.bt.net (109.159.251.207) 17.863 ms
acc2-xe-1-2-0.sf.21cn-ipp.bt.net (109.159.251.195) 17.242 ms
9 core2-te0-2-3-0.ealing.ukcore.bt.net (109.159.251.147) 29.046 ms
core2-te0-2-4-0.ealing.ukcore.bt.net (109.159.251.143) 30.707 ms
core1-te-0-4-0-16.ilford.ukcore.bt.net (109.159.251.51) 28.016 ms
10 peer1-xe11-1-0.telehouse.ukcore.bt.net (109.159.254.112) 24.893 ms 25.685 ms
peer1-xe11-0-0.telehouse.ukcore.bt.net (109.159.254.124) 24.130 ms
11 10ge.xe-0-0-0.linxb.ldn-teleh-dis-1.peer1.net (195.66.224.156) 98.740 ms * *
12 * * *
13 * * *

This looks to me like an internal BT issue, but... if I reboot the Home Hub 5 and let it reconnect, all is fine for a short time - the more the connection is used the worse it becomes.

Accessing big commercial sites like flickr, ebay, tumblr seem less affected than single host wordpress type sites, but do seem to bog down occasionally especially if it's a week or more since rebooting the Hub5 - which is then cured by a Hub5 reboot.

If I now tether my computer to my iphone or ipad and connect via either 3's 3G service or EE 4G all is fine.

HH5 reports:

1. Product name: BT Home Hub
2. Serial number:
3. Firmware version: Software version 4.7.5.1.83.8.173.1.6 (Type A) Last updated 03/01/14
4. Board version: BT Hub 5A
5. VDSL uptime: 0 days, 00:20:13
6. Data rate: 6803 / 26668
7. Maximum data rate: 6791 / 31278
8. Noise margin: 6.8 / 6.2
9. Line attenuation: 0.0 / 24.1
10. Signal attenuation: 0.0 / 21.8
11. Data sent/received: 66.3 MB / 7.6 MB

I see a lot of messages in the log like this:

13:41:45, 09 Feb. OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.64:63339-​>173.194.34.70:443 on ppp3)
13:41:42, 09 Feb. IN: BLOCK [12] Spoofing protection (IGMP 86.129.64.60-​>224.0.0.22 on ppp3)
13:41:36, 09 Feb. OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.64:63339-​>173.194.34.70:443 on ppp3)
13:41:36, 09 Feb. IN: BLOCK [15] Default policy (TCP 2.16.64.224:443-​>86.129.64.60:49225 on ppp3)
13:41:34, 09 Feb. IN: BLOCK [15] Default policy (TCP 54.239.36.9:443-​>86.129.64.60:49231 on ppp3)

Any ideas, anyone?

Thanks

Andy
Standard User Iakonalol
(newbie) Wed 19-Feb-14 16:42:11
Print Post

Re: BT traffic problem?


[re: kirbyan] [link to this post]
 
Having the same issue on a different ISP. Probably an issue with the site itself. Have a 30mb line with VM and still getting ping of around 80-90, and the trace (whilst not going through as many hops as yours is still quite large.

May possibly be a routing issue either way...
  Print Thread

Jump to