On 09/16/2013 11:55 PM, Barry Ard wrote:
> I am including my sanitized radius configuration so maybe you can see
> something that I can't.
I'd say the configuration is fine. Another cause might be an EAP
fragment that was sent to the process by the proxy. If the EAP message
looks like having EAP
Hi Heikki,
I am including my sanitized radius configuration so maybe you can see
something that I can't. This has worked well for years. There are 2 radius
servers with 10 radiusd processes behind a proxy. On Saturday one process
was repeately receiving the "Could not load EAP module Radius::EAP_"
On 09/13/2013 11:19 PM, Barry Ard wrote:
> I have noticed these messages in my radiator logs for EAP-PEAP handler
>
> Could not load EAP module Radius::EAP_: Can't locate Radius/EAP_.pm in
> @INC (@INC contains: /etc/radiator/hooks/ /etc/radiator/hooks .
> /etc/perl /usr/local/lib/perl/5.14.2 /us
Hi Group,
I have noticed these messages in my radiator logs for EAP-PEAP handler
Could not load EAP module Radius::EAP_: Can't locate Radius/EAP_.pm in @INC
(@INC contains: /etc/radiator/hooks/ /etc/radiator/hooks . /etc/perl
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
/
On Fri, 15 Jul 2011, Heikki Vatiainen wrote:
> On 07/15/2011 10:46 AM, Martin Burton wrote:
>
> I was just about to compose a reply to Jethro when I noticed your
> message.
>
> I agree on all points you have made and also suspect something is
> munging the messages.
Hi Heikki and Martin,
Tha
Hi,
> (As an aside, what do the numbers in the "Handling with EAP: code 2, 11,
> 76, 176" line each represent anyway?)
the joy of RADIATOR is you have the code. in EAP.pm theres this
"Handling with EAP: code $code, $identifier, $length, $type"
where $type is the EAP type/class - you've got so
On 07/15/2011 10:46 AM, Martin Burton wrote:
Hello Martin,
I was just about to compose a reply to Jethro when I noticed your message.
I agree on all points you have made and also suspect something is
munging the messages.
> If I'm reading the code correctly the values in the DEBUG are: packet
>
Hi Jethro,
If I'm reading the code correctly the values in the DEBUG are: packet
code (2=response), identifier(11), length(76) and method type(176)
A quick check of the IANA registered EAP types at
http://www.iana.org/assignments/eap-numbers/eap-numbers.xml shows no
entry for EAP method 176. Whic
In the last couple of days, for no particularly obvious reason, I've been
getting lots of this sort of stuff authenticating remote EAP users:
Thu Jul 14 20:04:40 2011: DEBUG: Handling with EAP: code 2, 11, 76, 176
Thu Jul 14 20:04:40 2011: DEBUG: Response type 176
Thu Jul 14 20:04:40 2011: ERR: C
