Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Michael Richardson <mcr@sandelman.ca>,
	Cake List <cake@lists.bufferbloat.net>,
	 ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane] The two SCE tests I have in mind
Date: Mon, 1 Apr 2019 19:21:48 +0200	[thread overview]
Message-ID: <CAA93jw526AuriYRUPcQ594GpSHvRV021bdmRmzOaNj5BnUY_JQ@mail.gmail.com> (raw)
In-Reply-To: <20190401090258.144ff939@shemminger-XPS-13-9360>

On Mon, Apr 1, 2019 at 6:03 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Sun, 24 Mar 2019 13:32:03 +0100
> Michael Richardson <mcr@sandelman.ca> wrote:
>
> > Jonathan Morton <chromatix99@gmail.com> wrote:
> >     >> On 24 Mar, 2019, at 12:05 pm, Pete Heist <pete@heistp.net> wrote:
> >     >>
> >     >> tcpdump -r file.pcap udp port 2112 and greater 80 and "ip[1] != 0x1”
> >     >>
> >     >> “greater 80” ignores the handshake packets and 0x1 is whatever TOS
> >     >> value we want to make sure the packets contain. We can use different
> >     >> filters for other traffic.
> >
> >     > Bear in mind that the TOS byte contains ECN as well as DSCP fields, and
> >     > the latter is left-justified.
> >
> > libpcap should probably learn about DSCN bits to avoid people having to
> > think so much :-)

Well, I still have nothing better than tcptrace + xplot.

> >
> > Send patches to me/github.


> >
>
> Libpcap is ancient history by now. It is like ifconfig, everyone still can't reprogram
> their brain; but the tool is on life support.
>
> All development is happening on wireshark/tshark.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

  reply	other threads:[~2019-04-01 17:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 19:15 [Cake] Sce In cake testers wanted Dave Taht
2019-03-23 21:28 ` Kevin Darbyshire-Bryant
2019-03-23 23:53   ` Jonathan Morton
2019-03-23 23:54     ` Dave Taht
2019-03-23 23:58       ` Jonathan Morton
2019-03-24  7:37         ` Pete Heist
2019-03-24  8:45           ` Jonathan Morton
2019-03-24  8:55             ` [Cake] The two SCE tests I have in mind Dave Taht
2019-03-24  9:30               ` Luca Muscariello
2019-03-24 10:30                 ` Dave Taht
2019-03-24 12:33                   ` Dave Taht
2019-03-24 22:31                   ` Sebastian Moeller
2019-03-24 11:05               ` Pete Heist
2019-03-24 11:08                 ` Jonathan Morton
2019-03-24 11:21                   ` Pete Heist
2019-03-24 12:32                   ` [Cake] [Ecn-sane] " Michael Richardson
2019-04-01 16:02                     ` Stephen Hemminger
2019-04-01 17:21                       ` Dave Taht [this message]
2019-04-02 13:36                       ` Rodney W. Grimes
2019-03-24 21:00   ` [Cake] Sce In cake testers wanted Kevin Darbyshire-Bryant

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw526AuriYRUPcQ594GpSHvRV021bdmRmzOaNj5BnUY_JQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    --cc=stephen@networkplumber.org \
    /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