Question on HS20, possibly realm related.

Ben Greear greearb at candelatech.com
Thu Sep 19 18:43:11 EDT 2013


I've been testing out some different HS20 configurations on hostapd and wpa_supplicant.

I notice something that seems strange to me.  If I don't configure a user-name in
supplicant, it will not attempt to connect to the AP, but it does not actually matter
what I choose for the user-name..it just needs to exist.

In both cases, hostapd config file looks like this:

interface=vap0
driver=nl80211
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
dump_file=/home/lanforge/wifi/hostapd_vap0.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=ben-138
bssid=80:01:02:03:04:05
country_code=US
ieee80211d=1
hw_mode=a
ieee80211n=1
channel=36
beacon_int=240
dtim_period=2
max_num_sta=2007
rts_threshold=2347
fragm_threshold=2346
preamble=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
# Enable HT modes if you want 300Mbps+ throughput.
#ht_capab=[HT20][HT40-][HT40+][GF][SHORT-GI-20][SHORT-GI-40]
#         [TX-STBC][RX-STBC123][MAX-AMSDU-7935][DSSS_CCK-40][PSMP][LSIG-TXOP-PROT]
ht_capab=[HT20][HT40+][SHORT-GI-40][SHORT-GI-20]
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
ieee8021x=1
own_ip_addr=10.97.1.1
auth_server_addr=192.168.100.119
auth_server_port=1812
auth_server_shared_secret=lanforge
wpa=2
wpa_pairwise=CCMP
wpa_key_mgmt=WPA-EAP

# 802.11u configuration
interworking=1
access_network_type=4
internet=1
asra=1
esr=1
uesa=1
venue_group=2
venue_type=1
hessid=00:00:00:00:00:01
roaming_consortium=01010101
venue_name=eng:LANforge Test Venue
network_auth_type=00
ipaddr_type_availability=04
domain_name=lanforge.org
anqp_3gpp_cell_net=244,91;310,026;234,56
nai_realm=0,lanforge.org,13[5:6],21[2:4][5:7]

# HotSpot 2.0 configuration
hs20=1
hs20_oper_friendly_name=eng:LANforge HotSpot 2.0
hs20_wan_metrics=01:8000:1000:80:240:3000
hs20_operating_class=5173

# Error emulation settings.
ignore_probe_probability=0.000000
ignore_auth_probability=0.000000
ignore_assoc_probability=0.000000
ignore_reassoc_probability=0.000000
corrupt_gtk_rekey_mic_probability=0.000000



The working wpa_supplicant config looks like this:

ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1
can_scan_one=1
min_scan_gap=5

# 802.11u / Interworking configuration.
interworking=1
auto_interworking=1
access_network_type=0

# HotSpot 2.0 configuration
hs20=1

bss_max_count=2000
network={
     interworking_defaults=1
     disable_ht=0
     disable_ht40=0
     disable_sgi=0
     ht_mcs=""
     disable_max_amsdu=-1
     ampdu_factor=-1
     ampdu_density=-1

}

cred={
     username="client"
     password="lanforge"
     ca_cert="/home/lanforge/ca.pem"
     private_key="/home/lanforge/client.p12"
     private_key_passwd="lanforge"
     realm="lanforge.org"
     domain="lanforge.org"
     eap=TLS

}


But, if I remove that 'username="client"', the interworking code will fail its EAP selection.

If I change 'client' to anything else, it still works...so it does not actually seem to be
using that field for anything useful...


Any ideas on this?

Thanks,
Ben



-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



More information about the HostAP mailing list