Thomas Fagart wrote:
The server where it is located has two IP interfaces and even worse on
one of the interface we're using IP aliasing :-)
I've notice that freeradius always use the same IP to proxy from inner
tunnel.
I know that I could use the listen directive in radiusd.conf (and
I install freeradius in the server its ip is 192.168.1.1.
In the server I have already do the radtest ,and the result is OK
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=11, length=20
I want to add a test authenticator host client. So I add something at
the end of my
syharash wrote:
My freeradius is set and working fine, the authentication is successful on a
windows XP machine on the wireless network. I am using Cisco Switches and
Ruckus Zone Director 1000 with Ruckus AP's. They are connected to the
switches on the trunk ports with all vlans allowed.
徐宇 wrote:
Should I do other things to finish it? I need to do the radtest in
the client(192.168.1.100) right? But there isn't a radtest command in
the client, Need I install some softwares in the client?
Yes, that's how computers work.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Thomas Fagart wrote:
The server where it is located has two IP interfaces and even worse on
one of the interface we're using IP aliasing :-)
I've notice that freeradius always use the same IP to proxy from inner
tunnel.
I know that I could use the listen directive in radiusd.conf (and that's
I install freeradius in the server its ip is 192.168.1.1.
In the server I have already do the radtest ,and the result is OK
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=11, length=20
I want to add a test authenticator host client. So I add something at
the end of my
On Sat, Apr 9, 2011 at 5:03 PM, 徐宇 xuyub...@gmail.com wrote:
I install freeradius in the server its ip is 192.168.1.1.
In the server I have already do the radtest ,and the result is OK
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=11, length=20
I want to add a test
On Fri, Apr 8, 2011 at 9:50 PM, u...@3.am wrote:
On my client's wifi network, we are authenticating staff users via
FreeRADIUS against the corporate LDAP database.
I've created a new SSID/WLAN with an IP pool that I've restricted through
router ACLs that we want to deploy for temporary guest
On 08/04/2011 08:54, Alan DeKok wrote:
Phil Mayers wrote:
+1 - In my experience it's necessary to cater for windows' weirdness
*first*. Most other clients have sane behaviours. I'm concerned about
the we didn't do much windows testing line...
Yup.
I've just pushed some changes to the
9 matches
Mail list logo
