Ryan A. Krenzischek wrote:
Greetings!
I am at a road block here. I know setting up WPA2 Enterprise
PEAPv0/EAP-MSCHAPv2 / 802.1X should be simple. It just isn't working!
Perhaps I am suffering from green screen syndrome :)
I have followed directions from:
On 01/04/2010, at 1:44 PM, Matt Harlum wrote:
On 01/04/2010, at 7:39 AM, Bruno Kremel wrote:
On Wednesday 31 March 2010 21:28:48 Alan DeKok wrote:
What should be there?
Beacuse I don't know I am using Daloradius web interafce for adding data to
database, so I just loaded default
2010/4/1 Matt Harlum m...@cactuar.net:
On 01/04/2010, at 1:44 PM, Matt Harlum wrote:
On 01/04/2010, at 7:39 AM, Bruno Kremel wrote:
On Wednesday 31 March 2010 21:28:48 Alan DeKok wrote:
What should be there?
Beacuse I don't know I am using Daloradius web interafce for adding data to
On 01/04/2010, at 8:40 PM, Bruno Kremel wrote:
2010/4/1 Matt Harlum m...@cactuar.net:
On 01/04/2010, at 1:44 PM, Matt Harlum wrote:
On 01/04/2010, at 7:39 AM, Bruno Kremel wrote:
On Wednesday 31 March 2010 21:28:48 Alan DeKok wrote:
What should be there?
Beacuse I don't know I am
Bruno Kremel wrote:
Sending Access-Challenge of id 0 to 192.168.3.1 port 1320
EAP-Message = 0x010c00061900
Message-Authenticator = 0x
State = 0x53b1704557bd694fbe3359243d2a2638
Finished request 40.
Going to the next request
Waking up
Hi ,I am happing problem that I couldn't resolve alone. If anyone in the list
could help me will be appreciated.
I have access point EnGenius 2610 and I run freeradius under RHEL5.RHEL5 have
two ethernet card, eth0 : 192.168.1.4 to Internet, eth1 to Wifi Client with IP
192.168.0.1 (Client is
2010/4/1 Alan DeKok al...@deployingradius.com:
Bruno Kremel wrote:
Sending Access-Challenge of id 0 to 192.168.3.1 port 1320
EAP-Message = 0x010c00061900
Message-Authenticator = 0x
State = 0x53b1704557bd694fbe3359243d2a2638
Finished
Hi everybody,
I'm beginner with FreeRadius and I'd like to know where can I use a
vendor specific attribute for my Redback router (in which
configuration file).
The dictionary is in /usr/share/freeradius/dictionary.redback and
loaded when FreeRadius starts.
When is try to use Context-Name =
Bruno Kremel wrote:
I am posting full log with first is radtest accepted and others are
failde login from wifi client with 2 different accounts...
FreeRADIUS Version 2.0.4, for host i486-pc-linux-gnu, built on Mar 29
2010 at 15:58:09
You should probably upgrade to 2.1.8. It has a lot of
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the access-req
packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to the
IP address other than the src-ip of the NAS that is used in reqular
FreeRadius
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
One of NAS is on the other side of a load balancer, source IP is not the
same as NAS-IP.
John
This message is confidential to Prodea Systems, Inc unless otherwise
On 04/01/2010 05:39 PM, Marlon Duksa wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to
the IP address other than the src-ip of the NAS that is
Marlon Duksa wrote:
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
Many. There is *no* requirement in RADIUS that they be identical.
When a packet is proxied, the NAS-IP-Address stays the same, but the
source IP changes.
Alan
--On 01 April 2010 09:39 -0700 Marlon Duksa mdu...@gmail.com wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the scr-IP of the
access-req packet should not be the same?
If the NAS-IP is configurable in the NAS, then the NAS-IP can be set to
the IP address other than the
{...}
++[preprocess] returns ok
[auth_log] expand:
/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -
/var/log/radius/radacct/128.146.XXX.XXX/auth-detail-20100401
[auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d
expands to /var/log/radius/radacct/128.146
Plenty of reasons - but one you won't have control over even in CoA is
that it could be proxied.
The NAS-IPAddress is used in the CoA request packet to tell the NAS
which client should receive the packet.
Marlon Duksa wrote:
Hi everyone -
Can anyone think of a reason why the NAS-IP and the
16 matches
Mail list logo
