[EMAIL PROTECTED] wrote:
confirm tha EAP-TTLS userid's used to work with freeradius (1.0.5 era
through to 1.1.3) but then only anonymous was seen. i've been following
this User-Name = %{User-Name} etc thread with interest
Ouch. It needs fixing, then. I'm at a conference this week, so I'll
Hi,
Ouch. It needs fixing, then. I'm at a conference this week, so I'll
see what I can do in a few days.
It would be nice to have regression tests for the server...
certainly for eg the glibc double-free issue that has hitbut otherwise
there are so many different permutations and
I can also vouch for freeradius 1.0.5 after building retro-fitting
my configuration to it. I'll probably just downgrade to an earlier
1.1.x build, since I haven't seen any major security
vulnerabilities/
fixes since the early 1.0.x builds.
On Tue, 20 Mar 2007 16:53:26 -0500 [EMAIL PROTECTED]
Sam Schultz wrote:
I have set a DEFAULT entry that sets the User-Name attribute via
':=', but I still end up with two User-Name attributes (anonymous
identity real identity). This is especially strange, since
use_tunneled_reply copy_request_to_tunnel are both enabled as
well.
Then it
On Tue, 20 Mar 2007 09:38:25 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
I have set a DEFAULT entry that sets the User-Name attribute via
':=', but I still end up with two User-Name attributes
(anonymous
identity real identity). This is especially strange, since
Hi,
It worked for me right out of the box at one time, too. I have a
feeling it was using either freeradius 1.1.3 or 1.0.3 (or whatever
FC2 came pre-packaged with). I'll probably test my configuration
against
an earlier version later see if I can establish it as a bug. The
version I've
After alot of experimenting researching, I still haven't found
a solution to the TTL anonymous outer identity being used for
accounting.
I have set a DEFAULT entry that sets the User-Name attribute via
':=', but I still end up with two User-Name attributes (anonymous
identity real identity).
Sam Schultz wrote:
P.S. A link to a list of known-good access points, or personal
recommendations on access points would also be appreciated.
We will be replacing a few 3com APs soon because they don't
play well with...well...ANYTHING. One (3com OfficeConnect)
doesn't even
On Thu, 15 Mar 2007 10:51:17 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
An entry like:
DEFAULT Realm == test, Autz-Type := sql-test
User-Name = %{User-Name}
Please read man users for the definition and meaning of
operators.
You want:
DEFAULT
On Tue, 13 Mar 2007 13:15:52 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
This should be solvable by adding something like
'User-Name = %{User-Name}' to the DEFAULT entries in the users
file,
correct?
Yes.
One of my users file DEFAULT entries look like this:
DEFAULT
-Message d'origine-
De :
[EMAIL PROTECTED]
radius.org
[mailto:[EMAIL PROTECTED]
sts.freeradius.org] De la part de Sam Schultz
Envoyé : mercredi 14 mars 2007 17:13
À : freeradius-users@lists.freeradius.org
Objet : Re: EAP-TTLS outer identity accounting
On Tue, 13 Mar
@lists.freeradius.org
Objet : Re: EAP-TTLS outer identity accounting
On Tue, 13 Mar 2007 13:15:52 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
This should be solvable by adding something like
'User-Name = %{User-Name}' to the DEFAULT entries in the
users
file,
correct
: freeradius-users@lists.freeradius.org
Objet : Re: EAP-TTLS outer identity accounting
On Tue, 13 Mar 2007 13:15:52 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
This should be solvable by adding something like
'User-Name = %{User-Name}' to the DEFAULT entries
Sam Schultz wrote:
I'm currently using EAP-TTLS PAP (via SecureW2) to authorize
authenticate wireless clients against specific realms. Users are
able to authorize authenticate properly, but the username in
incoming accounting replies come in as 'anonymous@realmname'.
You can set
On Tue, 13 Mar 2007 11:58:51 -0500 Alan DeKok
[EMAIL PROTECTED] wrote:
Sam Schultz wrote:
I'm currently using EAP-TTLS PAP (via SecureW2) to authorize
authenticate wireless clients against specific realms. Users are
able to authorize authenticate properly, but the username in
incoming
Sam Schultz wrote:
This should be solvable by adding something like
'User-Name = %{User-Name}' to the DEFAULT entries in the users file,
correct?
Yes.
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
-
List
I'm currently using EAP-TTLS PAP (via SecureW2) to authorize
authenticate wireless clients against specific realms. Users are
able to authorize authenticate properly, but the username in
incoming accounting replies come in as 'anonymous@realmname'.
I had this spitting out proper accounting
17 matches
Mail list logo