Marcotte, Tyler wrote:
Thank you for the response, even if it was ridden with unnecessary
sarcasm.
shrug After nearly a decade on this list, I've found that the best
way to convince certain people to READ my messages, and to THINK about
the problem they have is to be blunt. Those people
Marcotte, Tyler wrote:
I can understand that nowhere in any documentation does it say that an
Access-Reject is sent back (I just double-checked to verify). However,
what I don't understand is why not?
Because it's an EAP method, *and* it's TLS. Go read the debug output
again: the inner
insightful, even if
it was condescending and rude.
Regards,
-Tyler
-Original Message-
From: [EMAIL PROTECTED]
[mailto:freeradius-
[EMAIL PROTECTED] On Behalf Of Alan DeKok
Sent: Thursday, October 11, 2007 3:35 AM
To: FreeRadius users mailing list
Subject: Re: Simultaneous-Use and PEAP
On Thu, 2007-10-11 at 15:11 -0400, Marcotte, Tyler wrote:
Thank you for the response, even if it was ridden with unnecessary
sarcasm.
I wasn't trying to argue, I was trying to understand why an
Access-Reject wasn't sent back. Thank you for explaining that.
While I don't necessarily agree
Hi, You said it's a bug in 1.x. I just tried the latest code in the cvs
repository (2.0 I believe) and I still get the same problem. After the
PEAP failure, it sends an Access-Challenge rather than an Access-Reject.
Am I missing anything else here?
Thank you in advance.
Regards,
-Tyler
Marcotte, Tyler wrote:
Hi, You said it's a bug in 1.x. I just tried the latest code in the cvs
repository (2.0 I believe) and I still get the same problem. After the
PEAP failure, it sends an Access-Challenge rather than an Access-Reject.
That's completely different from what you said
Marcotte, Tyler wrote:
Hi, You said it's a bug in 1.x. I just tried the latest code in the
cvs
repository (2.0 I believe) and I still get the same problem. After
the
PEAP failure, it sends an Access-Challenge rather than an Access-
Reject.
That's completely different from what you
Marcotte, Tyler wrote:
...
PEAP: Got tunneled reply RADIUS code 3
Reply-Message := \r\nYou are already logged in - access
denied\r\n\n
PEAP: Processing from tunneled session code 0x81667248 3
Reply-Message := \r\nYou are already logged in - access
denied\r\n\n
PEAP:
So? Why would you expect it to send an Access-Reject? If you watch
what happens next in the conversation, you should see the side effects
of the Simultaneous-Use.
I'm not surprised at this behavior. It's what is *supposed* to
happen.
Alan DeKok.
I can understand that nowhere in
Marcotte, Tyler wrote:
I've configured Simultaneous-Use on my freeradius server and have it
configured to use PEAP as an authentication method. Users can authenticate
perfectly well, however when the Simultaneous-Use limit is exceeded, it only
half works. The user is not allowed on, the
Marcotte, Tyler wrote:
I've configured Simultaneous-Use on my freeradius server and have it
configured to use PEAP as an authentication method. Users can
authenticate
perfectly well, however when the Simultaneous-Use limit is exceeded,
it
only half works. The user is not allowed on, the PEAP
11 matches
Mail list logo
