From: Rich Brown <richb.hanover@gmail.com>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] Meanwhile, over on NANOG...
Date: Tue, 12 Nov 2019 07:07:45 -0500 [thread overview]
Message-ID: <1CF67BBC-B528-4667-97AE-760DCE027466@gmail.com> (raw)
I saw this message crop up in the NANOG digest today... https://mailman.nanog.org/pipermail/nanog/2019-November/104045.html
Rich
> Message: 9
> Date: Mon, 11 Nov 2019 16:55:14 -0800
> From: Owen DeLong <owen@delong.com>
> To: Baldur Norddahl <baldur.norddahl@gmail.com>
> Cc: nanog@nanog.org
> Subject: Re: ECN
> Message-ID: <59956815-A2BB-4DA3-AD57-C746C49FD617@delong.com>
> Content-Type: text/plain; charset=utf-8
>
>
>
>> On Nov 11, 2019, at 05:01 , Baldur Norddahl <baldur.norddahl@gmail.com> wrote:
>>
>> Hello
>>
>> I have a customer that believes my network has a ECN problem. We do not, we just move packets. But how do I prove it?
>
> Are you saying that none of your routers support ECN or that you think ECN only applies to endpoints?
>
>> Is there a tool that checks for ECN trouble? Ideally something I could run on the NLNOG Ring network.
>>
>> I believe it likely that it is the destination that has the problem.
>
> I’d say start with asking the reporter to provide a PCAP of the problem and review the packet trace to provide clues of tap points
> in your network to investigate where ECN is (or should be) occurring and the opposite is occurring.
>
> Owen
>
next reply other threads:[~2019-11-12 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 12:07 Rich Brown [this message]
2019-11-12 12:20 ` Toke Høiland-Jørgensen
2019-11-12 12:25 ` Mikael Abrahamsson
2019-11-12 13:02 ` Toke Høiland-Jørgensen
2019-11-12 13:54 ` Luca Muscariello
2019-11-12 14:35 ` Toke Høiland-Jørgensen
2019-11-12 22:01 ` Toke Høiland-Jørgensen
2019-11-13 0:04 ` Rodney W. Grimes
2019-11-13 8:05 ` Luca Muscariello
2019-11-13 10:45 ` Toke Høiland-Jørgensen
2019-11-13 15:36 ` Rodney W. Grimes
2019-11-13 10:43 ` Toke Høiland-Jørgensen
2019-11-13 15:25 ` Rodney W. Grimes
2019-11-13 15:35 ` Toke Høiland-Jørgensen
2019-11-13 15:36 ` Luca Muscariello
2019-11-13 15:42 ` Rodney W. Grimes
2019-11-13 15:52 ` Toke Høiland-Jørgensen
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=1CF67BBC-B528-4667-97AE-760DCE027466@gmail.com \
--to=richb.hanover@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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