From: Ryszard <ryszard99@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Florian Fainelli <florian@openwrt.org>,
Patrick McHardy <kaber@trash.net>,
linux-wireless@vger.kernel.org
Subject: Re: virtual access poitns (ath5k/mac80211)
Date: Tue, 31 Aug 2010 20:19:01 +1000 [thread overview]
Message-ID: <AANLkTi=euxWBB94ubR6WF0Yv4KmOfvorH+7_h8Py41Mj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinkv5dbKT_PKAv3L0atFW95p3_WvqZL5ZD9S4vw@mail.gmail.com>
ben, setting the AP's to the same channel works! thx :-)
On 31 August 2010 10:29, Ryszard <ryszard99@gmail.com> wrote:
> ah, that might be it! i've got them configured on different channels.
> i'm not at home now, but will check it in probably about 10 hours or
> so and let you know..
>
> thanks once again for the quick reply!!
>
> On 31 August 2010 10:05, Ben Greear <greearb@candelatech.com> wrote:
>> On 08/30/2010 04:52 PM, Ryszard wrote:
>>>
>>> hey ben,
>>>
>>> i've set everything up and have all the routing working etc etc. it
>>> seems as tho' there is one last issue i'm hoping you can point me in
>>> the right direction with.
>>>
>>> When the device i'm working on boots i've got hostapd starting up with
>>> two VAP's (vap0 and vap1). when i connect to on AP everything goes
>>> well and i can send and receive traffic, however when i disconnect and
>>> reconnect to the other AP it seems as tho' the client connection
>>> hangs.
>>>
>>> Inspecting syslog shows all the dhcp information for the 1st
>>> connection, however there is nothing in syslog for the 2nd connection.
>>>
>>> have you seen this, or have an idea why it may happen by chance?
>>
>> Make sure both APs are configured on the same channel in hostapd?
>>
>> An example of two of my hostapd config files are below, in case that helps:
>>
>> [root@lanforge-D0-20 wifi]# more hostapd_vap0.conf
>> ### Auto-generated by LANforge...do not attempt to modify.
>> interface=vap0
>> driver=nl80211
>> logger_syslog=-1
>> logger_syslog_level=2
>> logger_stdout=-1
>> logger_stdout_level=2
>> dump_file=wifi/hostapd_vap0.dump
>> ctrl_interface=/var/run/hostapd
>> ctrl_interface_group=0
>> ssid=
>> bssid=00:1f:f1:d0:0f:00
>> country_code=US
>> ieee80211d=0
>> hw_mode=a
>> channel=1
>> beacon_int=240
>> dtim_period=2
>> max_num_sta=2007
>> rts_threshold=2347
>> fragm_threshold=2346
>> preamble=0
>> macaddr_acl=0
>> auth_algs=3
>> ignore_broadcast_ssid=0
>> wme_enabled=0
>> wme_ac_bk_cwmin=4
>> wme_ac_bk_cwmax=10
>> wme_ac_bk_aifs=7
>> wme_ac_bk_txop_limit=0
>> wme_ac_bk_acm=0
>> wme_ac_be_aifs=3
>> wme_ac_be_cwmin=4
>> wme_ac_be_cwmax=10
>> wme_ac_be_txop_limit=0
>> wme_ac_be_acm=0
>> wme_ac_vi_aifs=2
>> wme_ac_vi_cwmin=3
>> wme_ac_vi_cwmax=4
>> wme_ac_vi_txop_limit=94
>> wme_ac_vi_acm=0
>> wme_ac_vo_aifs=2
>> wme_ac_vo_cwmin=2
>> wme_ac_vo_cwmax=3
>> wme_ac_vo_txop_limit=47
>> wme_ac_vo_acm=0
>> ieee8021x=0
>> eapol_key_index_workaround=0
>> eap_server=0
>> own_ip_addr=127.0.0.1
>> [root@lanforge-D0-20 wifi]# more hostapd_vap1.conf
>> ### Auto-generated by LANforge...do not attempt to modify.
>> interface=vap1
>> driver=nl80211
>> logger_syslog=-1
>> logger_syslog_level=2
>> logger_stdout=-1
>> logger_stdout_level=2
>> dump_file=wifi/hostapd_vap1.dump
>> ctrl_interface=/var/run/hostapd
>> ctrl_interface_group=0
>> ssid=
>> bssid=00:1f:f1:d0:0f:01
>> country_code=US
>> ieee80211d=0
>> hw_mode=a
>> channel=1
>> beacon_int=240
>> dtim_period=2
>> max_num_sta=2007
>> rts_threshold=2347
>> fragm_threshold=2346
>> preamble=0
>> macaddr_acl=0
>> auth_algs=3
>> ignore_broadcast_ssid=0
>> wme_enabled=0
>> wme_ac_bk_cwmin=4
>> wme_ac_bk_cwmax=10
>> wme_ac_bk_aifs=7
>> wme_ac_bk_txop_limit=0
>> wme_ac_bk_acm=0
>> wme_ac_be_aifs=3
>> wme_ac_be_cwmin=4
>> wme_ac_be_cwmax=10
>> wme_ac_be_txop_limit=0
>> wme_ac_be_acm=0
>> wme_ac_vi_aifs=2
>> wme_ac_vi_cwmin=3
>> wme_ac_vi_cwmax=4
>> wme_ac_vi_txop_limit=94
>> wme_ac_vi_acm=0
>> wme_ac_vo_aifs=2
>> wme_ac_vo_cwmin=2
>> wme_ac_vo_cwmax=3
>> wme_ac_vo_txop_limit=47
>> wme_ac_vo_acm=0
>> ieee8021x=0
>> eapol_key_index_workaround=0
>> eap_server=0
>> own_ip_addr=127.0.0.1
>>
>>
>> If you still have no luck, please send output of:
>>
>> ifconfig -a
>>
>> route -n
>>
>> tail -200 /var/log/messages
>>
>> dmesg
>>
>> on your VAP machine.
>>
>> Thanks,
>> Ben
>>
>>
>> --
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc http://www.candelatech.com
>>
>>
>
prev parent reply other threads:[~2010-08-31 10:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 1:53 virtual access poitns (ath5k/mac80211) Ryszard
2010-08-01 9:37 ` Florian Fainelli
2010-08-01 20:56 ` Ryszard
2010-08-01 22:21 ` Ben Greear
[not found] ` <AANLkTi=FEFrKdXUHN-h-BZruvNzSmwXdPcq9-OgZcFAM@mail.gmail.com>
2010-08-02 5:00 ` Ben Greear
[not found] ` <AANLkTim8i245P0nGcnpsf63_O8xXeby9re=pX53WfOwV@mail.gmail.com>
2010-08-07 5:23 ` Ryszard
2010-08-08 18:51 ` Ben Greear
2010-08-09 23:58 ` Ryszard
2010-08-10 0:05 ` Ben Greear
2010-08-10 0:11 ` Ryszard
2010-08-10 16:54 ` Luis R. Rodriguez
2010-08-10 17:06 ` Ben Greear
2010-08-10 17:39 ` Luis R. Rodriguez
2010-08-21 3:07 ` Ryszard
2010-08-23 4:43 ` Ryszard
2010-08-30 2:47 ` Ryszard
2010-08-30 23:52 ` Ryszard
2010-08-31 0:05 ` Ben Greear
2010-08-31 0:29 ` Ryszard
2010-08-31 10:19 ` Ryszard [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='AANLkTi=euxWBB94ubR6WF0Yv4KmOfvorH+7_h8Py41Mj@mail.gmail.com' \
--to=ryszard99@gmail.com \
--cc=florian@openwrt.org \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).