Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>,
	ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] [Cake]  The two SCE tests I have in mind
Date: Mon, 1 Apr 2019 09:02:58 -0700	[thread overview]
Message-ID: <20190401090258.144ff939@shemminger-XPS-13-9360> (raw)
In-Reply-To: <11555.1553430723@dooku.sandelman.ca>

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 :-)
> 
> 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.

  reply	other threads:[~2019-04-01 16:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw5bsQLo0QJbE0cke-mgr9DwEYM0F9E-RYmGqSTWFe+qrA@mail.gmail.com>
     [not found] ` <CAB6BA96-AF64-4A16-A5D2-2EAD065F303A@darbyshire-bryant.me.uk>
     [not found]   ` <3F3F78F9-8F97-42F2-9005-F8449489BECF@gmail.com>
     [not found]     ` <CAA93jw6BMggHXcYoqfFS2e0iuB54iMr+q+BWv720Z4zfaMb5gw@mail.gmail.com>
     [not found]       ` <42B7B2FB-94FC-4CA6-B75E-CADB61FE3173@gmail.com>
     [not found]         ` <6047E899-078F-4E08-A29C-B87D268A4E5E@heistp.net>
     [not found]           ` <69EA569B-4AD2-4C4B-937B-9ABDD563B120@gmail.com>
2019-03-24  8:55             ` [Ecn-sane] " Dave Taht
2019-03-24  9:30               ` [Ecn-sane] [Cake] " 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               ` [Ecn-sane] " Pete Heist
2019-03-24 11:08                 ` Jonathan Morton
2019-03-24 11:21                   ` Pete Heist
2019-03-24 12:32                   ` Michael Richardson
2019-04-01 16:02                     ` Stephen Hemminger [this message]
2019-04-01 17:21                       ` [Ecn-sane] [Cake] " Dave Taht
2019-04-02 13:36                       ` Rodney W. Grimes

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

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

  git send-email \
    --in-reply-to=20190401090258.144ff939@shemminger-XPS-13-9360 \
    --to=stephen@networkplumber.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    /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