4 ms·
And its far more consistent to deal with. v6 works like v4, arp and ndp work the same (down to subcommand to invoke them: they're under "neighbor") everything
by icehawk 4y ago
And its far more consistent to deal with.
v6 works like v4, arp and ndp work the same (down to subcommand to invoke them: they're under "neighbor") everything uses the same verbiage: add/delete/change/set.
none of this sillyness where you need one command to show the routing table 'netstat -rn' and another to manipulate the routing table 'route add/delete/change' (and then v4 uses -mask and v6 uses -prefixlen, etc etc)
- akira2501 4y agoAlso, vlans and bridges.. and vlans _on_ bridges. tap interfaces? Yup! Flattening everything and then making it available through the 'verb' syntax is an absolute joy to work with, especially if you're doing time sensitive work or trying to debug a test setup. The CLI flows like a language, and you find yourself guessing at new "phrases" that very often _don't_ summon demons and actually do what you expected. I like it so much, I emulate it whenever it makes sense to do so for my own CLI tools.
- justsomehnguy 4y agoWorking with Windows, Linux, FreeBSD, switches all the time I still occasionally try to `ipconfig` on non-Windows machines, `ip addr` on BSD and I'm still try to `route print` before remembering it's `netstat -nr`. `ip` is ugly (especially it's help system or more like lack of it) but works and pretty consistent.