> Once upon a time Dietmar Stommel shaped the electrons to say...
> >That means, RADIUS terminates usernames on ANY whitespace before check the
> >auth. , but it send back the unterminated usrename to our MAX 4000 ! And
>
> No - RADIUS never sends a username BACK. In fact, that is not allowed by
> the RFC.
>
> It is just that the NAS keeps using what the user actually typed and does
> not truncate locally. And RADIUS accounting doesn't either, it is a simple
> logging deamon that slavishly logs what it gets.
>
> >so USER "test01" never log in, but he did, with a wrong Username ! And we
> >have a problem with accounting !
>
> You have to write your accounting scripts to truncate on whitespace too.
I think to modify the accounting scripts is not the fine way. Can i
modify the radiusd-source to accept Blank's.
There is another Problem. Entries in /etc/rqaddb/users are ignored, when
using blanks in username !
For example: /etc/raddb/users
->
test01 Password = "UNIX"
User-Service = Framed-User,
Ascend-Send-Auth= Send-Auth-PAP,
Framed-Protocol = PPP,
Framed-Address = 0.0.0.0,
Framed-Netmask = 255.255.255.0,
Ascend-Idle-Limit = 0,
Ascend-IP-Direct = 194.10.200.83,
Ascend-Assign-IP-Pool = 1
With this entrie i want to restrict the user test01, but when he logged in
with "test01 123" RADIUSD ignored the /etc/raddb/users, because it don't
find a match. And so the user can work whithout 'IP-Direct'.
>
> -MZ
> --
> Livingston Enterprises - Chair, Department of Interstitial Affairs
> Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
> For support requests: support@livingston.com <http://www.livingston.com/>
> Snail mail: 4464 Willow Road, Pleasanton, CA 94588
>