"Also note that I often alias ip to ip -br -c as it provides a much prettier output. Compare, before: anarcat@angela:~> ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default"
"After: anarcat@angela:~> ip -br -c a lo UNKNOWN 127.0.0.1/8 ::1/128 wlan0 DOWN virbr0 DOWN 192.168.122.1/24 eth0 UP 192.168.0.108/24 I don't even need to redact MAC addresses! It also affects the display of the other commands, which look similarly neat. Also imagine pretty colors above. Finally, I don't have a cheat sheet for iw vs iwconfig (from wireless-tools) yet. I just use NetworkManager now and rarely have to mess with wireless interfaces directly."
ifconfig from net-tools has been superseded by the ip command from iproute2 for managing network interfaces. The ip command provides more modern output and features and supports concise display options. Aliasing ip to "ip -br -c" produces a compact, colored interface listing that shows addresses and states succinctly. The compact output often renders MAC-address redaction unnecessary and makes command output easier to scan. Example outputs contrast verbose multiline results with brief summarized lines. Wireless tooling differs between iw and iwconfig, but NetworkManager handles most wireless configuration so manual wireless commands are less common.
Read at Anarc
Unable to calculate read time
Collection
[
|
...
]