Hi
I have an issue where I authenticate incoming DHCP requests on a broadband
aggregation router using the Option 82 Port ID information as the username
attribute within the RADIUS authentication request.
Unfortunately the Port ID information includes spaces - and this is causing
an issue where
I have an issue where I authenticate incoming DHCP requests on a broadband
aggregation router using the Option 82 Port ID information as the username
attribute within the RADIUS authentication request.
Unfortunately the Port ID information includes spaces - and this is
causing
an issue
I'm a relatively new freeradius user so I am not really an expert
with it.
I have two users in the racheck table:
admin and d6 40 1a 98. Both with passwords admin198.
Doing this:
*radtest admin admin198 localhost 0 testing123*
..returns an Access-Accept packet.
But doing this:
*radtest d6 40 1a
I'm a relatively new freeradius user so I am not really an expert
with it.
I have two users in the racheck table:
admin and d6 40 1a 98. Both with passwords admin198.
Doing this:
*radtest admin admin198 localhost 0 testing123*
...returns an Access-Accept packet.
But doing this:
*radtest d6 40
Joeven Rex Dizon wrote:
I wonder why the user with spaces in the username is being rejected.
Run the server in debugging mode, as suggested in the FAQ, README,
INSTALL, man page, and *too* often on this list.
I've read somewhere that I need to specify nospace_user. Can I edit
that in the
5 matches
Mail list logo