Hello Kailash -
On Wed, 09 Feb 2000, kailash wrote:
Hello Everybody
I am a ISP and being using radius from last 2 years,it is fabulous.Now from last
5 to 6 days I am facing a problem.My customers are complaining that after they
dial they sometimes they don't see the username and password
Hi!
Is it posible to store the entire radius accounting packet in a single sql blob
field like a comma or new-line separated list?
thanks.
Félix
__
DATAGRAMA SERVICIOS GLOBALES IP
C/ Acer 30
Hi,
Because we get garbage usernames, i've used the handler bit in the config file
(see below):
Handler User-Name = /\\x/
AuthBy FILE
Filename %D/reject-users
/AuthBy
/Handler
Handler
AuthByPolicy ContinueWhileIgnore
RewriteUsername tr/A-Z/a-z/
From the documentation, DupInterval is applied to the client, ie the
host sending the request, eventually an intermediate proxy.
From reading the Client.pm source code I see following :
$self-{RecentIdentifiers}-{$nas_id . $code}[$p-identifier]
$nas_id is there supposed to be the
Oh, I want to clarify that we're *not* on NT -- I'm using
Sun Solaris boxes (2.5.1 and 2.6) for RADIUS, sendmail, and
POP3 services.
At 08:17 AM 2/9/00 +0100, [EMAIL PROTECTED] wrote:
On Tue, Feb 08, 2000 at 06:53:30PM -0600, John Coy wrote:
use Radiator for dial-up authentication. I was
I believe Solaris 7 and 8 support ldap as a name service switch. Hence,
any system calls (getpwnam, getspnam, etc.) are passed to ldap and then to
anything else you've specified in /etc/nsswitch.conf
--
Aaron Holtz
ComNet
Hi Christophe,
My advice is to reduce the DupInterval to something like 2 seconds. It is
really only intended to catch genuine duplicate packets (ie packets sent along
duplicate parallel network paths, or from some other pathological network
problem). Its really not supposed to catch
Hello Robin -
On Thu, 10 Feb 2000, Robin Gruyters wrote:
Hi,
Because we get garbage usernames, i've used the handler bit in the config file
(see below):
Handler User-Name = /\\x/
AuthBy FILE
Filename %D/reject-users
/AuthBy
/Handler
Handler
