After further thought, how about this: # Optional NAS-Identifier, containing a string value used to identify the NAS # originating RADIUS packets. This must be unique to the NAS within the # scope of a RADIUS server. For example, a fully qualified domain name can be # used here appended with the . # Where nas_identifier has not been set, the BSSID will be sent in RADIUS # packets. This will be of the form 00-10-A4-23-19-C0. # When using IEEE 802.11r, nas_identifier must be set and be between 1 and # 48 octets long. #nas_identifier=ap.example.com # Whether to include the BSSID in the NAS-Identifier sent in RADIUS packets. # For example, where the nas_identifier is configured as ap.example.com, a # value of the form ap.example.com_00-10-A4-23-19-C0 will be used. # Where mutiple BSSes are offered by a NAS, each BSS for which RADIUS accounting # is occuring must be presented as being an individual NAS for Accounting-On and # Accounting-Off to be handled correctly by a RADIUS server. # This option has no effect where the nas_identifier has not been set. # Where this is the case, the BSSID will always be sent. # This will be of the form 00-10-A4-23-19-C0. nas_identifier_include_bssid=1 Cheers, Nick _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
