3 ms·
That was exactly my thought, specially after reading another answer: > "ip addr show" lists interfaces and their stats. It's harder to read than ifconfig -a bu
by f1shy 4y ago
That was exactly my thought, specially after reading another answer:
> "ip addr show" lists interfaces and their stats. It's harder to read than ifconfig -a but gives you the same information in a similar format.
> "ip route show" replaces netstat -rn to show the routing table but is also not as well formatted as the old command.
> So basically it combines a bunch of commands (including ifconfig) into one and gives them all a unified interface.
To me sounds like same but worse, and combining 10 commands into 1 seems to be totally against the unix philosophy "it should do one thing, and do it properly"
- agapon 4y agoNote that "netlink support" != "ip command". In fact, ip command hasn't been added and I haven't heard of any plans to do so.
- zokier 4y ago> To me sounds like same but worse, and combining 10 commands into 1 seems to be totally against the unix philosophy "it should do one thing, and do it properly" The "one thing" ip essentially does is working with NETLINK_ROUTE protocol; it is relatively thin wrapper exposing that to shell.
- icehawk 4y agoAnd 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.
- Hikikomori 4y agoFollowing the unix philosophy we should have one command to manage physical interfaces, another for ethernet level stuff, separate commands to manage ipv4 and ipv6 addresses, then v4 and v6 multicast, another for vlans, different ones for v4 and v6 route tables, and so on, all with an inconsistent cli interface and output. As a network engineer pre-ip linux was a disaster, while ip is a joy to work with.
- nmz 4y agoUnix programs should stop worrying about how something looks, just spit out csv and let anyone pipe into a pretty printer. If its properly formatted you can make it look however you want.
- jeltz 4y agoHaving used both I would say ip is the same thing but better. The old tools are inconsistent and often do not show all info you need.