linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Horacio J. Peña" <horape@compendium.com.ar>
To: linux-wireless@vger.kernel.org
Subject: Re: Multiple Virtual Interfaces: when the station one fails the ap follows
Date: Thu, 22 Sep 2011 10:23:32 -0300	[thread overview]
Message-ID: <20110922132332.GY18063@compendium.com.ar> (raw)
In-Reply-To: <20110917205507.GK8298@compendium.com.ar>

Following on this, I've found that "It seems that this channel hopping looking
for AP1 is what breaks AP2." was wrong. I've tried a very dirty workaround,
making a fake regulatory domain that only allows channel 6. Then, there is no
channel hopping, but still the AP2 doesn't works. It sometimes sends out Probe
Responses but no beacons.

Some idea on where to look?

Thanks,
Horacio J. Peña

On Sat, Sep 17, 2011 at 05:55:07PM -0300, Horacio J. Peña wrote:
> [Please excuse me the openwrt syntax, I wrote this first on the openwrt forum]
> 
> When using multiple virtual interfaces like:
> 
> 
> config wifi-device  radio0
>         option type     mac80211
>         option channel  6
> ...
> 
> config wifi-iface
>         option device   radio0
>         option network  wan
>         option mode     sta
>         option ssid     AP1
> ...
> config wifi-iface
>         option device   radio0
>         option network  wlan
>         option mode     AP2
> 
> 
> If wan gets deassociated from AP1, it gets impossible to associate to AP2 network. 
> 
> Looking with airodump-ng I see a few beacons sent on the right channel and that it's sending probes on the wrong channels. It seems that this channel hopping looking for AP1 is what breaks AP2.
> 
> It seems that devices in managed mode disregard the channel configuration. Is there any way to force it?
> 
> This has been tested on a TP-LINK MR3420 (AR9287)
> 
> Thanks!
> -- 
> Horacio J. Peña
> horape@compendium.com.ar
> horape@uninet.edu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Horacio J. Peña
horape@compendium.com.ar
horape@uninet.edu

      reply	other threads:[~2011-09-22 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17 20:55 Multiple Virtual Interfaces: when the station one fails the ap follows Horacio J. Peña
2011-09-22 13:23 ` Horacio J. Peña [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=20110922132332.GY18063@compendium.com.ar \
    --to=horape@compendium.com.ar \
    --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).