multiple bss - tsf remains 0

Michael Voorhaen michael.voorhaen at ua.ac.be
Mon May 3 10:02:45 EDT 2010


I've noticed that the tsf of vap1 remains 0 and is not incremented like the 'primary' IP. It also seems that this is the reason why the client is not attempting to associate. Any suggestions?

Regards,
Michael

PS the output from iwlist scan

          Cell 12 - Address: 00:80:48:53:00:3F
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=70/70  Signal level=-30 dBm  
                    Encryption key:off
                    ESSID:"test"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000ce1d0a182
                    Extra: Last beacon: 195ms ago
                    IE: Unknown: 00056C64333965
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
          Cell 13 - Address: 00:80:48:53:00:40
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=31/70  Signal level=-79 dBm  
                    Encryption key:off
                    ESSID:"vap1"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 11235ms ago
                    IE: Unknown: 000476617031
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030101
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C



Groeten,
Michael

-------------------------
IBBT - PATS research group
Dept. of Mathematics and Computer Sciences
University of Antwerp
Campus Middelheim, G3.30
Middelheimlaan 1
B-2020 Antwerpen, Belgium
Phone: +32 (0)3 265.38.75
Fax: +32 (0)3 265.37.77
Web: www.pats.ua.ac.be/michael.voorhaen









On 29 Apr 2010, at 19:43, Michael Voorhaen wrote:

> Hi,
> 
> I'm trying to run several APs on 1 interface and I'm always having some trouble connecting to the second AP created. The idea would be to have each AP connected to a different bridge (this is possible right?).
> 
> I'm using 2.6.32 and hostapd-git for my tests.
> 
> I've tried the following configurations:
> 
> 1. separate hostapd.conf files for each AP started with:
> 
> hostapd /etc/hostapd.conf /etc/hostapd.vap1.conf
> 
> /etc/hostapd.conf
> 
> interface=wlan1
> bridge=br0
> driver=nl80211
> auth_algs=3
> debug=0
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> beacon_int=100
> max_num_sta=255
> hw_mode=g
> channel=1
> ssid=test
> 
> /etc/hostapd.vap1.conf
> 
> interface=vap1
> bridge=br1
> driver=nl80211
> auth_algs=3
> debug=0
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> beacon_int=100
> max_num_sta=255
> hw_mode=g
> channel=1
> ssid=nl80211vap1
> 
> This results in both access points becoming visible when I scan on another device, but I'm unable to connect to the one configured in the second file (both are open btw).
> 
> Both wireless interfaces are added to their respective bridge interface automatically.
> 
> 2. Define an additional bss in hostapd.conf.
> 
> This has the same behavior, only the second AP is never added to the configured bridge. I used the following config file for this.
> 
> interface=wlan1
> bridge=br0
> driver=nl80211
> auth_algs=3
> debug=0
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> beacon_int=100
> max_num_sta=255
> hw_mode=g
> channel=1
> ssid=test
> bss=vap1
> bridge=br1
> #bssid=00:80:48:53:00:40
> ssid=vap1
> 
> 3. Running the APs on two different physical interfaces worked just fine.
> 
> Any ideas? I noticed from the git commit messages that there were some recent changes to the multi-BSS parts, could this be causing my problems?
> 
> Best regards,
> Michael
> 
> -------------------------
> IBBT - PATS research group
> Dept. of Mathematics and Computer Sciences
> University of Antwerp
> Campus Middelheim, G3.30
> Middelheimlaan 1
> B-2020 Antwerpen, Belgium
> Phone: +32 (0)3 265.38.75
> Fax: +32 (0)3 265.37.77
> Web: www.pats.ua.ac.be/michael.voorhaen
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at lists.shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



More information about the HostAP mailing list