The ip command has a built-in help system you can get started with "ip help", but it tends to throw a lot of fugly BNF at you and is pretty light on detail.
The ip manpage is much better. It is broken up into sections which is a bummer for searching but does make it a little less daunting for reading.
The nice thing about it is that since it has been around for many years now you can google search most any question and find the answer. All in all the ip command is fairly straightforward and orthogonal which is nice.
Some starting commands
"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.
"ip neigh show" replaces arp -a and is about the same level of legibility.
"ip route add ..." replaces "route ..." command and is about the same to use.
So basically it combines a bunch of commands (including ifconfig) into one and gives them all a unified interface.
The ip manpage is much better. It is broken up into sections which is a bummer for searching but does make it a little less daunting for reading.
The nice thing about it is that since it has been around for many years now you can google search most any question and find the answer. All in all the ip command is fairly straightforward and orthogonal which is nice.
Some starting commands
"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.
"ip neigh show" replaces arp -a and is about the same level of legibility.
"ip route add ..." replaces "route ..." command and is about the same to use.
So basically it combines a bunch of commands (including ifconfig) into one and gives them all a unified interface.