putting-the-you-in-cpu VS mtr

Thanks to cpu.land , I grew an uncanny interest in how cpu works and got me deep into operating systems from there, it’s fascinating to see the deep down of your computer to the levels of registers and ALUs(arithmetic logical units). Nand2tetris and OSTEP is the greatest resource for starting with operating systems.

OrbStack | Founding Engineer | US/Europe REMOTE | Full-time | https://orbstack.dev

OrbStack is making Docker containers & development environments delightful. Our app replaces Docker Desktop and makes containers faster, lighter, and easier to work with. It's the tool of choice for PlanetScale, Replicate, and other hot companies.

Containers should be a joy to use, not something you have to put up with. Let's build the future of dev envs.

As a founding engineer, you'll mainly work on breaking high-level ideas down into tough systems problems, solving them, and taking ownership of projects. If https://cpu.land and https://docs.orbstack.dev/architecture excite you, you'll be right in place.

Email: jobs orbstack dev

Hi! I'm Lexi. I'm 17, and one of the things I'm interested in is gaining a deeper understanding of how computers work and showing that in new ways. A few months ago I published https://cpu.land (discussion: https://news.ycombinator.com/item?id=37062422).

After cpu.land, I felt a lot of pressure to make another Big Giant Thing but didn't really have anything compelling. So I just hacked away on personal projects and, through some coincidental learning on how the Internet works, ended up hacking together a traceroute program that could live stream to a website from scratch!

I realized I had never seen this sort of thing on the web before, and it was actually a kind of cool and novel way of visualizing the structure of the Internet, so I polished it up and built a pretty site around it. In the process, I learned some really interesting things about how BGP and the structure of The Internet, so I melted the traceroute tool with an article sharing that knowledge.

I'm still hacking on this and I'm sure my code will manage to break somehow, so please let me know if you have any suggestions! :)

(Side note: why Rust? I don’t think programming language choice matters that much, but I wanted to quickly write a very dependable low-level program, and I really like Rust’s error handling primitives.

https://cpu.land/

As a reminder, Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues. You can think of it as a modern, cross platform, Rust based version of tools such as mtr, with a bunch of advanced features and a fancy TUI.

Cool project! Two suggestions, one serious, one frivolous:

- I wonder if you could get more accurate results by using TCP or UDP instead of ICMP. I think traditional traceroute has an option to use UDP, mtr [1] can use TCP or UDP, and tcptraceroute [2] can use TCP.

- This would be a perfect fit for some Talking Heads references. "And you may ask yourself, well, how did I get here?" [3]

[1] https://github.com/traviscross/mtr

[2] https://linux.die.net/man/1/tcptraceroute

[3] https://en.wikipedia.org/wiki/Once_in_a_Lifetime_(Talking_He...

Run mtr, or whatever the Windows equivalent might be, and leave it running shortly before 4:15pm, and see where the traffic stops when the Internet shuts off.

Lot of great stuff here, haven’t seen MTR yet: https://github.com/traviscross/mtr

Consider using MTR (software) towards the actual end-point of the SIP connection to get a combination of traceroute and ping which will be much more revealing. This will also allow you to quickly identify if the problem is local to your equipment or somewhere along the path. Consider allowing her to join a Google Conference from Teams to determine if it is provider related. Yes, port mirroring and wire shark is the gold standard and will display the "answer" on your screen quickly but it requires skills to know what to analyze, look at and how to interpret the data.

Have you tried something like mtr to check for connection issues? I would recommand the view you get when hitting d twice after starting it (with the colored graph for latencies).

Continuing to build trippy; a network diagnostic tool inspired by mtr. There is still a long way to go but it is getting closer to feature parity with mtr.