FujiApple

6 ms·

1.
by FujiApple 5mo ago
> If you ever see packet loss in a trace at one step but the steps after it aren't showing it, you can ignore that packet loss, it's likely a CPU limitation on a busy router. Trippy now includes [0] forward loss (Floss) and bac
2.
by FujiApple 1y ago
I’ve recently been building a similar tool [1] which defines a specification for CLIs, though the goals are slightly different to the tool you mention I think. I just added support for fish as it happens. [1] https://github.com&#
3.
by FujiApple 1y ago
Something I’ve been working on recently is a command line tool [1] to bring clap declarative command line parsing to shell scripts. Unfinished WIP but largely functional. [1] https://github.com/fujiapple852/claptrap
4.
by FujiApple 2y ago
Great concept. I was on mobile and agree the custom keyboard is far from ideal. As others have said I also found it to be overly US-centric. Keen to see how this develops, feels like a winning idea!
5.
by FujiApple 2y ago
You can, with several caveats, detect which hop(s) on the path perform NAT by using some trickery [1]: > NAT devices are detected by observing a difference in the expected and actual checksum of the UDP packet that is returned as the par
6.
by FujiApple 2y ago
OP, you may find this [1] “trick” useful. It allows you to dynamically determine the correct byte order for the various IPv4 headers for the platform and thus avoid the need to statically decide on the byte ordering for each platform you i
7.
by FujiApple 2y ago
It’s not guaranteed to be accurate, but tracing using the UDP/dublin strategy with a fixed dest port and varying src port per round can help to identify and visualize valid ECMP flows. I recently wrote some guidance [1] on using Tripp
8.
by FujiApple 2y ago
I recently had to look at the implementation of the Sparkline [1] widget in Ratatui which uses a similar Unicode technique but scales nicely for sparklines with larger vertical size. [1] https://github.com/ratatui/ratat
9.
by FujiApple 2y ago
Exploring adding the (novel?) concept of forward and backward packet loss heuristics to Trippy [1] as discussed here [2]. [1] https://github.com/fujiapple852/trippy/issues/860 [2] https://news.ycom
10.
by FujiApple 2y ago
I recently tried Zulip [1] again after a few years and the UX is much improved on web and mobile, worth a look (it is OSS and you can self host). [1] https://zulip.com/
11.
by FujiApple 2y ago
This Tailscale blog [1] from 2020 has been posted on HN many times before I’m sure but is worth highlighting again as it does a great job outlining the technical complexities that CGNAT (and NAT in general) introduce. I have my head in this
12.
by FujiApple 2y ago
What is the state of the art for running NetBSD (and other *BSD) in CI such as GitHub actions? Edit: to add a bit more detail, I maintain a cross platform tool [1] on GitHub and require a way to build and test it in CI for several platform
13.
by FujiApple 3y ago
Thanks! I’ll take a look
14.
by FujiApple 3y ago
For the RTT and loss% measurements Trippy just does the obvious thing (i.e. RTT = recv time - send time and loss% = lost / total_sent). There is a plan [0] to add custom columns to Trippy and then to add various jitter measurements [1]
15.
by FujiApple 3y ago
Thanks for that, I'll give this some thought and write a proposal in this [0] placeholder issue. [0] https://github.com/fujiapple852/trippy/issues/860
16.
by FujiApple 3y ago
I agree regarding documentation. There was a request [0] for something similar, though not specifically covering this important point. Regarding sending a ping flood, Trippy allow you to reduce the minimum and maximum round time (and grace
17.
by FujiApple 3y ago
Something I intend to add to Trippy, but have not got around to it yet; is to codify the "If a packet takes the path A -> B -> C and pings to B have 50% loss but pings to C have 0% loss, then the path is perfectly fine" idea
18.
by FujiApple 3y ago
Thank you, I'll look into those RFCs.
19.
by FujiApple 3y ago
That looks great, seems like they've raised the bar for GeoIp accuracy, kudos to them. It looks like they provide mmdb files (for a fee) which should be compatible with Trippy. I'd love to be able to test it out, the sample [0] t
20.
by FujiApple 3y ago
Thank you for adding Trippy to your list. > how did you accomplish all the package managers? In most cases I didn't do anything! I've discovered that there are many kind souls out there who are willing to give up their free tim
21.
by FujiApple 3y ago
You are right that showing packet loss for intermediate hops is a frequent source of confusion. Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 10
22.
by FujiApple 3y ago
The TUI is built with the awesome Ratatui [0] library (formerly tui-rs [1]). UX is certainly not my area of expertise and I would not have been able to create Trippy without this library. [0] https://github.com/ratatui-or
23.
by FujiApple 3y ago
Yes, in my experience GeoIp is _highly_ unreliable, alas Trippy can do no more than report the location from the provided mmdb file. I'm aware of some interesting techniques which use timing measurements from multiple locations to try
24.
by FujiApple 3y ago
Author here, thanks for posting this (i’d meant to do a show HN post at some point). Trippy is a modern, cross platform, feature rich alternative to MTR with a fancy TUI. And yes, it’s written in Rust. https://github.com/fuj
25.
by FujiApple 3y ago
"Never attribute to malice that which can be adequately explained by stupidity"
26.
by FujiApple 3y ago
Very little coverage of this bill passing in the UK mainstream media that I have seen.
27.
by FujiApple 3y ago
This is very similar to the layering approach I ended up with for a service I built a couple of years ago (AWS using Pulumi). Global - Things from the AWS global region, notably DNS (DelegationSet and Zone) and IAM Core - Semi-permanent per
28.
by FujiApple 3y ago
Great resource, thanks for sharing.
29.
by FujiApple 4y ago
This is great, good luck with the inevitable NYT buyout :) One nit, the letters could snap the grid a bit more aggressive, I found I frequently had letter “miss” the grid and have to drag them again (on an iPad).
30.
by FujiApple 4y ago
You know you’re in a long term relationship when your better half starts throwing away your stuff without asking.

More ›