linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanthearith HUON <chanthearith.huon@telecom-sudparis.eu>
To: Andrey Yurovsky <andrey@cozybit.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, Hakima.Chaouchi@it-sudparis.eu
Subject: Re: SIOCSIFFLAGS: Name not unique on network
Date: Sat, 24 Jan 2009 09:24:04 +0100	[thread overview]
Message-ID: <497AD024.2050301@telecom-sudparis.eu> (raw)
In-Reply-To: <45e8e6c40901231457x57625153wad49b4869a1627bd@mail.gmail.com>

Thank you very much, this problem also occured with supported cards.
I solved this problem with both broadcom and intel wireless cards.

I deactivated the physical interface first before using mesh interfaces 
and no more error message.
However, since you mentionned that non of Intel card support mesh, now I 
only use broadcom wireless cards for testing.

I followed the howto http://www.open80211s.org/trac/wiki/HOWTO
but things did not work as expected.

my broadcom wireless cards
"
card: Broadcom Corporation BCM4306
driver: b43legacy
"

Here are commands for all my pcs except mesh interface name and ip which 
are different thereby i replace them here by X.
"
Killall NetworkManager
iw dev wlan0 interface add meshX type mp mesh_id mymesh
ifconfig wlan0 down
iwconfig meshX mode Ad-hoc
ifconfig meshX up
iwconfig meshX channel 2.462G
ifconfig meshX inet 192.168.1.X netmask 255.255.255.0
"

However, with "iw dev meshX station dump" in all experiement machines, 
nothing displayed on the screen as a result. I waited and no route 
constructed between them. Thus, I can not ping any mesh neighbors.

I would like to know ur suggestion? what is missing or...?

Thank,
Thierry

Andrey Yurovsky wrote:
> On Fri, Jan 23, 2009 at 2:21 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>   
>> On Thu, 2009-01-22 at 16:19 +0100, Chanthearith HUON wrote:
>>
>>     
>>> This wireless card is not listed
>>> in http://linuxwireless.org/en/users/Devices
>>> <http://linuxwireless.org/en/users/Devices>
>>> but the driver is in the
>>> list http://linuxwireless.org/en/developers/Documentation/mac80211#mac80211drivers
>>> <http://linuxwireless.org/en/developers/Documentation/mac80211#mac80211drivers>
>>>       
>> But it's listed here:
>> http://linuxwireless.org/en/users/Drivers
>>
>> -- as not supporting mesh.
>>
>>     
>>> The OS is ubuntu Intrepid Ibex 8.10 with kernel 2.6.27-9-generic
>>>
>>> After creating new interface for mesh "iw dev wlan0 interface add mesh
>>> type mp mesh_id 100". I turned the mesh interface up by "ifconfig mesh up".
>>> I got following error message
>>> " SIOCSIFFLAGS: Name not unique on network "
>>>       
>> That's strange, it should not have allowed you to add the interface in
>> the first place. But then, you're using an ancient kernel anyway...
>>
>> johannes
>>
>>     
>
> That's indeed strange: the iwl3945 (along with the other Intel cards)
> definitely doesn't support mesh but I was able to add an interface as
> well on my Ubuntu box (2.6.27-9).  I think the reason is that iwlwifi
> doesn't explicitly test for interfaces it actually supports:
>
> static int iwl3945_mac_add_interface(struct ieee80211_hw *hw,
>                                  struct ieee80211_if_init_conf *conf)
> {
>         struct iwl_priv *priv = hw->priv;
>         unsigned long flags;
>
>         IWL_DEBUG_MAC80211("enter: type %d\n", conf->type);
>
>         if (priv->vif) {
>                 IWL_DEBUG_MAC80211("leave - vif != NULL\n");
>                 return -EOPNOTSUPP;
>         }
> <snip>
>   


  reply	other threads:[~2009-01-24  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 15:19 SIOCSIFFLAGS: Name not unique on network Chanthearith HUON
2009-01-23 22:21 ` Johannes Berg
2009-01-23 22:57   ` Andrey Yurovsky
2009-01-24  8:24     ` Chanthearith HUON [this message]
2009-01-24 14:11     ` Johannes Berg

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=497AD024.2050301@telecom-sudparis.eu \
    --to=chanthearith.huon@telecom-sudparis.eu \
    --cc=Hakima.Chaouchi@it-sudparis.eu \
    --cc=andrey@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --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).