sowmini.varadhan at sun.com wrote:
> On (06/26/07 12:52), Garrett D'Amore wrote:
>   
>>> # dladm show-linkprop wpi0
>>> LINK         PROPERTY        VALUE          DEFAULT        POSSIBLE
>>> wpi0         channel         10             --             --
>>> wpi0         powermode       ?              off            off,fast,max
>>> wpi0         radio           ?              on             on,off
>>> wpi0         speed           54             --             
>>> 1,2,5.5,6,9,11,12,18,
>>> 24,36,48,54
>>> wpi0         zone            --             --             --
>>>
>>> WiFi properties:
>>>
>>> LINK       STATUS            ESSID               SEC    STRENGTH   MODE   
>>> SPEED
>>> wpi0       connected         Radio Lsys          wep    very good  g      
>>> 54Mb
>>>
>>>       
>> This just doesn't make sense to me.
>>
>> A bunch of the properties above (powermode, radio, channel) are really 
>> wifi-only properties.
>>     
>
> I agree.  I was actually just cutting/pasting current output
> from a laptop.. the first table is what we print for show-linkprop today.
> My own intuition would have been that the first table
> (show-linkprop) should be really sparse and general, maybe not even
> have the DEFAULT/POSSIBLE fields? And the second one should have all
> the details.
>
> I suspect that the first table shows the r/w properties, hence
> the DEFAULT/POSSIBLE columns.
>
>   
>> I would really prefer to have two separate commands:
>>
>> * show-linkprop which displays all properties in all their glory (and 
>>     
>
> I personally think show-linkprop should be terse, esp. if we also
> have a separate "show-<linktype>" command.
>   

Nah,  I think you're missing my point.

Direct access to link properties is probably an "advanced" operation.  
(Maybe instead of "linkprop" call it "show properties" :-)

What should be "relatively" terse is the show-<linktype>.

In that case, the show-<linktype> includes the most commonly asked for 
information... I'd propose that this is:

For all types:

    * MTU
    * link state (up or down)

For ethernet:

    * current link speed, duplex, and whether the link is forced or not.
    * whether flow control (pause/asmpause) is supported
    * security == none (maybe in the future 802.1x or "linksec"?) .... 
maybe suppress this for unsecured links?

For wifi:

    * current link speed, mode, and essid
    * current security model (wep, wpa, open, etc.)
    * signal quality
    * current channel
    * if the radio is off, then the signal quality can report "off"
      (I'd leave "powermode" as an "advanced" property unlikely to be 
accessed by the typical end-user. )

For 3G networks (not yet supported, but I'm putting it here as an example):

    * current band, link quality and speed if the chipset supports 
reporting it (some do, some don't)
    * APN (a network name, its like an SSID)

I think what we have for vlans and aggrs (show-vlan and show-aggr) is 
pretty good already.

    -- Garrett
>   
>> * show-dev or somesuch, which displays the device details in a manner that 
>>     
>
> show-dev currently shows what devices are available.
> I think CV's "show-<linktype>" is what you may have in mind.
>
> --Sowmini
>
>   


Reply via email to