<p dir="ltr">In realtà non solo in owrt... comunque il senso c'è ;)</p>
<p dir="ltr">Grazie Saverio!</p>
<p dir="ltr">--<br>
Arka</p>
<div class="gmail_quote">Il 28/nov/2014 08:27 "Saverio Proto" <<a href="mailto:zioproto@gmail.com">zioproto@gmail.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Radio0 è una keyword di openwrt piu astratta di phy0</p>
<p dir="ltr">Phy0 è una keyword del kernel, nello specifico del driver wifi</p>
<p dir="ltr">Ci sta questo livello di astrazione perchè se domani avremo interfacce radio non wifi potremmo sempre chiamarle radio0 in owrt</p>
<p dir="ltr">Saverio</p>
<div class="gmail_quote">Il 27/nov/2014 14:09 "Nemesis" <<a href="mailto:nemesis@ninux.org" target="_blank">nemesis@ninux.org</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Altre info:<br>
<a href="https://github.com/interop-dev/json-for-networks/issues/3#issuecomment-64786879" target="_blank">https://github.com/interop-dev/json-for-networks/issues/3#issuecomment-64786879</a><br>
<br>
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:<br>
<br>
config wifi-device 'radio0'<br>
...<br>
option phy 'phy0'<br>
This is how you configure multiple radios on a device. You may
also use the MAC address using the macaddr attribute.<br>
<br>
I am not sure how this is for non-mac80211 drivers.<br>
<br>
<br>
<br>
On 11/27/2014 01:33 PM, Alessandro (aka ArkaNet) wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">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 <b>dev</b> si definisce la locazione
dell'interfaccia mentre con <b>phy</b> se ne possono osservare
le sue caratteristiche.
<div><br>
</div>
<div>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</div>
<div><br>
</div>
<div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>
<div>dev <interface name></div>
<div>- network interface.</div>
<div>phy <phy name></div>
<div>- wireless hardware device (by name).</div>
<div>phy#<phy index></div>
<div>- wireless hardware device (by index).</div>
</div>
</blockquote>
<br>
</div>
<div><br>
</div>
<div>Tutta la documentazione che ho trovato è la seguente</div>
<div><br>
</div>
<div>- <a href="http://wireless.kernel.org/en/users/Documentation/iw" target="_blank">http://wireless.kernel.org/en/users/Documentation/iw</a><br>
</div>
<div>- <a href="http://wireless.kernel.org/en/users/Documentation/modes" target="_blank">http://wireless.kernel.org/en/users/Documentation/modes</a></div>
<div>- <a href="http://linux.die.net/man/8/iw" target="_blank">http://linux.die.net/man/8/iw</a></div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>
<div dir="ltr">
<pre cols="72"><span style="background-color:rgb(255,255,255);white-space:normal"><font face="'comic sans ms', sans-serif"><pre cols="72"><i>--
Arka</i></pre></font></span></pre>
</div>
</div>
</div>
<br>
<div class="gmail_quote">2014-11-27 10:38 GMT+01:00 Nemesis <span dir="ltr"><<a href="mailto:nemesis@ninux.org" target="_blank">nemesis@ninux.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Spiego meglio va:<br>
<br>
<font face="Helvetica, Arial, sans-serif"><a href="https://github.com/interop-dev/json-for-networks/issues/3" target="_blank">https://github.com/interop-dev/json-for-networks/issues/3</a><br>
<i><br>
</i><b><font face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">Pasted text:</font></font></b><i><br>
<br>
</i></font> <i>Is there difference between phy0 and
radio0?</i><i><br>
</i><i><br>
</i><i>In the nodewatcher-agent example posted in #1
both are mentioned but only radio0 has a definition.</i><i><br>
</i><i><br>
</i><i>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.</i><i><br>
</i><i><br>
</i><i>Via the iw command I see that interfaces
reference a phy object, and iw phy returns all the
capabilities of the physical device.</i><i><br>
</i><i><br>
</i><i>I am a bit confused. Can anyone bring some
clarity?<br>
<br>
</i>
<div>
<div><i><br>
<br>
</i><br>
On 11/26/2014 11:58 AM, nemesis wrote:<br>
</div>
</div>
</div>
<div>
<div>
<blockquote type="cite">Incollo chat log: <br>
<br>
ho un dubbio <br>
su physical_devices <br>
che dovrebbe essere qualcosa tipo quello che c’è in
“iw phy” <br>
se fai “iw dev” vedi che ogni dev punta ad un phy <br>
però su ubus se fai “ubus call network.wireless
status” <br>
esce qualcosa di diverso e menziona radio0 <br>
nodewatcher-agent ha una sezione “core.wireless” <br>
in cui vengono menzionati sia radio0 che phy0 <br>
come se fossero due cose diverse, io pensavo fossero
una cosa sola <br>
qui c’è un esempio di nodewatcher-agent <br>
<a href="https://github.com/interop-dev/json-for-networks/issues/1#issuecomment-60508259" target="_blank">https://github.com/interop-dev/json-for-networks/issues/1#issuecomment-60508259</a>
<br>
<br>
Nemesis <br>
_______________________________________________ <br>
ninux-dev mailing list <br>
<a href="mailto:ninux-dev@ml.ninux.org" target="_blank">ninux-dev@ml.ninux.org</a> <br>
<a href="http://ml.ninux.org/mailman/listinfo/ninux-dev" target="_blank">http://ml.ninux.org/mailman/listinfo/ninux-dev</a>
<br>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
ninux-dev mailing list<br>
<a href="mailto:ninux-dev@ml.ninux.org" target="_blank">ninux-dev@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/ninux-dev" target="_blank">http://ml.ninux.org/mailman/listinfo/ninux-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
ninux-dev mailing list
<a href="mailto:ninux-dev@ml.ninux.org" target="_blank">ninux-dev@ml.ninux.org</a>
<a href="http://ml.ninux.org/mailman/listinfo/ninux-dev" target="_blank">http://ml.ninux.org/mailman/listinfo/ninux-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
ninux-dev mailing list<br>
<a href="mailto:ninux-dev@ml.ninux.org" target="_blank">ninux-dev@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/ninux-dev" target="_blank">http://ml.ninux.org/mailman/listinfo/ninux-dev</a><br>
<br></blockquote></div>
<br>_______________________________________________<br>
ninux-dev mailing list<br>
<a href="mailto:ninux-dev@ml.ninux.org">ninux-dev@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/ninux-dev" target="_blank">http://ml.ninux.org/mailman/listinfo/ninux-dev</a><br>
<br></blockquote></div>