Olivier Bilodeau wrote:
http://wiki.freeradius.org/Rlm_perl#Logging refers to:
0 - Debug
1 - Auth
Those are wrong. See src/include/radiusd.h, L_DBG, etc.
I've fixed the Wiki.
I expected Debug not to go out in radius.log and Auth to do since I
specified Auth to yes in radiusd.conf.
Hello all,
I am implementing Free Radius to authenticate DHCP Requests with Option82. I
have configured DHCP Relay Agent, DHCP Snooping in CISCO Switch and DHCP
Server. Now i have to configure RADIUS for option82.
Please help me to configure RADIUS for DHCP option82. Also i am not clear who
On Wed, Feb 22, 2012 at 3:16 PM, sachin.sha...@wipro.com wrote:
Hello all,
I am implementing Free Radius to authenticate DHCP Requests with Option82.
I have configured DHCP Relay Agent, DHCP Snooping in CISCO Switch and DHCP
Server. Now i have to configure RADIUS for option82.
Are you
sachin.sha...@wipro.com wrote:
I am implementing Free Radius to authenticate DHCP Requests with
Option82. I have configured DHCP Relay Agent, DHCP Snooping in CISCO
Switch and DHCP Server. Now i have to configure RADIUS for option82.
What does that mean?
It's like saying configure a web
On 02/21/2012 11:04 PM, Tim White wrote:
Following on from my previous email, I've checked an x86 machine as
well, and get the same behaviour.
I should hope so; SQL is not architecture specific!
Your original solution was correct as far as I could see; if there's any
chance a column might be
Hello Fajar/Alan
Thanks for u r quick Responses !!
I already configured DHCP Server that handles option 82 of DHCP Requests. But
new to RADIUS stuff. For security reasons, We want to introduce radius so DHCP
Offer is to be made only to authenticated clients.
I just need a idea to have
sachin.sha...@wipro.com wrote:
I already configured DHCP Server that handles option 82 of DHCP Requests. But
new to RADIUS stuff. For security reasons, We want to introduce radius so
DHCP Offer is to be made only to authenticated clients.
Ah. That isn't a common configuration. But it
On 2012/02/22 01:10 PM, Alan DeKok wrote:
Yes.
If you use FreeRADIUS for both RADIUS and DHCP, you can track user
status in a database. When you receive a RADIUS packet, update the
database. When you receive a DHCP packet, query the database.
Traditional DHCP servers (i.e. ISC)
On Wed, Feb 22, 2012 at 7:03 PM, Johan Meiring
jmeir...@pcservices.co.za wrote:
Another option which we use very successfully is a Mikrotik DHCP server.
It can talk to Freeradius.
http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server
It works well.
Good documentation.
So basically the dhcp
Hi
Can you tell me something about performances?
I'm using Mtik as NAS for PPPoE users and 500-600 online users per
server is optimum according to my experiences (Quad core server, 2GB
RAM,...).
ISC DHCP works very well for 6000 users and the same number of cable
modems but I'm not sure is
Marinko Tarlać wrote:
Can you tell me something about performances?
It all depends on the DB, because that's where IPs are stored.
For a normal database, 1000 packets/s should be possible.
I'm using Mtik as NAS for PPPoE users and 500-600 online users per
server is optimum according to
No No, you didn't understand me...
Mtik is installed on the server (HP ML3xx series) and the optimum is
500-600 online PPPoE users... I achieved 1100 online PPPoE users per
Mikrotik but the CPU load was always to high and the packet loss was to
high (1-2%). The problem is visible because the
Hello again,
We're piloting RadSec as a federation server uplink. They use Radiator. When
we first attempted to connect we'd get
a Received packet will be too large! carp from main/tls.c. They checked on
their end and say they have no fragment
size option for RadSec TLS connections, only
Freeradius Dear users, good afternoon!
I have a radius server using a mysql database authentication by performing
login and mac address working very well.
Now I need to implement a new plan of authentication where some users can only
connect at a certain time of day (eg Monday to Friday
I seem to be having a hardtime setting up FreeRADIUS to work with my Astaro
firewall.
First, in radiusd.conf I have left most of the configurations the same only
made a few small ones such as the port for:
listen {
type = auth
ipaddr = *
port = 1812 (instead of the default 0)
}
In
Hi,
port = 1812 (instead of the default 0)
doesnt matter - it'll use 1812 and not 0 - read from /etc/services
client ASG {
ipaddr = 192.168.***.***
secret = my secret
if the secret really does have spaces in it, then you need to ensure its
enclosed in quotes my secret
In
Hi,
We're piloting RadSec as a federation server uplink. They use Radiator.
When we first attempted to connect we'd get
a Received packet will be too large! carp from main/tls.c. They checked on
their end and say they have no fragment
size option for RadSec TLS connections, only for
NAS-Port = 242
+- entering group authorize {...}
++[preprocess] returns ok
[auth_log] expand:
/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -
/var/log/radius/radacct/127.0.0.1/auth-detail-20120222
[auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d
Hi,
We're trying to get a GlobalSign issued wildcard CA to work on our radius
server that is authenticating users via PEAP/MSCHAPv2 to Active Directory.
We're good on Android devices and iOS devices. With Windows 7 (SP1) we're
fine as long as we leave validate server certificate
On Wed, Feb 22, 2012 at 04:11:00PM -0600, John Dunning wrote:
devices. With Windows 7 (SP1) we're fine as long as we leave
validate server certificate unchecked. As soon as we enable
So your general server config is good.
(1.3.6.1.5.5.7.3.1) Extended Key usage. The cert listed in the
Hi,
We're piloting RadSec as a federation server uplink. They use Radiator. When
we first attempted to connect we'd get
a Received packet will be too large! carp from main/tls.c. They checked on
their end and say they have no fragment
size option for RadSec TLS connections, only for
21 matches
Mail list logo
