auth_module libexec/mod_auth.so
Hope it will help you
--
Samuel Degrande LIFL - UMR8022 CNRS - INRIA Futurs - Bat M3
Phone: (33)3.28.77.85.30 USTL - Universite de Lille 1
Fax: (33)3.28.77.85.37 59655 VILLENEUVE D'ASCQ CEDEX - FRANCE
[CA certs: http://igc.services.cnrs.fr/CNRS
somewhere that precisely describes how the server chains things ?
But perhaps it's a big secret, a kind of graal that only
radius core developpers can touch ? :-) However, a public version could be
really helpfull...
--
Samuel Degrande LIFL - UMR8022 CNRS - INRIA Futurs - Bat M3
Phone: (33
' the authentication
protocol from EAP on the first radius server, and only send
user-name/user-password attributes to the central radius server ?
(i guess that my question is stupid, but I don't know how
to express it in the good way...)
thanks
--
Samuel Degrande LIFL - UMR8022 CNRS - INRIA
it's the problem ?)
Second question:
How to configure the A server so that if B rejects the request, then
A will check in a local user base (through pam) ?
As I said, I'm just perhaps too bad, and did not understand how all this
thing works, but please help me anyway :-)
Thanks.
--
Samuel
Alan DeKok wrote:
Samuel Degrande [EMAIL PROTECTED] wrote:
I don't find a way to add a NAS-Identifier value inside the proxied
request, so that B server could check it...
That's because the NAS didn't send it. FreeRADIUS doesn't add one,
so...
I tried:
username Proxy-To-Realm := realm
5 matches
Mail list logo