nanog mailing list archives
Re: ECN
From: Baldur Norddahl <baldur.norddahl () gmail com>
Date: Wed, 13 Nov 2019 19:40:53 +0100
ZTE M6000-S V3.00.20(3.40.1) We are moving away from this platform so I can not be bothered with requesting a fix. In the past they have made fixes for us, so I believe they would also fix this issue if we asked them to do so. Also I would like to state that I have not personally verified that the equipment is doing hashing based on the ECN bits. I just turned off ECMP so the customer can test. If it works we will either let ECMP stay off or move the customer to the new platform. Regards, Baldur On Wed, Nov 13, 2019 at 7:30 PM Mikael Abrahamsson <swmike () swm pp se> wrote:
On Wed, 13 Nov 2019, Baldur Norddahl wrote:In any case, is it not recommended that users of anycast proxy packets that arrive at the wrong place? To avoid this kind of issue.In typical anycast deployments there is no feasible way to figure out where the "right place" is. It would be very interesting if your could share what equipment you're using that is doing ECMP hashing based on ECN bits. That vendor needs to fix that or people should avoid their devices. -- Mikael Abrahamsson email: swmike () swm pp se
Current thread:
- ECN Baldur Norddahl (Nov 11)
- Re: ECN Saku Ytti (Nov 13)
- Re: ECN William Herrin (Nov 13)
- Re: ECN Lukas Tribus (Nov 13)
- Re: ECN Saku Ytti (Nov 14)
- Re: ECN Tore Anderson (Nov 13)
- Re: ECN Warren Kumari (Nov 13)
- TCP and anycast (was Re: ECN) Anoop Ghanwani (Nov 13)
- Re: TCP and anycast (was Re: ECN) Bill Woodcock (Nov 14)
- Re: TCP and anycast (was Re: ECN) William Herrin (Nov 14)