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

[Nemesis]

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
> 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/99618c9e/attachment-0001.html>