You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
phy0 is a mac80211 specific concept
radio0 is an abstract openwrt identifier for "first radio"
on mac80211 this usually maps to pyh0
on proprietary broadcom it would be wl0
on atheros it would be ath0
and so on
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 ofradio0
(viaubus call network.wireless status
, just it doesnt have the information contained in ourphysical_devices
section, but something slightly different.Via the
iw
command I see that interfaces reference aphy
object, andiw phy
returns all the capabilities of the physical device.I am a bit confused. Can anyone bring some clarity?
The text was updated successfully, but these errors were encountered: