I would have done this ages ago if I knew where to find a more comprehensive
manual explaining it all, rather than relying on bits of info scattered in
thousand different places. The freeRADIUS wiki isn't terribly helpful either
- this -
Hi,
Sending Access-Request of id 13 to 127.0.0.1 port 1812
User-Name = usertest
NAS-IP-Address = 10.1.1.28
NAS-Port = 0
MS-CHAP-Challenge = 0x7effa6d1eaf313a9
MS-CHAP-Response =
once again, you are looking at trivial client output. look at the
I was able to run the server by changing the port in innertunnel to
18120 But still i am getting the following error
Ignoring EAP-Type/tls because we do not have OpenSSL support.
Ignoring EAP-Type/ttls because we do not have OpenSSL support.
Ignoring EAP-Type/peap because we do not have OpenSSL
Bhanu Vegesna wrote:
I was able to run the server by changing the port in innertunnel to
18120 But still i am getting the following error
Ignoring EAP-Type/tls because we do not have OpenSSL support.
Ignoring EAP-Type/ttls because we do not have OpenSSL support.
Ignoring EAP-Type/peap
On Mon, Nov 28, 2011 at 4:27 PM, Bhanu Vegesna bhanu.vege...@gmail.com wrote:
I was able to run the server by changing the port in innertunnel to
18120 But still i am getting the following error
Ignoring EAP-Type/tls because we do not have OpenSSL support.
Did you read the message?
The
Hello,
I have a setup wich Is a follow:
NASes FREERADIUS Auth+live acct
FREERADIUS Acct only
In this setup, users connect to NASes, which authenticate them against
the front freeradius (Auth + live acct). The front freeradius, maintain
a db of the connected
Hi,
I was able to run the server by changing the port in innertunnel to
18120 But still i am getting the following error
Ignoring EAP-Type/tls because we do not have OpenSSL support.
Ignoring EAP-Type/ttls because we do not have OpenSSL support.
Ignoring EAP-Type/peap because we do not have
FYI: This is not a perl script. It’s a compiled C program. Just its
extension is .pl!
For more information:
This is my module config:
exec netbill_pre_auth{
wait = yes
program = /etc/netbill/preauth.pl
input_pairs = request
On Mon, Nov 28, 2011 at 6:51 PM, Ali Majdzadeh ali.majdza...@gmail.com wrote:
Also plz note that auth.pl forks another exec program per authenticated user
(named calc) and will live till user stopped. So if I’ve 20.000 online
users, I’ve also 20.000 calc process.
The most obvious question is
Ali Majdzadeh wrote:
So I need to use with exec-wait becos the external programs need to wait
util authentication/authorization/accounting done!
That is how exec-wait works.
Also plz note that auth.pl forks another exec program
per authenticated user (named calc) and will live till user
Alexandre Chapellon wrote:
This work as epected for most of my NASes. Unfortunately, i have some
NASes that are behind a satelite link, which is a very unreliable link
with regular packets loss. UDP retramission of packet make the systems
work even with that kind of link, but I have one
Dear all
I try to set freeradius proxy and put my server
my dns server and my isp dns is ok.
on server startup after reboot freeradius not start and show error
Error: /etc/freeradius/proxy.conf[667]: Failed looking up hostname
radius.easyzonecorp.net.
but when i try to start by hand
Hi,
on server startup after reboot freeradius not start and show error
Error: /etc/freeradius/proxy.conf[667]: Failed looking up hostname
radius.easyzonecorp.net.
but when i try to start by hand /etc/init.d/freeradius start, it 's OK.
Why freeradius fail to looking up hostname only on
Arran Cudbard-Bell a.cudba...@freeradius.org writes:
The wiki does NOT require you to login to view content, that's the
whole point of the new wiki. You're trying to access a page that
doesn't exist. If you had even bothered to read the URL you'd have
seen that it contained the word create,
Hi,
I was successful to install Freeradius 2.1.10 and basic PAP authentication,
Authentication against Active Directory was successful when I installed
Freeradius for first time. But I had to deinstall and reinstall Freeradius
2.1.10 again due to some missing libraries. I am following the same
Hi Fajar,
Thanks so much for replying.
The debug log for local test against AD is attached:
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on command file /var/run/radiusd/radiusd.sock
Listening on proxy address * port 1814
Ready to process
suggestme wrote:
I was successful to install Freeradius 2.1.10
Upgrade to 2.1.12.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Tue, Nov 29, 2011 at 4:03 AM, Vikash Gounder
vikash.goun...@acu.edu.au wrote:
Hi Fajar,
Thanks so much for replying.
The debug log for local test against AD is attached:
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on command
So in this case what changes do I need to make in order for it to work.
Sorry am bit lost right now.
Thanks and appreciate it.
Sent from my iPhone
On 29/11/2011, at 10:22 AM, Fajar A. Nugraha l...@fajar.net wrote:
On Tue, Nov 29, 2011 at 4:03 AM, Vikash Gounder
vikash.goun...@acu.edu.au
On Tue, Nov 29, 2011 at 6:29 AM, Vikash Gounder
vikash.goun...@acu.edu.au wrote:
So in this case what changes do I need to make in order for it to work.
Sorry am bit lost right now.
http://deployingradius.com/documents/configuration/active_directory.html
--
Fajar
-
List
Le 28/11/2011 13:53, Alan DeKok a écrit :
Alexandre Chapellon wrote:
This work as epected for most of my NASes. Unfortunately, i have some
NASes that are behind a satelite link, which is a very unreliable link
with regular packets loss. UDP retramission of packet make the systems
work even
21 matches
Mail list logo