(sigh) I'm just thinking those thoughts right now.
tracepath -m60 bad.horse
openssl s_client -connect signed.bad.horse:443 -servername signed.bad.horse ssh funky.nondeterministic.computer > tracepath -m60 bad.horse
[...]
16: bad.horse 81.233ms asymm 10
19: he.rides.across.the.nation 85.365ms asymm 11
20: he.got.the.application 96.067ms asymm 13
23: it.needs.evaluation 112.377ms asymm 15
24: a.heinous.crime 114.826ms asymm 17
25: a.show.of.force 120.842ms asymm 18
26: bad.horse 133.089ms asymm 20Behind the keyboard of a large PC
Love this
https://lamplightdev.com/blog/2024/01/10/streaming-html-out-...
This is categorically incorrect. While the AS path is often the same, the actual peering points are almost always quite different. Most ASes use hot-potato routing - getting packets to the next AS at the closest peering point to the source of the traffic. (And even if cold-potato routing is used, that's still asymmetric). In addition if there are two options with the same AS-path-length hot-potato routing can lead to different AS paths. This can happen if there's two mutual transit providers between source and destination and various other situations.
(EDIT: fixed hot/cold mixup)
You may think this is unfair, and yes, it is, but it's also quite logical when you consider you don't know where the packet is going in the destination AS. If you have a network spanning Berlin and Hamburg and the packet is going to a different network that also spans Berlin and Hamburg, and you interconnect at both points, and you don't know which city it's actually going to, handing it off at the closest interconnect doesn't risk round-tripping it for no good reason.
They had a DS3 to AT&T for Internet and a T1 to Sprint for 'back-up' in case the primary went down. Same AS, but 75% of the Internet traffic perferred the Sprint return route.
Our 'network guy' couldn't figure out why everyone in this company (100k employees) was experiencing worse than dial-up performance at their desks. Took about 10 minutes to see what the issue was (using reverse traceroute from a looking glass server out there somewhere).
As soon as we fixed that, ran into the next problem. Dude built a caching proxy server on a Sun e4500 with ONE disk.
Got to be a hero for a little bit lol.
> - Lexi, Nov 7, 3:16 PM PST
One of the major infelicities of the web is that CSS is specified to ignore truncation, and there is no way to fix this. Now think about what happens if something like `display: inline-block` gets truncated before the `-`.
ChrisArchitect•5h ago
https://news.ycombinator.com/item?id=38531604