[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Service provider story about tracking down TCP RSTs
- Subject: Service provider story about tracking down TCP RSTs
- From: bill at herrin.us (William Herrin)
- Date: Sat, 1 Sep 2018 16:00:36 -0400
- In-reply-to: <[email protected]>
- References: <[email protected]>
On Sat, Sep 1, 2018 at 2:51 PM, <frnkblk at iname.com> wrote:
> pointing out that a
> single traceroute to a Fastly site was hitting two of their POPs (they use
> anycast) and because they donâ??t sync state between POPs the second POP would
> naturally issue a TCP RST (sidebar: fascinating blog article on Fastlyâ??s
> infrastructure here:
> https://www.fastly.com/blog/building-and-scaling-fastly-network-part-2-balancing-requests).
Oh for Pete's sake. If they're going to attempt Anycast TCP with a
unicast protocol stack they should at least have the sense to suppress
the RSTs.
Better yet, do the job right and build an anycast TCP stack as
described here: https://bill.herrin.us/network/anycasttcp.html
Regards,
Bill Herrin
--
William Herrin ................ herrin at dirtside.com bill at herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>