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: Sun, 2 Sep 2018 06:40:10 -0400
• In-reply-to: <[email protected]>
• References: <[email protected]> <CAP-guGX=Sg[email protected]> <CA[email protected]> <[email protected]>

On Sun, Sep 2, 2018 at 6:06 AM, Bjørn Mork <bjorn at mork.no> wrote:
> William Herrin <bill at herrin.us> writes:
>>  https://bill.herrin.us/network/anycasttcp.html
>
> I didn't see a security section in your document.  Did you consider the
> side effects of this sequence number abuse?

Hi Bjørn,

In the "issues and criticisms" section.

Regards,
Bill Herrin


-- 
William Herrin ................ herrin at dirtside.com  bill at herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>

• Follow-Ups:
  • Service provider story about tracking down TCP RSTs
    • From: bjorn at mork.no (Bjørn Mork)

• References:
  • Service provider story about tracking down TCP RSTs
    • From: frnkblk at iname.com (frnkblk at iname.com)
  • Service provider story about tracking down TCP RSTs
    • From: bill at herrin.us (William Herrin)
  • Service provider story about tracking down TCP RSTs
    • From: bill at herrin.us (William Herrin)
  • Service provider story about tracking down TCP RSTs
    • From: bjorn at mork.no (Bjørn Mork)

• Prev by Date: Service provider story about tracking down TCP RSTs
• Next by Date: Service provider story about tracking down TCP RSTs
• Previous by thread: Service provider story about tracking down TCP RSTs
• Next by thread: Service provider story about tracking down TCP RSTs
• Index(es):
  • Date
  • Thread