Linux wireless drivers development
 help / color / mirror / Atom feed
From: Simon Raffeiner <sturmflut@lieberbiber.de>
To: linux-wireless@vger.kernel.org
Subject: Unable to create an 802.11s mesh using compat-wireless-2009-09-27
Date: Sun, 27 Sep 2009 15:41:58 +0200	[thread overview]
Message-ID: <200909271541.58448.sturmflut@lieberbiber.de> (raw)

Hello List,

I built todays compat-wireless (compat-wireless-2009-09-27) on two different 
Ubuntu machines:

- kernel 2.6.28-15-generic i686 using rt73usb
- kernel 2.6.31-11-generic x86_64 using ath5k (AR2425)

and tried to create an 802.11s Mesh following the HOWTO - unsuccessfully:

root@ion:/home/sturmflut# export MESH_IFACE=mesh
root@ion:/home/sturmflut# export MESH_ID=test
root@ion:/home/sturmflut# iw dev wlan0 interface add $MESH_IFACE type mp 
mesh_id $MESH_ID

root@ion:/home/sturmflut# ifconfig -a | grep mesh
mesh      Link encap:Ethernet  HWaddr 00:22:75:50:13:c2

root@ion:/home/sturmflut# ifconfig $MESH_IFACE up
SIOCSIFFLAGS: Name not unique on network

if I remove wlan0 the mesh device can be brought up through ifconfig:

root@ion:/home/sturmflut# iw dev wlan0 del
root@ion:/home/sturmflut# ifconfig $MESH_IFACE up

The strange thing is that iwconfig lists the interface as Mode "Auto" 
immediately after it is added:

root@ion:/home/sturmflut# iwconfig mesh
mesh      IEEE 802.11bg  Mode:Auto  Tx-Power=11 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

and falls back to "Managed" after about five seconds:

root@ion:/home/sturmflut# iwconfig mesh
mesh      IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated
          Tx-Power=11 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

Symptoms are identical on both machines. I remember this working some weeks 
ago, at least using the ath5k driver, and without any "Name not unique on 
network" errors.

I could try with a full wireless-testing.git checkout but I doubt anything 
will change, Ubuntus 2.6.31-11-generic is quite recent and all relevant 
modules should have been overwritten by those in compat-wireless.

regards,
Simon Raffeiner

University of Applied Sciences Offenburg

             reply	other threads:[~2009-09-27 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 13:41 Simon Raffeiner [this message]
2009-09-28 20:28 ` Unable to create an 802.11s mesh using compat-wireless-2009-09-27 Andrey Yurovsky

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=200909271541.58448.sturmflut@lieberbiber.de \
    --to=sturmflut@lieberbiber.de \
    --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