>
> Howdy,
>
> We ran into this with radius 2.0 on a linux 2.0.33 system. Turns out when
> we upgraded to 2.0.1 we started logging several combinations of the following:
>
> Mar 20 16:23:23 grail radius[11849]: user_find: space in username
> <(>IbuQx4?gHL# NBPA%0A> rejected
> Mar 20 16:45:33 grail radius[12382]: user_find: space in username <
> N~S2|3/Jrbmcjr> rejected
> Mar 20 23:32:48 grail radius[21851]: user_find: space in username
> <}xt~N=U]P{W_|:Iq;#SkX8|K~M$t\uT,p\#~N^~-\Z{g5Jo~O9*"gEs l~~ix9$> rejected
>
> I do think someone was trying to give us problems. I fed those username to
> radius 2.0 and guess what... It choked. We have our radius set up so there
> are two daemon processes. I guess this is by default since we didn't alter
> the source code. What these strings do is cause one process to die. The end
> result is no authentication. Then the phones start ringing.
This is one of several things....
1) user has line noise
2) user has encrypted aka secure connection enabled
3) flow control is wrong on someone's modem
4) someone is trying to overflow your RADIUS buffers
There are some notes in the archives about running the daemon as a
standalone -s if I remember right...
check for that and see what happens...
-- Aloha from Paradise,Sherwood
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-radius' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>