From owner-freebsd-isp  Wed Sep  3 06:48:27 1997
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA12885
          for isp-outgoing; Wed, 3 Sep 1997 06:48:27 -0700 (PDT)
Received: from ns1.cioe.com (steve@ns1.cioe.com [204.120.165.37])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12880
          for <freebsd-isp@freebsd.org>; Wed, 3 Sep 1997 06:48:23 -0700 (PDT)
Received: (from steve@localhost)
	by ns1.cioe.com (8.8.5/8.8.5) id IAA03249;
	Wed, 3 Sep 1997 08:48:23 -0500 (EST)
Date: Wed, 3 Sep 1997 08:48:23 -0500 (EST)
From: Steve Ames <steve@ns1.cioe.com>
Message-Id: <199709031348.IAA03249@ns1.cioe.com>
To: spork@super-g.com, steve@ns1.cioe.com
Subject: Re: Radius dumping core
Cc: freebsd-isp@freebsd.org
Sender: owner-freebsd-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Actually... I managed to solve that particular problem by changining
the 'users' file. Additionally in the 2.2-STABLE code the ports compiles
apparently use /etc/make.conf and the CCFLAGS that most people use for
building the world cause nasty things to happen to radius. I got an email
from William Bulley <web@merit.edu> suggesting a compile with just the
'-g' option and that radius seems a lot more stable (days up instead of
hours or minutes).

The changes I made to the users file basically changed it to look like
this:

DEFAULT Authentication-Type = Realm,
        Service-Type = Framed,
        Framed-Protocol = PPP,
        Framed-IP-Netmask = 255.255.255.255,
        Framed-Routing = None,
        Framed-MTU = 1500,
        Framed-Compression = Van-Jacobson-TCP-IP
#       Filter-Id = "unlim"

I don't really remember how that differs from the original/default. But
it works. Might have been just commenting out the Filter-Id...

Good luck!

							-STeve

> I just came across the message below while looking for info in the mail
> archives about spontaneous radiusd crashes, and I'm curious if anyone had
> found a resolution.  We're running into a similar problem (the USR stuff
> is still being beta tested) on a 2.1.7-stable machine.  radiusd catches a
> sig 11 and dies.  Looking at the core it appeared to be during a failed
> authentication.  The same machine runs primary nameservice and acts as a
> mail hub, and this is so far the only program that sig 11s.
>
> Does anyone have a preference on which radius dist to use with a USR TCH?
>
> Charles
>
>
> Date:      Thu, 30 Jan 1997 07:54:03 -0500 (EST)
> From:      Steve Ames <steve@vic.cioe.com>
> To:        allenh@wtrt.net, freebsd-isp@FreeBSD.ORG, steve@vic.cioe.com
> Sender:    owner-isp@FreeBSD.ORG
> Subject:   Re: USR Total Control
>
> >>Does anyone have a FreeBSD radius port that will work with the USR Total
> >>Control system? I've installed the one in ports-current but it crashes as
> >>soon as I attempt to authenticate from the USR onto it...
> >> I am using the radius from ports, on a 2.1.6-Release box, with a USR Total
> > Control system.  I have not had the problems you describe.  You might want
> > to check the logfile to see if it tells why radius crashed.
>
> /var/log/messages is claiming a sig 11 and core dump... Now my first
> thought
> was 'bad memory chip', but this is the only application that will dump
> period. And I've got plenty else running...
>
>                                                 -Steve
>
>
>
>