nanog mailing list archives
Re: Service provider story about tracking down TCP RSTs
From: Bjørn Mork <bjorn () mork no>
Date: Sun, 02 Sep 2018 12:06:24 +0200
William Herrin <bill () herrin us> writes:
BTW, for anyone concerned about an explosion in state management overhead, the TL;DR version is: the anycast node which first accepts the TCP connection encodes its identity in the TCP sequence number where all the other nodes can statelessly find it in the subsequent packets.
I didn't see a security section in your document. Did you consider the side effects of this sequence number abuse? Bjørn
Current thread:
- Service provider story about tracking down TCP RSTs frnkblk (Sep 01)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 01)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 01)
- Re: Service provider story about tracking down TCP RSTs Lee (Sep 01)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 01)
- Re: Service provider story about tracking down TCP RSTs Lee (Sep 01)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 01)
- Re: Service provider story about tracking down TCP RSTs Bjørn Mork (Sep 02)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 02)
- Re: Service provider story about tracking down TCP RSTs Bjørn Mork (Sep 02)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 02)
- Re: Service provider story about tracking down TCP RSTs William Herrin (Sep 01)
- Re: Service provider story about tracking down TCP RSTs James Bensley (Sep 02)
- Re: Service provider story about tracking down TCP RSTs nanog (Sep 02)
- Re: Service provider story about tracking down TCP RSTs Tarko Tikan (Sep 02)
- Re: Service provider story about tracking down TCP RSTs Timothy Manito via NANOG (Sep 04)