Re: "double" realm problem

solved it now another way: authorize { auth_log suffix mschap eap { ok = return } if ( ("%{User-Name}" !~ /@/) || ("%{User-Name}" =~ /@.*@/)) { update r

Re: "double" realm problem

when i put the "validate_username" direct after server eduroam { validate_username authorize { . i do not get an error. but it doesnt work. i am just trying around, i know that the "validate_username" doesnt make sense when NOT in the authorize section. so anyone has an idea redg

Re: "double" realm problem

Hi, > /etc/raddb/sites-enabled/eduroam[9]: Failed to find module > "validate_username". > /etc/raddb/sites-enabled/eduroam[2]: Errors parsing authorize section. hmm, interesting - this looks very much like a post i made here earlier this month where 3rd-party virtual servers dont seem to pick up

Re: "double" realm problem

hello alexander, thanks alot for this piece of code. but now i have a problem with getting this to work. in radiusd.conf i have an $INCLUDE policy.conf and in my authorize section i got the following: authorize { auth_log validate_username suffix

Re: "double" realm problem

mr typo wrote: > > i was trying to reject those "double" realm. > but i cannot find the right syntax and/or where to put the lines. > > i was trying to put this lines in the user file: > DEFAULT User-Name =~ "/^...@company.com@.*/" > Auth-Type := Reject > > > that did not work. > when puttin

Re: "double" realm problem

i was trying to reject those "double" realm. but i cannot find the right syntax and/or where to put the lines. i was trying to put this lines in the user file: DEFAULT User-Name =~ "/^...@company.com@.*/" Auth-Type := Reject that did not work. when putting: if (User-Name ~= /^...@company.com@

Re: "double" realm problem

mr typo wrote: > > i do have a problem with our freeradius configuration and i have no idea how > to solve it. > > we do have one realm configured domainname.com which works perfectly. every > user who wants to authenticate with a different realm is proxied to an > outside radius. server. the se

Re: "double" realm problem

where would be the best place to deny those users? we do not have alot of practice with freeradius, so any help would be appreciated, kind regards -euroreg On Wed, Oct 7, 2009 at 3:03 PM, mr typo wrote: > hey, > yes we are talking about eduroam and after reading your post, it seems > like tha

Re: "double" realm problem

hey, yes we are talking about eduroam and after reading your post, it seems like that it is the best to deny such users. thanks alot -euroreg On Wed, Oct 7, 2009 at 2:44 PM, Stefan Winter wrote: > Hi, > > > problem is, that we are a university, so they are "our" people. > > tousands of student

Re: "double" realm problem

Hi, > problem is, that we are a university, so they are "our" people. > tousands of students and teachers. if we deny those users, our > helpdesk will get more work. > is there a way to remove the double entries or do i have to block those? Any chance we are talking about eduroam? In this case: d

Re: "double" realm problem

problem is, that we are a university, so they are "our" people. tousands of students and teachers. if we deny those users, our helpdesk will get more work. is there a way to remove the double entries or do i have to block those? -euroreg On Wed, Oct 7, 2009 at 1:50 PM, Alan Buxey wrote: > Hi, >

Re: "double" realm problem

Hi, > we do have one realm configured domainname.com which works perfectly. every > user who wants to authenticate with a different realm is proxied to an > outside radius. server. the setup works fine. > > we do have some mobile devices who send something like: > usern...@company.com@wlan.mnc003

Re: "double" realm problem

Hi, > we do have one realm configured domainname.com > which works perfectly. every user who wants to authenticate with a > different realm is proxied to an outside radius. server. the setup > works fine. > > we do have some mobile devices who send something like: > usern

"double" realm problem

Hello all, i do have a problem with our freeradius configuration and i have no idea how to solve it. we do have one realm configured domainname.com which works perfectly. every user who wants to authenticate with a different realm is proxied to an outside radius. server. the setup works fine. we