Re: ifconfig v2

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

On Wed, Jun 12, 2013 at 10:47:21AM -0500, David Young wrote:
> [...]
> I like the idea of combining the keywords that way, but even with
> compression, the capabilities and enables take at least 4 out of 9 lines
> in a fairly normal default display:
> 
> wm0: flags < up, running >
>         capabilities:   ip4csum, tcp4csum, tcp6csum, tso4, tso6,
>                         udp4csum, udp6csum
>         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
>         inet6 fe80::226:2dff:fef3:c8c7%wm0 prefixlen 64 scopeid 0x1
> 
> I am pretty sure that most of the time, people are not looking for the
> capabilities/enables in the ifconfig output.
> 
> I find it hard to ignore the larger issue, though, which is that those
> capability flags are only useful insofar as the NetBSD networking stack
> and drivers are distrusted or buggy and some masochists like to turn
> knobs until they find a combo that works. :-) Ordinarily a driver should
> enable the offload capabilities that are known to work reliably, and it
> should not advertise the buggy ones.

it's more complicated than that; there are cases (e.g. mixing
offload-enabled an non-enabled interfaces in a bridge) breaks things
in subtle ways, and it's not the ethernet driver's fault.
So yes, I need to see them.

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