Michael Ziegler
Michael Ziegler
I'm wondering if we should add a PMTUD feature. That is, regularly figure out what the path MTU to a certain target is, and show that in the target list.
I'm wondering if we should add route tracing to meshping, so that you can click on a target and see the route that packets take in a similar fashion to...
I'd like to integrate meshping with an IPAM tool such as netbox or phpipam, to automatically fetch targets from those. Also, UniFi comes to mind, which makes clients and devices...
We're still using VueJS 2, which is deprecated. I don't want to use VueJS 3 though, because I feel it's way too large and complicated for what we need here....
It would be cool if we tracked changes in traceroutes and users could see when changes happened and what the routes were.
Display whois information for targets and route hops. Exceptions: * RFC1918, RFC6598 (`100.64.0.0/10`) * Ipv6 addresses not in GUA scope (`2000::/3`)
Currently, DNS names are only resolved when adding a target, and from then on, IPs are assumed to be static. Let's add some kind of support for dyndns targets.
Now that we know all the hops, we could draw a graph of some sort to display a network map. Maybe generate some PlantUML and let it handle the dirty...