News for hackers. Stuff that matters.
Re:AT&T Fiber in the SF Bay Area is flipping bits by cranekam on Tuesday December 08, 2020 @01:26AM (#25342487)
TCP checksums are notoriously weak:

https://www.evanjones.ca/tcp-checksums.html

With enough packets passing the dodgy RAM a noticeable number will manage to get mangled in such a way that the checksum is still correct.

Re:AT&T Fiber in the SF Bay Area is flipping bits by ericbarrett on Tuesday December 08, 2020 @02:00AM (#25342671)
Checksums are also often recomputed on transit if the packet is intercepted, e.g. to limit TTL, unflag odd/unused TCP features, that kind of ISP-ish preening. So if it was a software error or even a hardware problem in the right (wrong) spot it’s possible to get this kind of corruption without retransmits.
Re:AT&T Fiber in the SF Bay Area is flipping bits by noncoml on Tuesday December 08, 2020 @01:54PM (#25349757)
I think you are confusing the IP header with TCP header.

Routers don’t touch the TCP header at all

Re:AT&T Fiber in the SF Bay Area is flipping bits by ericbarrett on Tuesday December 08, 2020 @11:56PM (#25355521)
No. URG, “Christmas tree” packets, etc. all can be mangled by the ISP. Or more commonly dropped
Re:AT&T Fiber in the SF Bay Area is flipping bits by Avery3R on Tuesday December 08, 2020 @09:39PM (#25354674)
if your router does NAT it touches the tcp header
Re:AT&T Fiber in the SF Bay Area is flipping bits by noncoml on Tuesday December 08, 2020 @10:12PM (#25354902)
You are right, although NAT could be classified as a firewall feature, that runs on routers.

But in any case it's irrelevant in this context as ATT shouldn't be doing any NAT

Re:AT&T Fiber in the SF Bay Area is flipping bits by bytesandbots on Tuesday December 08, 2020 @03:51PM (#25351185)
In that case, won't there be significant packet loss causing throughput to be very slow? I don't know if this is possible without something messing with TCP headers.