> This reverse traceroute is still helpful. The paths will be roughly the same, likely differing only in terms of which specific routers see your packet.
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)
7 hours ago [-]
archmaster 9 hours ago [-]
Anecdotally, I've run a bunch of traceroutes and reverse traceroutes to different locations and they tend to follow the same AS paths — although sometimes the traceroute will surface more routing through your ISP (especially from college networks). In general you are correct, though, and I would love to explain more about hot-potato vs. cold-potato (and other interesting routing decisions) in the future. Either way, the results the reverse traceroute provides are good enough for the purposes of explaining the internet, IMO!
immibis 9 hours ago [-]
FYI what you described is hot-potato routing: each AS gets rid of it as soon as possible.
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.
advisedwang 9 hours ago [-]
ha yes thank you. I worked for a AS that mostly did cold-potato routing so grabbed the wrong term trying to describe the common case.
FredPret 10 hours ago [-]
> "You may have noticed that the traceroute progressively loads in lines above the bottom line. Web pages can only load forward. Since I didn’t want to use any JavaScript, I did the hackiest thing possible: every time I update the traceroute display, I embed a CSS block that hides the previous iteration! Since browsers render CSS as the page is loading, this made it look like the traceroute was being edited over time."
Love this
tshaddox 9 hours ago [-]
You can also do out-of-order HTML streaming without JavaScript using declarative shadow DOM. For example:
I thought this was going to play a Talking Heads song
fredland 10 hours ago [-]
letting the days go by
archmaster 9 hours ago [-]
check the html :)
mjmas 9 hours ago [-]
> Seems like this hit the Hacker News front page again, and the server's having some trouble pinging all of you. Feel free to read the article, but if you want to see your tracereoute you might need to bookmark and check back tomorrow :)
> - Lexi, Nov 7, 3:16 PM PST
archmaster 8 hours ago [-]
somewhat better now! added a bit more concurrency. lesson learned: use tokio next time
bagels 2 hours ago [-]
I tried it out, and found out that my primary internet connection had failed, and I was on the backup due to a power outage earlier today. Useful!
cat-whisperer 45 minutes ago [-]
it's not loading for me. :'(
IncreasePosts 43 minutes ago [-]
Now you must visit how-didnt-i-get-there.net
o11c 9 hours ago [-]
Hmm, after several seconds it gave up and displayed raw markup ... I'm not sure exactly why in this case, but ...
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 `-`.
It's like when your uncle squeezes you at Christmas. You're glad to see him again, but it's just a liiiitttleee... too... much... for... your... lungssss,.,.,.,
andrewshadura 10 hours ago [-]
Same as it ever was.
Razengan 11 hours ago [-]
I thought this was going to be a review of life choices
einpoklum 10 hours ago [-]
The review of life choices happens in our heads when we click this link on the main HN page.
(sigh) I'm just thinking those thoughts right now.
Rendered at 08:06:31 GMT+0000 (Coordinated Universal Time) with Vercel.
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.
Love this
https://lamplightdev.com/blog/2024/01/10/streaming-html-out-...
Behind the keyboard of a large PC
Well, how did ip route here?
> - 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 `-`.
https://news.ycombinator.com/item?id=38531604
(sigh) I'm just thinking those thoughts right now.