Date: Wed, 3 Sep 1997 08:48:23 -0500 (EST) From: Steve Ames <steve@ns1.cioe.com> To: spork@super-g.com, steve@ns1.cioe.com Cc: freebsd-isp@freebsd.org Subject: Re: Radius dumping core Message-ID: <199709031348.IAA03249@ns1.cioe.com>
next in thread | raw e-mail | index | archive | help
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
>
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709031348.IAA03249>