maxmouchet
I've also played a bit with an interactive visualization of the graph by using map tiles [4].
[1] https://github.com/TheOpteProject/LGL
[2] https://github.com/maxmouchet/minilgl (cleaned-up version of the code)
IP-to-ASN mappings are typically built from route collectors [2,3] that peer with various networks and receive their announcements. AFAIK route collectors don't filter anything and it's easy to find bogus announcements (e.g. private ASNs) in the data.
I can't find 4294967296 from a quick glance at the latest RouteViews data but I can find other private ASNs. For example AS7594 - AS2764 - AS4294901866 for 210.10.189.0/24 seen by the route-views.perth collector.
I don't know what kind of filtering iptoasn.com is doing but at work (ipinfo.io) we do filter bogus origins, as well as a bunch of other things like RPKI/IRR-invalid routes and hyper-specific prefixes (> /24 or /48) [4].
[1] https://bgpfilterguide.nlnog.net
[2] https://www.routeviews.org/routeviews/
[3] https://www.ripe.net/analyse/internet-measurements/routing-i...
There are several free ASN MMDBs [2,3] but you can also build your own MMDB files from any Prefix->Value mapping with the mmdbwriter library [4] or a CLI tool built on top of it like mmdbctl [5].
Assuming the ASN MMDB is fully loaded in memory, it would use around 60MB.
[1] https://maxmind.github.io/MaxMind-DB/
[2] https://dev.maxmind.com/geoip/docs/databases/asn/
[3] https://ipinfo.io/products/free-ip-data-downloads
[4] https://github.com/maxmind/mmdbwriter
[5] https://github.com/ipinfo/mmdbctl
(I work for IPinfo, but there are lots of other companies offering MMDB files).
Now there are some issues with this methodology (all common issues with ICMP/RTT measurements + traffic was not really routed through the "relay" probe), but such pairs do exist.
[1] https://theses.hal.science/tel-03666771/document (see page 84 for an example; if you can read French :-))
These changes are more typical of a physical path change, as suggested by the author.
CPU/soft processing latency would look more like additive noise.
I give some examples of RTT patterns in this talk: https://ripe77.ripe.net/archives/video/2250/
And that’s a detail, but SLAAC as in RFC4842 is deterministic. The randomization is introduced by the privacy extensions in RFC4941.
Why so? What’s the link between the twos?
(Genuinely asking)
dig +short TXT mumbai.weather @dns.google
# NXDOMAIN
dig +short TXT mumbai.weather @dns.toys
"Mumbai (IN)" "30.90C (87.62F)" "45.90% hu." "clearsky_day" "15:30, Sun"
"Mumbai (IN)" "28.10C (82.58F)" "56.00% hu." "fair_day" "17:30, Sun"
...Another solution is to bring your own cup.
https://gallica.bnf.fr/accueil/en/content/accueil-en
https://gallica-bnf-fr.translate.goog/blog/11122015/des-tira...
In my experience (co)lima was already an improvement over Docker Desktop in terms of reliability and background resource usage, but OrbStack is even more lightweight. I also do a bit of low-level networking development and Docker Desktop was rewriting some fields of the IP packets (besides NAT translation) which was annoying. It works seamlessly here.
It still has the same VM memory usage issue as other tools (Linux page cache taking more and more memory over time and not releasing it to the host), but they claim it will work correctly once a bug in Virtualization.framework is fixed: https://twitter.com/OrbStack/status/1645782250116505600
[1] https://eclecticlight.co/2022/03/23/how-visual-look-up-works...
An alternative is to issue wildcard certificates with LE, so that the subdomains names are kept private.
[1] https://crt.sh/
[1] https://github.com/WireGuard/wgctrl-go [2] https://github.com/pritunl/pritunl/blob/f82528ff2b7250965faf...