Service provider story about tracking down TCP RSTs

• Subject: Service provider story about tracking down TCP RSTs
• From: tarko at lanparty.ee (Tarko Tikan)
• Date: Sun, 2 Sep 2018 17:43:21 +0300
• In-reply-to: <[email protected]>
• References: <[email protected]> <CA[email protected]> <CAAWx_pXC5i[email protected]> <[email protected]>

hey,

> But why did the TLS Hello has a TTL lower that the TCP Syn ?
> 
> Do you have any information on that ?

Consumer CPEs are typically some BCM reference design where initial TCP 
handshake is handled by linux kernel and everything following (including 
NAT) is handled in SOC.

I've seen those systems not decrement TTL at all, decrement TTL before 
checking if packet is destined to itself etc. This case is weird as 
typically the hardware part is faulty, not the kernel.

-- 
tarko

• Follow-Ups:
  • Service provider story about tracking down TCP RSTs
    • From: tmanito at protonmail.com (Timothy Manito)

• 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: garrett at skjelstad.org (Garrett Skjelstad)
  • Service provider story about tracking down TCP RSTs
    • From: jwbensley at gmail.com (James Bensley)
  • Service provider story about tracking down TCP RSTs
    • From: nanog at jack.fr.eu.org (nanog at jack.fr.eu.org)

• 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