TalkTalk and DSCP and 19 second latency: Difference between revisions
Appearance
Content deleted Content added
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
This page is about in interesting problem that was reported to us, by a customer, in December 2021. We have written this up so that this page can be found if other people are seeing a similar problem. |
This page is about in interesting problem that was reported to us, by a customer, in December 2021. We have written this up so that this page can be found if other people are seeing a similar problem. |
||
We've masked the IP we're pinging in this page as it doesn't matter what IP you ping - in our tests though we were mostly pinging the IP of our LNS, as that is the 'next hop' on the customer's route to the internet. |
We've masked the IP we're pinging in this page as it doesn't matter what IP you ping - in our tests though we were mostly pinging the IP of our LNS, as that is the 'next hop' on the customer's route to the internet. |
||
=TL;DR= |
=TL;DR= |
||
For some reason, TalkTalk's kit is reading IP DSCP marks from IPv4 |
For some reason, TalkTalk's kit is reading IP DSCP marks from IPv4 packets inside PPPoE, and then putting them in a funny queuing setup which results in latency quickly increasing to over 19 seconds: |
||
1408 bytes from x.x.x.x: icmp_seq=986 ttl=63 time='''19084.589 ms''' |
1408 bytes from x.x.x.x: icmp_seq=986 ttl=63 time='''19084.589 ms''' |
||