Re: ifconfig v2

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Jun 11, 2013 at 09:50:24PM -0500, David Young wrote:
> [...]
> Finally, for the sake of consistency, let's put all of the addresses,
> even the link-layer address, into <family> <address> form:
> 
> wm0: flags < up, running >
>         media: Ethernet none (none)
>         link 00:26:2d:f3:c8:c7
>         inet 169.254.162.222 prefixlen 16
>         inet6 fe80::226:2dff:fef3:c8c7%wm0 prefixlen 64 scopeid 0x1
> 
> That is an efficient and consistent display.  I estimate that it will
> meet my information needs more than 95% of the time when I run 'ifconfig
> wm0', and it will meet my needs more quickly than the status quo because
> it is less cluttered and more compact.
> 
> If I need more information, I will ask for it with ifconfig -v wm0:
> 
> wm0: flags < up, broadcast, running, simplex, multicast > mtu 1500
>         capabilities: ip4csum-rx, ip4csum-tx, tcp4csum-rx, tcp4csum-tx,
>                       tcp6csum-rx tcp6csum-tx, tso4, tso6,
>                       udp4csum-rx, udp4csum-tx, udp6csum-rx, udp6csum-tx
>         enabled: <none>
>         ether capabilities: vlan-mtu, vlan-hwtagging, jumbo-mtu
>         ether enabled: <none>
>         media: Ethernet none (none)
>         link 00:26:2d:f3:c8:c7
>         inet 169.254.162.222 prefixlen 16 broadcast 169.254.255.255
>         inet6 fe80::226:2dff:fef3:c8c7%wm0 prefixlen 64 scopeid 0x1

I think capabilities (both supported and enabled) should still be in the
default output; it's an important information when you're configuring a
network interface.
Maybe some of them could be merged, e.g. when you have ip4csum-rx, ip4csum-tx
print ip4csum (ifconfig accepts this as input).

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--