Search Linux Wireless

Re: why can the distance only be set on a phy not a dev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2012-01-17 at 12:29 +0000, David Goodenough wrote:
> Using the iw command, most things can either be directed to a dev or
> a phy, but a distance can only be set on a phy.
> 
> This leads to problems as I do not know which phy is connected to a 
> dev (or at least I do not know how to find out which phy is connected
> to a dev), and so in my Debian /etc/network/interfaces file I have:-
> 
> iface wlan0 inet manual
> 	pre-up iw dev wlan0 interface add mesh0 type mp
> 
> iface mesh0 inet static
>     address 10.101.11.254
>     netmask 255.255.255.0
>     pre-up iw dev mesh0 set channel 153
>     post-up iw phy phy0 set distance 3500
>     up iw dev mesh0 mesh join MeshId
> 
> so in the mesh0 stanza I have a reference to phy0 which is hard
> coded and if it changes subject to error.
> 
> So either I need to be able to set distance to dev mesh0, or have
> some means or working out which phy corresponds to dev mesh0.

I can easily allow you to invoke iw with the netdev rather than the phy,
but the parameter would still be per phy.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux