Erik Bolsø <[EMAIL PROTECTED]> writes:
> So I must do source-level hacks to be able to send a 1-octet \000
> attribute, with current FreeRADIUS? Have I understood you correctly?
Seems to work here, as long as the attribute is of type "octets".
This test file:
[EMAIL PROTECTED]:/usr/local/test$ cat testfiles/3
User-Name = [EMAIL PROTECTED]
Password = b
NAS-Port-Type = xDSL
Calling-Station-Id =\000
MS-CHAP-Challenge = 0x00
results in:
[EMAIL PROTECTED]:/usr/local/test$ bin/radclient -x localhost:1812 auth
testing123 -f testfiles/3
Sending Access-Request of id 178 to 127.0.0.1 port 1812
User-Name = "[EMAIL PROTECTED]"
Password = "b"
NAS-Port-Type = xDSL
Calling-Station-Id = ""
MS-CHAP-Challenge = 0x00
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=178, length=20
Received on the server as:
Packet-Type = Access-Request
Thu Jun 15 13:55:14 2006
User-Name = "[EMAIL PROTECTED]"
User-Password = "b"
NAS-Port-Type = xDSL
MS-CHAP-Challenge = 0x00
NAS-IP-Address = 127.0.0.1
Stripped-User-Name = "ppp1"
Realm = "example.com"
Calling-Station-Id is a FreeRADIUS "string", not to be confused with
a RFC2865 "string". MS-CHAP-Challenge is a FreeRADIUS "octets" type.
Bjørn
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
