cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
2,787 Views
Message 1 of 5

ping in the high 100,s speed under 0.50mbps

Not sure what is going on here , have had this for 3 days now , ping in the high 100's , packet loss , speed dropped to under 0.50mbps , have copied a sample from hub records , anyone make any sense of it :-

14:11:31, 13 Jun.IN: BLOCK [16] Remote administration (TCP [218.77.79.43]:38952-​>[86.142.160.52]:8080 on ppp0)
14:05:51, 13 Jun.IN: BLOCK [16] Remote administration (ICMP type 8 code 0 129.82.138.44-​>86.142.160.52 on ppp0)
13:58:03, 13 Jun.IN: BLOCK [16] Remote administration (TCP [61.183.128.6]:58584-​>[86.142.160.52]:8080 on ppp0)
13:56:19, 13 Jun.IN: BLOCK [16] Remote administration (TCP [199.203.59.117]:26600-​>[86.142.160.52]:80 on ppp0)
13:54:58, 13 Jun.( 9302.250000) Admin login successful by 192.168.1.64 on HTTP
13:54:45, 13 Jun.( 9289.050000) New GUI session from IP 192.168.1.64
13:47:30, 13 Jun.IN: BLOCK [16] Remote administration (ICMP type 8 code 0 195.251.255.69-​>86.142.160.52 on ppp0)
13:40:07, 13 Jun.IN: BLOCK [16] Remote administration (TCP [43.255.188.131]:45629-​>[86.142.160.52]:22 on ppp0)
13:35:29, 13 Jun.IN: BLOCK [16] Remote administration (ICMP type 8 code 0 72.73.28.82-​>86.142.160.52 on ppp0)
13:05:05, 13 Jun.IN: BLOCK [16] Remote administration (TCP [222.186.34.30]:22347-​>[86.142.160.52]:8080 on ppp0)
12:54:27, 13 Jun.IN: BLOCK [16] Remote administration (ICMP type 8 code 0 203.178.148.19-​>86.142.160.52 on ppp0)
12:47:58, 13 Jun.IN: BLOCK [16] Remote administration (TCP [61.183.128.6]:55359-​>[86.142.160.52]:8080 on ppp0)
12:36:11, 13 Jun.IN: BLOCK [16] Remote administration (TCP [185.22.172.103]:45156-​>[86.142.160.52]:8080 on ppp0)
12:21:54, 13 Jun.IN: BLOCK [16] Remote administration (TCP [178.190.136.238]:58512-​>[86.142.160.52]:80 on ppp0)
12:10:37, 13 Jun.IN: BLOCK [16] Remote administration (TCP [61.183.128.6]:52145-​>[86.142.160.52]:8080 on ppp0)
12:00:56, 13 Jun.IN: BLOCK [16] Remote administration (TCP [61.139.5.22]:3938-​>[86.142.160.52]:22 on ppp0)
11:52:57, 13 Jun.( 1981.460000) Port forwarding rule deleted via UPnP/TR064. Protocol: UDP, external ports: any-​>49803, internal ports: 49803, internal client: 192.168.1.64
11:52:02, 13 Jun.IN: BLOCK [12] Spoofing protection (IGMP 86.142.160.52-​>224.0.0.22 on ppp0)
11:52:00, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 88.147.134.70-​>86.142.160.52 fragment_offset=1456)
11:51:48, 13 Jun.( 1912.480000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any-​>49803, internal ports: 49803, internal client: 192.168.1.64
11:51:44, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 91.4.23.250-​>86.142.160.52 fragment_offset=0)
11:51:27, 13 Jun.IN: BLOCK [4] Illegal packet options (TCP [130.185.16.29]:27032-​>[86.142.160.52]:53769 on ppp0)
11:51:12, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 92.145.84.71-​>86.142.160.52 fragment_offset=0)
11:51:06, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 223.205.216.182-​>86.142.160.52 fragment_offset=0)
11:51:05, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 36.75.37.36-​>86.142.160.52 fragment_offset=0)
11:51:01, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 223.205.216.182-​>86.142.160.52 fragment_offset=0)
11:51:01, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 178.68.218.86-​>86.142.160.52 fragment_offset=0)
11:50:53, 13 Jun.( 1857.410000) Port forwarding rule deleted via UPnP/TR064. Protocol: UDP, external ports: any-​>50005, internal ports: 50005, internal client: 192.168.1.64
11:50:53, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 46.48.156.199-​>86.142.160.52 on ppp0)
11:50:50, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 11 code 0 185.40.80.1-​>86.142.160.52 on ppp0)
11:50:49, 13 Jun.BLOCKED 2 more packets (because of ICMP replay)
11:50:48, 13 Jun.BLOCKED 3 more packets (because of ICMP replay)
11:50:47, 13 Jun.BLOCKED 2 more packets (because of ICMP replay)
11:50:46, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 11 code 0 185.40.80.1-​>86.142.160.52 on ppp0)
11:50:46, 13 Jun.BLOCKED 1 more packets (because of ICMP replay)
11:50:46, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 217.159.171.17-​>86.142.160.52 on ppp0)
11:50:45, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 79.100.246.164-​>86.142.160.52 on ppp0)
11:50:42, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 212.88.10.223-​>86.142.160.52 on ppp0)
11:50:41, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 88.20.9.91-​>86.142.160.52 on ppp0)
11:50:41, 13 Jun.BLOCKED 3 more packets (because of ICMP replay)
11:50:40, 13 Jun.BLOCKED 1 more packets (because of Defragmentation failed)
11:50:40, 13 Jun.BLOCKED 1 more packets (because of ICMP replay)
11:50:40, 13 Jun.IN: BLOCK [5] Fragmented packet (UDP 176.85.228.134-​>86.142.160.52 fragment_offset=0)
11:50:39, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 46.28.49.228-​>86.142.160.52 fragment_offset=8880)
11:50:39, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 46.28.49.228-​>86.142.160.52 fragment_offset=5920)
11:50:39, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 46.28.49.228-​>86.142.160.52 fragment_offset=4440)
11:50:39, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 46.28.49.228-​>86.142.160.52 fragment_offset=2960)
11:50:39, 13 Jun.IN: BLOCK [5] Fragmented packet (IP 46.28.49.228-​>86.142.160.52 fragment_offset=1480)
11:50:39, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 122.5.19.122-​>86.142.160.52 on ppp0)
11:50:39, 13 Jun.BLOCKED 2 more packets (because of ICMP replay)
11:50:39, 13 Jun.OUT: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [95.31.163.213]:27032-​>[192.168.1.64]:27032 on br0)
11:50:39, 13 Jun.BLOCKED 7 more packets (because of Defragmentation failed)
11:50:39, 13 Jun.IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 193.33.33.138-​>86.142.160.52 on ppp0)
11:50:38, 13 Jun.OUT: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [78.171.146.44]:27032-​>[192.168.1.64]:27032 on br0)
11:50:38, 13 Jun.BLOCKED 7 more packets (because of Defragmentation failed)
11:50:37, 13 Jun.OUT: BLOCK [53] Defragmentation failed (Fragmented packet, packet exceeds: UDP [92.253.35.228]:27032-​>[192.168.1.64]:27032 on br0)
0 Ratings
4 REPLIES 4
Highlighted
Guru
Guru
2,777 Views
Message 2 of 5

Re: ping in the high 100,s speed under 0.50mbps

Hi @nicco1965

 

Looking at the log, you have a few fragmented datagrams being produced.

 

Can you please connect a computer to the router/Homehub with a wired Ethernet connection and open up cmd (Windows) or Terminal (Unix) and ping bbc.co.uk

Then post the results here.


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
Highlighted
Contributor
2,760 Views
Message 3 of 5

Re: ping in the high 100,s speed under 0.50mbps

Hi,

 

Just did that ping test :- packets sent 4 , recieved 4 , lost 0  , round trip minium 1344ms , maximum 1562 , average 1444ms ,  also just ran a speed test and got 0.58 mbps , i always use ethernet cable as a play alot of online games but as you proably can guess  i am not able to do this at the moment with a ping of over 1000ms

Tags (1)
0 Ratings
Highlighted
Contributor
2,717 Views
Message 4 of 5

Re: ping in the high 100,s speed under 0.50mbps

hello , might be time for a mod to have a look and see what is going on , i got a DSL rate of 1.51mbps which is what i always get , i live in rural area and about 5kms from exchange so i know that i will never get a good speed , just did a speed test and with no devices connected , only my pc , using test socket , always use ethernet cable , even though the dsl rate is 1.51 mbps the speed test just gave me a result of 0.52mbps with a ping of 1477 ms , it has been like this for 4 days now . My usually speed is 1.20mbps with a ping of 25ms .

0 Ratings
Highlighted
Distinguished Sage
2,712 Views
Message 5 of 5

Re: ping in the high 100,s speed under 0.50mbps

Hi Welcome to the community forums
Here is a basic guide to getting help from the community members done by CL Keith Please read through the link posted http://forumhelp.dyndns.info/speed/first_steps.html
once you have posted the information asked for then the community members can help you more

if using a hub 4 locate these lines located in the hub logs
Lines should look like this
19:11:29, 07 Nov. (2290101.460000) DSL noise margin: 7.00 dB upstream, 6.10 dB downstream
19:11:29, 07 Nov. (2290101.390000) DSL line rate: 448 Kbps upstream, 288 Kbps downstream

Thank You
This is a customer to customer self help forum the only BT presence here are the forum moderators
0 Ratings