FreeRadius upgrade from 1.3 to 2.0.4

Trevor Jennings tjennings at
Fri Mar 5 00:00:26 CET 2010


My apologies, it was 1.1.3!! That will teach me not to look at the version
before posting!

Anyway, I did upgrade to the latest stable (2.1.8?) and then realized that I
had not entered a realm in the proxy.conf. Once I did that, the
username at domain were stripped!!!

So everything is good!!!  Thanks for your reply.

 - Trevor

On Thu, Mar 4, 2010 at 5:32 PM, Alan Buxey <A.L.M.Buxey at> wrote:

> Hi,
> >  I recently upgraded one of our freeradius servers from 1.3.3 to 2.0.4.
> We use this for mac authentication for wireless which is working fine and
> also ldap authentication for our vpn users.
> just to note there was never a 1.3 or a 1.3.3 version of FreeRADIUS. the 1x
> train has 1.0.3 or 1.1.3
> but stops, currently at 1.1.8
> > The problem I am having with the ldap authentication is that when a user
> tries to authenticate with their user at domain, it does not work! However,
> it works fine if the user does not add the domain name. Is there a glitch
> with v2.0.4 or a configuration issue that I am missing?
> any particular reason for the 2.0.4 version? there were many bugs in the
> 2.0.x train - I would serious
> consider running the latest 2.1.x release  (version 2.1.8)
> > I am using this in the ldap config:-
> > filter = "(sAMAccountName=%{%{Stripped-User-Name}:-%{User-Name}})"
> >
> > but the Stripped-User-Name appears to be blank when using debug mode.
> the full debug will show what and why things happen to the
> Stripped-User-Name -
> did you migrate you config to 2.0.4 or just dump the 1.x config over the
> top? if
> you did the latter then you are doomed to wierd issues happening.
> alan
> -
> List info/subscribe/unsubscribe? See
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Freeradius-Users mailing list