ben, setting the AP's to the same channel works! thx :-) On 31 August 2010 10:29, Ryszard <ryszard99@xxxxxxxxx> 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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx> >> Candela Technologies Inc http://www.candelatech.com >> >> > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
