Observing same error after restarting the radius server and using the DB. So I
think Radius server is remembering the PAC for this reason it's not getting
authenticated.
Regards
Sudhir H
-Original Message-
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Beha
Hi Heiki,
Still I am not clear about the working of EAP-FAST with MSCHAPv2.
In this case:
Whenever I flash the code to the device(client), its generating the new PAC
with this radius server and the client are authenticated successfully.
If I restart the radius server means by pressing ctrl+c it s
On 04/17/2012 01:29 PM, Sudhir Harwalkar wrote:
>
> Because previously it was working fine without any modification from client
> side, does modification in EAP_43.pm is affecting for authentication?
> From the client log its failing after username and Pw. See the screen shot of
> the client log
I have taken myself out of the "users" unix group and was still able to login,
shouldnt this setup that was suggested deny my logon? At this point of testing
all we want to have is a users logon ID and its group membership be verified
before granting access to the networking equipment. What is
Hi Hugh,
I just now had a call with the vendor. he confirmed they are sending
encrypted requests.
will keep posting updates.
Regards,
-Manish
From: Hugh Irvine
To: Heikki Vatiainen
Cc: radiator@open.com.au
Sent: Tuesday, April 17, 2012 3:47 PM
Subject
Hello Manish, Hello Heikki -
I have seen these before - they are probes from the device with usernames of
this form.
There is nothing wrong with your configuration - but you might want to turn off
these probes on the device.
regards
Hugh
On 17 Apr 2012, at 17:18, Heikki Vatiainen wrote:
>
Hi
Thanks for the response. I'm doing replace into statements for the DB
inserts. Show engine innodb status looks alright to me (although I'm not
100% sure what I'm looking for!).
Is there a way to alter the deadlock timeout?
Cheers
On 17/04/2012 05:30, "Ben Lisle" wrote:
>I'd check what is ha
On 04/17/2012 11:11 AM, Sudhir Harwalkar wrote:
> See the attached radiator log file.
Radiator does not find the PAC the client sends and would create a new
PAC. The client, however, expects something else and sends "slv3 alert
unexpected message". Try resetting the client or making sure it can
r
On 04/17/2012 09:47 AM, Arya, Manish Kumar wrote:
> We have configured ALU devices to authenticate against radiator
> server. I have added vendor dictionary to config and created client list.
> but I see mangled username in radius logs. not sure why this is
> happening. here is snapshot of my
On 04/17/2012 08:38 AM, Sudhir Harwalkar wrote:
> After creating the DB and used config files, I am getting an error as:
> ERR: EAP-FAST TLS Handshake unsuccessful: 1248: 1 - error:140943F2:SSL
> routines:SSL3_READ_BYTES:sslv3 alert unexpected message
>
> See the DB file attached with this.
Th
10 matches
Mail list logo
