From: Curtis Villamizar <curtis@ipv6.occnc.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Wesley Eddy <wes@mti-systems.com>,
bloat <bloat@lists.bufferbloat.net>,
"Fred Baker \(fred\)" <fred@cisco.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Cerowrt-devel] [aqm] [Bloat] ping loss "considered harmful"
Date: Thu, 05 Mar 2015 13:56:33 -0500 [thread overview]
Message-ID: <201503051856.t25IuXok099060@maildrop31.somerville.occnc.com> (raw)
In-Reply-To: Your message of "Tue, 03 Mar 2015 21:24:59 -0800." <CAA93jw4F7iffbTRUt5RFsF0wgoOAXPUVHdu7JESVq4uM17cm7A@mail.gmail.com>
In message <CAA93jw4F7iffbTRUt5RFsF0wgoOAXPUVHdu7JESVq4uM17cm7A@mail.gmail.com>
Dave Taht writes:
> My point was A), I have seen tons of shapers out there that actually
> prioritize ping over other traffic. I figure everyone here will agree
> that is a terrible practice, but I can certainly say it exists, as it
> is a dumb mistake replicated in tons of shapers I have seen... that
> makes people in marketing happy.
>
> Already put up extensive commentary on that bit of foolishness on
> "wondershaper must die".
Its possible to detect such a shaper prioritizing ICMP echo/reply by
doing a an HTTP fetch concurrent with a ping and then and see if the
TCP data packet get significantly delayed relative to the ICMP echo
and echo reply packets. You'd have to do a tcpdump and match the ICMP
echo to the echo reply and see if later the ICMP RTT looks very
different from the TCP RTT. It might be that the SYN and SYN ACK are
not delayed but the plain old TCP date packets are.
If anyone has a small amount of spare time and wants to put together a
shell script its certainly doable.
Curtis
next prev parent reply other threads:[~2015-03-05 19:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 3:57 [Cerowrt-devel] " Dave Taht
2015-03-02 4:00 ` [Cerowrt-devel] [aqm] " Andrew Mcgregor
2015-03-02 4:05 ` Mikael Abrahamsson
2015-03-02 4:06 ` [Cerowrt-devel] " David Lang
2015-03-02 9:40 ` [Cerowrt-devel] [aqm] " Brian Trammell
2015-03-02 10:17 ` Mikael Abrahamsson
2015-03-02 10:54 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-03-02 12:44 ` dpreed
2015-03-02 14:45 ` Brian Trammell
2015-03-02 18:41 ` David Lang
2015-03-03 6:45 ` [Cerowrt-devel] " Valdis.Kletnieks
2015-03-04 8:14 ` Mikael Abrahamsson
2015-03-02 21:53 ` Joe Touch
2015-03-02 23:14 ` David Lang
2015-03-02 23:25 ` Joe Touch
2015-03-02 23:34 ` David Lang
2015-03-03 0:07 ` Andrew Mcgregor
2015-03-02 10:47 ` Dave Dolson
2015-03-02 10:49 ` Andrew Mcgregor
2015-03-02 18:36 ` David Lang
[not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:33 ` Dave Dolson
2015-03-02 20:39 ` David Lang
2015-03-02 20:38 ` Dave Taht
2015-03-04 8:12 ` Mikael Abrahamsson
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29 ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2015-03-03 18:00 ` [Cerowrt-devel] [aqm] [Bloat] " Fred Baker (fred)
2015-03-04 5:24 ` Dave Taht
2015-03-05 18:56 ` Curtis Villamizar [this message]
2015-03-05 19:50 ` [Cerowrt-devel] [Bloat] [aqm] " Rich Brown
2015-03-04 17:34 ` [Cerowrt-devel] [aqm] [Bloat] " dpreed
2015-03-04 19:45 ` Mikael Abrahamsson
2015-03-05 20:38 ` [Cerowrt-devel] " Matt Taggart
2015-03-05 20:53 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201503051856.t25IuXok099060@maildrop31.somerville.occnc.com \
--to=curtis@ipv6.occnc.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=fred@cisco.com \
--cc=wes@mti-systems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox