From: invalid@invalid.invalid   
      
   c186282  writes:   
   > On 1/14/26 16:54, Lawrence D’Oliveiro wrote:   
   >> ifconfig/iwconfig vs ip/iw -- the latter newer ones (part of the   
   >> Linux   
   >> “iproute2” suite) offer greater access to all the features of the   
   >> Linux network stack than the former, older ones, and so are preferable   
   >> in lots of ways. It is already possible to find setups which don’t   
   >> have the old commands installed by default; I’m not sure if any   
   >> distros have actually dropped the option for installing them   
   >> altogether, but no doubt that will happen at some point.   
   >   
   >   Sometimes more can be less. I rarely used ifconfig to   
   >   actually configure things - but use it often just to   
   >   see what's what. The Just The Important Stuff output   
   >   is better than 'ip's.   
      
   ifconfig omits quite basic information. For example it misses out most   
   of the IPv4 addresses.   
      
       $ ifconfig br0   
       br0: flags=4163  mtu 1500   
               inet 172.17.207.1  netmask 255.255.255.0  broadcast 172.17.207.255   
               inet6 2001:470:9544:1000::1  prefixlen 64  scopeid 0x0   
               inet6 fe80::a8af:4cff:fe30:beca  prefixlen 64  scopeid 0x20   
               inet6 2001:470:1f09:11ed::1  prefixlen 64  scopeid 0x0   
               ether aa:af:4c:30:be:ca  txqueuelen 1000  (Ethernet)   
               RX packets 428586239  bytes 209612436058 (195.2 GiB)   
               RX errors 0  dropped 0  overruns 0  frame 0   
               TX packets 441241166  bytes 730413120539 (680.2 GiB)   
               TX errors 0  dropped 31 overruns 0  carrier 0  collisions 0   
      
       $ ip addr show br0   
       4: br0:  mtu 1500 qdisc noqueue state UP   
   group default qlen 1000   
           link/ether aa:af:4c:30:be:ca brd ff:ff:ff:ff:ff:ff   
           inet 172.17.207.1/24 brd 172.17.207.255 scope global br0   
              valid_lft forever preferred_lft forever   
           inet 172.17.207.4/24 scope global secondary br0   
              valid_lft forever preferred_lft forever   
           inet 172.17.207.9/24 scope global secondary br0   
              valid_lft forever preferred_lft forever   
           inet 172.17.207.10/24 scope global secondary br0   
              valid_lft forever preferred_lft forever   
           inet 172.17.207.11/24 scope global secondary br0   
              valid_lft forever preferred_lft forever   
           inet 172.17.207.25/24 scope global secondary br0   
              valid_lft forever preferred_lft forever   
           inet6 2001:470:9544:1000::1/64 scope global   
              valid_lft forever preferred_lft forever   
           inet6 2001:470:1f09:11ed::1/64 scope global   
              valid_lft forever preferred_lft forever   
           inet6 fe80::a8af:4cff:fe30:beca/64 scope link proto kernel_ll   
              valid_lft forever preferred_lft forever   
      
   It also doesn’t seem to know about bridge membership:   
      
       $ ip addr show eno1.1   
       5: eno1.1@eno1:  mtu 1500 qdisc noqueue   
   master br0 state UP group default qlen 1000   
           link/ether 88:ae:dd:05:79:22 brd ff:ff:ff:ff:ff:ff   
       $ ifconfig eno1.1   
       eno1.1: flags=4163  mtu 1500   
               ether 88:ae:dd:05:79:22  txqueuelen 1000  (Ethernet)   
               RX packets 423961737  bytes 202388310544 (188.4 GiB)   
               RX errors 0  dropped 0  overruns 0  frame 0   
               TX packets 638112950  bytes 734464314910 (684.0 GiB)   
               TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0   
      
   --   
   https://www.greenend.org.uk/rjk/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)