5 ms·
Every packet you send has headers, cookies, etc. injected long before it reaches the public internet? really? Not for TLS (https). Not for vpn connections. Rea
by ploxiln 11y ago
Every packet you send has headers, cookies, etc. injected long before it reaches the public internet? really?
Not for TLS (https). Not for vpn connections. Really, pretty much never. It was big news when it came out that Verizon was doing this to mobile data connections.
All that happens to the IP header and everything inside is perhaps the ECN bit being fiddled, TOS bits being zeroed, that's it usually. And, as mentioned before, NAT.
For home cable or fiber internet connections, the NAT usually happens on your device, on your local network (and under your control if you reject the ISP-provided cable modem and use your own, or put the FIOS router in bridge mode).
- exelius 11y ago> It was big news when it came out that Verizon was doing this to mobile data connections. Because the other ISPs were sneakier and were only injecting their tokens when the user was visiting a site that was paying for the service. Other ISPs had been running similar schemes for years, but it flew under the radar because it was only active when the user visited certain sites. Verizon fucked up and released a half-baked solution and people caught on. Other companies were better at it. > For home cable or fiber internet connections, the NAT usually happens on your device, on your local network (and under your control if you reject the ISP-provided cable modem and use your own, or put the FIOS router in bridge mode). Most ISPs are running a carrier-grade NAT solution of some sort. A lot more happens in the access layer than most people realize.
- ploxiln 11y agoMaybe wireless ISPs, maybe wired ISPs in Asia, but not wired ISPs in the US or Europe.