[ninux-dev] Dubbio su JSON for networks: phy0 vs radio0

Nemesis nemesis at ninux.org
Thu Nov 27 14:09:28 CET 2014


Altre info:
https://github.com/interop-dev/json-for-networks/issues/3#issuecomment-64786879

radio0 comes from the UCI configuration section name while phy0 comes
from the driver in the kernel. The physical device associated with a
wireless interface in UCI may be configured using the phy attribute, for
example:

config wifi-device 'radio0'
    ...
    option phy 'phy0'
This is how you configure multiple radios on a device. You may also use
the MAC address using the macaddr attribute.

I am not sure how this is for non-mac80211 drivers.



On 11/27/2014 01:33 PM, Alessandro (aka ArkaNet) wrote:
> Onestamente non ho trovato materiale interessante tanto da fornire una
> risposta, quello che ho capito io ricade in una suddivisione, se
> vogliamo grossolanamente definirla, delle funzionalità, ovvero, con
> *dev* si definisce la locazione dell'interfaccia mentre con *phy* se
> ne possono osservare le sue caratteristiche.
>
> Definizioni esatte della distinzione tra dev e phy non ne ho trovate
> documentate, anche se dal man già si delinea quello che ho postato sopra
>
>     dev <interface name>
>     - network interface.
>     phy <phy name>
>     - wireless hardware device (by name).
>     phy#<phy index>
>     - wireless hardware device (by index).
>
>
>
> Tutta la documentazione che ho trovato è la seguente
>
> - http://wireless.kernel.org/en/users/Documentation/iw
> - http://wireless.kernel.org/en/users/Documentation/modes
> - http://linux.die.net/man/8/iw
>
>
>
> /--
> Arka/
>
> 2014-11-27 10:38 GMT+01:00 Nemesis <nemesis at ninux.org
> <mailto:nemesis at ninux.org>>:
>
>     Spiego meglio va:
>
>     https://github.com/interop-dev/json-for-networks/issues/3
>     /
>     /*Pasted text:*/
>
>     / /Is there difference between phy0 and radio0?//
>     //
>     //In the nodewatcher-agent example posted in #1 both are mentioned
>     but only radio0 has a definition.//
>     //
>     //Via openwrt ubus I see no mention of any phy object, but I see
>     mention of radio0 (via ubus call network.wireless status, just it
>     doesnt have the information contained in our physical_devices
>     section, but something slightly different.//
>     //
>     //Via the iw command I see that interfaces reference a phy object,
>     and iw phy returns all the capabilities of the physical device.//
>     //
>     //I am a bit confused. Can anyone bring some clarity?
>
>     /
>     /
>
>     /
>     On 11/26/2014 11:58 AM, nemesis wrote:
>>     Incollo chat log:
>>
>>     ho un dubbio
>>     su physical_devices
>>     che dovrebbe essere qualcosa tipo quello che c'è in "iw phy"
>>     se fai "iw dev" vedi che ogni dev punta ad un phy
>>     però su ubus se fai "ubus call network.wireless status"
>>     esce qualcosa di diverso e menziona radio0
>>     nodewatcher-agent ha una sezione "core.wireless"
>>     in cui vengono menzionati sia radio0 che phy0
>>     come se fossero due cose diverse, io pensavo fossero una cosa sola
>>     qui c'è un esempio di nodewatcher-agent
>>     https://github.com/interop-dev/json-for-networks/issues/1#issuecomment-60508259
>>
>>
>>     Nemesis
>>     _______________________________________________
>>     ninux-dev mailing list
>>     ninux-dev at ml.ninux.org <mailto:ninux-dev at ml.ninux.org>
>>     http://ml.ninux.org/mailman/listinfo/ninux-dev
>
>
>     _______________________________________________
>     ninux-dev mailing list
>     ninux-dev at ml.ninux.org <mailto:ninux-dev at ml.ninux.org>
>     http://ml.ninux.org/mailman/listinfo/ninux-dev
>
>
>
>
> _______________________________________________
> ninux-dev mailing list
> ninux-dev at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/ninux-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/ninux-dev/attachments/20141127/513ee048/attachment-0001.html>


More information about the ninux-dev mailing list