linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Goodenough <david.goodenough@btconnect.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: why can the distance only be set on a phy not a dev
Date: Tue, 17 Jan 2012 14:05:50 +0100	[thread overview]
Message-ID: <1326805550.3342.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201201171229.33901.david.goodenough@btconnect.com> (sfid-20120117_135652_146253_52D9EF91)

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


      reply	other threads:[~2012-01-17 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 12:29 why can the distance only be set on a phy not a dev David Goodenough
2012-01-17 13:05 ` Johannes Berg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1326805550.3342.17.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=david.goodenough@btconnect.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).