I have xsupplicant (CVS with hardcoded username/password because they change
the config file format currently) running with this configuration:
[CONFIG] ----------- Current Values for Network WA22 -----------
[CONFIG] Username : MNCI
[CONFIG] Password : mnci
[CONFIG] Root Certificate : /etc/1x/root.pem
[CONFIG] Client Certificate : /etc/1x/cert-clt.pem
[CONFIG] Root Cert. Dir. : (null)
[CONFIG] CRL Directory : (null)
[CONFIG] Key File : /etc/1x/cert-clt.pem
When I call it, I see (besides other stuff) this output:
...
[STATE] Processing ACQUIRED state.
Connection established, authenticating...
[STATE] Sending EAPOL-Response-Identification
[ALL] Frame to be sent :
00 02 2D 81 77 8E 00 10 - C6 19 27 09 88 8E 01 00 ..-.w.....'.....
00 0B 02 00 00 0B 01 3F - 00 4D 4E 43 49 00 00 00 .......?.MNCI...
...
In which RFC is the format of this packet described? I ask this, because
after the EAPOL-Packet goes to an Intermec WA22 Access-Point and then to my
freeRADIUS-Server (CVS), I see this:
...
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.233.220:1988, id=15,
length=128
User-Name = "?\000MNCI"
NAS-IP-Address = 192.168.233.220
Called-Station-Id = "00-10-40-04-e4-72"
NAS-Identifier = "16600300057"
NAS-Port-Type = Wireless-802.11
Framed-MTU = 1400
Calling-Station-Id = "00-10-c6-19-27-09"
EAP-Message = 0x0200000b013f004d4e4349
Message-Authenticator = 0x3935ecc3ce1242745d5b399879cb3f62
...
Here the username became suddenly "?\000MNCI".
Anybody any idea on why this happened?
--
Try Linux 2.6 from BitKeeper for PXA2x0 CPUs at
http://www.mn-logistik.de/unsupported/linux-2.6/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
