[Note truncated recipient list] On (06/26/07 15:51), Garrett D'Amore wrote: > >> I'm curious why you think having three properties (ala cap, >> advcap and lpadvcap) wouldn't be a reasonable tradeoff?
> > Because: I think the point that meem is trying to make is that maybe we should not feel obliged to stick to the lettering in the ieee802.3(5) man page, but leave that as "legacy ndd support", while we seek a more concise, but still useful presentation format, with a new man page if needed. > a) that doesn't tell the whole story. (is autonegotiation enabled? that's > another boolean! and having it disabled is a distinct case from having it > enabled with only one mode advertised.) > > b) i guess having adv_cap be tunable via a comma delimited list would work, > but it is likely to be more confusing than just "please force this mode" > (which is what admins who diddle here really want) > > c) just setting a single forced mode is all (arbitrary unsubstantiated > statistic alert!) 99% of the customers who do diddle here need... > > Given that this is the state of affairs, lets make case "C" above as easy > as possible. Raymond and I will go back and think about how to compress the information in ieee802.3 (if it can be done).. stay tuned. Meanwhile, it sounds like the "general" property list is not that long: it currently has mtu, zone, autopush. Is there anything else that we foresee adding in the future? Something related to security? Wake-on-lan related tunables? --Sowmini
