<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>HI, All,<BR>
<BR>
I have read the "802.11r" section in the "hostapd.conf" file. But it seems hard to me.<BR>
Are there more detail explain or examples on how to write the conf-file?<BR>
<BR>
Best Wishes,<BR>
<BR>
Shawn<BR>
<BR>
------------------------------<BR>
<BR>
##### IEEE 802.11r configuration ##############################################<BR>
# Mobility Domain identifier (dot11FTMobilityDomainID, MDID)<BR># MDID is used to indicate a group of APs (within an ESS, i.e., sharing the<BR># same SSID) between which a STA can use Fast BSS Transition.<BR># 2-octet identifier as a hex string.<BR>#mobility_domain=a1b2<BR>
# PMK-R0 Key Holder identifier (dot11FTR0KeyHolderID)<BR># 1 to 48 octet identifier.<BR># This is configured with nas_identifier (see RADIUS client section above).<BR>
# Default lifetime of the PMK-RO in minutes; range 1..65535<BR># (dot11FTR0KeyLifetime)<BR>#r0_key_lifetime=10000<BR>
# PMK-R1 Key Holder identifier (dot11FTR1KeyHolderID)<BR># 6-octet identifier as a hex string.<BR>#r1_key_holder=000102030405<BR>
# Reassociation deadline in time units (TUs / 1.024 ms; range 1000..65535)<BR># (dot11FTReassociationDeadline)<BR>#reassociation_deadline=1000<BR>
# List of R0KHs in the same Mobility Domain<BR># format: <MAC address> <NAS Identifier> <128-bit key as hex string><BR># This list is used to map R0KH-ID (NAS Identifier) to a destination MAC<BR># address when requesting PMK-R1 key from the R0KH that the STA used during the<BR># Initial Mobility Domain Association.<BR>#r0kh=02:01:02:03:04:05 r0kh-1.example.com 000102030405060708090a0b0c0d0e0f<BR>#r0kh=02:01:02:03:04:06 r0kh-2.example.com 00112233445566778899aabbccddeeff<BR># And so on.. One line per R0KH.<BR>
# List of R1KHs in the same Mobility Domain<BR># format: <MAC address> <R0KH-ID> <128-bit key as hex string><BR># This list is used to map R1KH-ID to a destination MAC address when sending<BR># PMK-R1 key from the R0KH. This is also the list of authorized R1KHs in the MD<BR># that can request PMK-R1 keys.<BR>#r1kh=02:01:02:03:04:05 02:11:22:33:44:55 000102030405060708090a0b0c0d0e0f<BR>#r1kh=02:01:02:03:04:06 02:11:22:33:44:66 00112233445566778899aabbccddeeff<BR># And so on.. One line per R1KH.<BR>
# Whether PMK-R1 push is enabled at R0KH<BR># 0 = do not push PMK-R1 to all configured R1KHs (default)<BR># 1 = push PMK-R1 to all configured R1KHs whenever a new PMK-R0 is derived<BR>#pmk_r1_push=1<BR><br /><hr />Stay in touch when you're away with Windows Live Messenger. <a href='http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008' target='_new'>IM anytime you're online.</a></body>
</html>