Menu
Reply
  • 72
  • 1
  • 7
andf
Dialled in
228 Views
Message 1 of 3
Flag for a moderator

Packet Loss

Hello,

I am not sure what is the best forum to start this thread in, so I am just pasting the one I made in Speed".

@Admins: Please delete one if required.

 

I have been experience a severely degraded performance for a week or so, with a constant packet loss.

My online services are not usable, I can only browse.

The connection parameters seem to be fine, i.e. the same I was seeing before, so I run a continuous ping to the first two IPs visibile in a traceroute to bbc.co.uk

Results below:

Reply from 62.252.114.121: bytes=32 time=11ms TTL=62
Reply from 62.252.114.121: bytes=32 time=10ms TTL=62
Reply from 62.252.114.121: bytes=32 time=8ms TTL=62
Request timed out.
Request timed out.
Request timed out.
Reply from 62.252.114.121: bytes=32 time=11ms TTL=62
Reply from 62.252.114.121: bytes=32 time=12ms TTL=62
Reply from 62.252.114.121: bytes=32 time=8ms TTL=62
Reply from 62.252.114.121: bytes=32 time=9ms TTL=62
Request timed out.
Reply from 62.252.114.121: bytes=32 time=18ms TTL=62
Reply from 62.252.114.121: bytes=32 time=11ms TTL=62
Reply from 62.252.114.121: bytes=32 time=7ms TTL=62

Ping statistics for 62.252.114.121:
Packets: Sent = 824, Received = 738, Lost = 86 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 94ms, Average = 10ms

++++++++++++++++++++++++++++++++++++++++++++

Reply from 213.46.174.118: bytes=32 time=11ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Reply from 213.46.174.118: bytes=32 time=15ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Reply from 213.46.174.118: bytes=32 time=17ms TTL=59
Reply from 213.46.174.118: bytes=32 time=14ms TTL=59
Reply from 213.46.174.118: bytes=32 time=9ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Request timed out.
Reply from 213.46.174.118: bytes=32 time=13ms TTL=59
Reply from 213.46.174.118: bytes=32 time=17ms TTL=59
Reply from 213.46.174.118: bytes=32 time=12ms TTL=59
Reply from 213.46.174.118: bytes=32 time=11ms TTL=59
Reply from 213.46.174.118: bytes=32 time=17ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Reply from 213.46.174.118: bytes=32 time=10ms TTL=59
Reply from 213.46.174.118: bytes=32 time=9ms TTL=59

Ping statistics for 213.46.174.118:
Packets: Sent = 957, Received = 904, Lost = 53 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 101ms, Average = 13ms

Downstream:

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1299000000238256 qam21
2403000000140256 qam28
33950000001.239256 qam27
43870000000.740256 qam26
53790000001.538256 qam25
63230000002.238256 qam24
73150000001.938256 qam23
8307000000238256 qam22
9291000000240256 qam20
102830000001.538256 qam19
112750000001.738256 qam18
122670000001.738256 qam17
13259000000238256 qam16
142510000001.938256 qam15
15243000000238256 qam14
162350000002.438256 qam13
172270000002.438256 qam12
182190000002.738256 qam11
192110000002.538256 qam10
202030000003.238256 qam9
211950000003.538256 qam8
221870000003.938256 qam7
23179000000440256 qam6
24171000000438256 qam5

 

Upstream:

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

16030000048.3512064 qam1
25370000048512064 qam2
33940000046.5512064 qam4
44620000047.5512064 qam3

 

Thanks!

0 Kudos
Reply
  • 72
  • 1
  • 7
andf
Dialled in
187 Views
Message 2 of 3
Flag for a moderator

Re: Packet Loss

Adding more information:

It is a wired connection, log posted below. 

Time Priority Description
2018-12-18 03:58:24.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-19 08:32:03.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-19 12:35:48.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-20 22:53:17.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-21 00:37:10.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-21 19:20:48.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 02:33:00.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 09:42:55.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 13:07:24.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 16:53:58.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


+++ Start of the issue +++
2018-12-23 00:05:05.00 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-23 01:35:49.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-26 01:43:28.00 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-26 09:08:05.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-26 12:58:18.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-26 20:11:13.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-27 07:14:25.00 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-27 07:27:38.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-27 21:20:04.00 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 72
  • 1
  • 7
andf
Dialled in
140 Views
Message 3 of 3
Flag for a moderator

Re: Packet Loss

Hello,

Issue is still present, as reported by several other threads on this forum:

0 Kudos
Reply