Hi All,
I installed freeRADIUS 1.0.5 recently, and configured the server as described
in the documentation files. I configured it (freeRADIUS) to accept incoming
authentication requests from a WLAN AP (10.128.253.122). (Thanks for everyone
who helped me throughout.)
Then, using the
Hi again,
How I can test IPv6 Freeradius authentication?
You know any IPv6 RADIUS client to interact with Freeradius and perform an
IPv6 authentication?
In IPv4 I find many clients, but to IPv6, I don't found any clients yet.
Please reply to me where I can get the client used to test CVS
I have upgrade my libs, but when execute dpkg-buildpackage -uc
-b(under root privilege), some error show out:
.
dpkg-buildpackage: source maintainer is Paul Hampson [EMAIL PROTECTED]
dpkg-buildpackage: host architecture is i386
debian/rules clean
dh_testdir
rm -f stamp-build
Hello.
Fist, I would like to apologize if my question is really too simple,
but I think that I don't exactly understand the configuration philosophy
of freeradius.
I did configure one radius server (A) to proxy incoming requests to an other
radius server (B, this later one using pam).
First
darkblue wrote:
I have upgrade my libs, but when execute dpkg-buildpackage -uc
-b(under root privilege), some error show out:
.
/bin/bash: line 1: dpatch: command not found
make: *** [unpatch] Error 127
any idea?
apt-get install dpatch
--
Nicolas Baradakis
-
List
Paulo Alexandre Caceres Ferreira wrote:
How I can test IPv6 Freeradius authentication?
You know any IPv6 RADIUS client to interact with Freeradius and perform an
IPv6 authentication?
There is a program called radclient in the FreeRADIUS source tree.
--
Nicolas Baradakis
-
List
Hi Again,
This email refers to the earlier email sent with the subject EAP/TLS
Configuration.
After having some trouble with the Windows XP and freeRADIUS, I was able to
connect to the AP. But, in the configuration (Windows XP), I removed the check
mark at 'Validate Server Certificate'.
On Friday 02 December 2005 22:53, Madhuraka Godahewa wrote:
After having some trouble with the Windows XP and freeRADIUS, I was able to
connect to the AP. But, in the configuration (Windows XP), I removed the
check mark at 'Validate Server Certificate'. Then, suddenly, it started
working.
thanks
I could not wait to complie from source tarball.
I will try the build deb some time later, anyway, thanks very much.
2005/12/2, Nicolas Baradakis [EMAIL PROTECTED]:
darkblue wrote:
I have upgrade my libs, but when execute dpkg-buildpackage -uc
-b(under root privilege), some error
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Dusty Doris
Sent: November 30, 2005 7:16 AM
To: FreeRadius users mailing list
Subject: RE: Freeradius How to integrate Active Directory
and return group attribute to VPN Concentrator
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, NAS-Identifier := id
We were able to move past this particular problem. For anyone who may
have a similar issue
Port 512 (tcpudp for EZEC service) need to be allowed in addition to
the standard 137-139, 445, 389. So if you are running TCP wrappers or
ip tables make certain it is allowed
cheers
I am considering use of a CA-signed SSL certificate.
Comodo (instantssl.com) offers an Intranet SSL
certificate good on a single, internal host. All of
their documentation refers to set up with a web server
or for email verification. Would it also work with FR?
There signed certificates are
On Wed, 30 Nov 2005, Alhagie Puye wrote:
Ok, So I played around some more with the settings.
Actually group and groupofnames are not correct attributes for user.
It is supposed to be memberof. So I changed line in ldap.attrmap to
look like:
replyItem Class
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 :=
I did configure one radius server (A) to proxy incoming requests to an other
radius server (B, this later one using pam).
First question:
I don't find a way to add a NAS-Identifier value inside the proxied
request, so that B server could check it...
preproxy_users will do this for you.
How
OK, here is the situation. I have successfully configured
RADIUS to authenticate/authorize NAS requests from my Cisco gear so long as the
user Auth-Type= System. I have also managed to get Samba working
and have joined the radius server to the AD realm in question. This is
confirmed
Well, most of our email accounts are in a different organizational unit,
and they use posixAccount (so based off of uid). However, our radius
organizational unit is separate ... and I'm now using type account with
cn's. You're saying this is ok?
Its probably fine.
The only reason I was
Alhagie Puye - Network Engineer
Datawave Group of Companies
(604)295-1817
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Dusty Doris
Sent: December 2, 2005 10:11 AM
To: FreeRadius users mailing list
Subject: RE: Freeradius How to integrate
I get acct info for my local nas, but not getting acct info on visp
authentication? I've just upgraded to v1.0.5, but no difference. What
does it take to get the acct info for visp authentications?
**
Computer problems? ...
hey, guys
I have built up the whole environment, very close to success, but still have a problem when the suppliant create tls tunnel with radius server, the following is the log:
rlm_eap: Request found, released from the list rlm_eap: EAP/peap rlm_eap: processing type peap rlm_eap_peap:
21 matches
Mail list logo