News for hackers. Stuff that matters.

frnkblk

Re:Service provider story about tracking down TCP RSTs on Monday September 03, 2018 @03:06PM (#17904329)
You are correct, the problem started only after placing new Arista border routers. The previous border routers were not doing ECMP. The issue was a combination of the use of anycast, diverse Internet transit egress, this model of Arista defaulting to using the packet's TTL in its ECMP hash calculations, and the end-customer router CPE egressing packets that are part of the same TCP connection with variable TTL values. Change any one of those items and the issue would not have shown up.
Re:Service provider story about tracking down TCP RSTs on Monday September 03, 2018 @01:59AM (#17900643)
The Arista units are 7504N which are running 4.20 or later, and I believe they use the Arad or Petra chpiset.
Re:Service provider story about tracking down TCP RSTs on Monday September 03, 2018 @01:51AM (#17900608)
To clarify, the Arista routers are the ISP's border routers. It was the residential/business customers' SOHO routers, of various makes and models, that were not decrementing the initial TCP SYN.