From owner-freebsd-stable Sat Jul 13 9:12:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC77A37B400 for ; Sat, 13 Jul 2002 09:12:53 -0700 (PDT) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 708B943E5E for ; Sat, 13 Jul 2002 09:12:53 -0700 (PDT) (envelope-from mark@cloud9.net) Received: from earl-grey.cloud9.net (earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id 046A028FD9; Sat, 13 Jul 2002 12:12:53 -0400 (EDT) Date: Sat, 13 Jul 2002 12:12:52 -0400 (EDT) From: Mark Hennessy To: Mike Tancsa Cc: Subject: Re: Cistron 1.6.6 freeze-ups (fwd) In-Reply-To: <5.1.0.14.0.20020711102924.036b6230@marble.sentex.ca> Message-ID: <20020713121155.Y83657-100000@earl-grey.cloud9.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Even with the specification of the interface and port, the problem persists. Is there anything else to try? -- Mark P. Hennessy mark@cloud9.net On Thu, 11 Jul 2002, Mike Tancsa wrote: > Date: Thu, 11 Jul 2002 10:34:31 -0400 > From: Mike Tancsa > To: Mark Hennessy , freebsd-stable@FreeBSD.ORG > Subject: Re: Cistron 1.6.6 freeze-ups (fwd) > > At 10:21 AM 11/07/2002 -0400, Mark Hennessy wrote: > >Hi all. I'm using FreeBSD 4.5 RELEASE, and I was wondering if any of the > >following message makes sense. > > > > > >This is an interesting number. Apparently the kernel receives the > >packets allright, but doesn't pass them on to Cistron for whatever > >reason. > > > >It looks like you have a FreeBSD bug...? > > > There are a good number of people who run Cistron RADIUS on > FreeBSD. Rather than tracing obscure (possibly nonexistent) kernel bugs, I > would look first for the more common problems. Typically, on machines with > more than one interface (logical or physical) source addresses come into play. > > Start up radiusd and force the bind address to be the one you expect (also > do the port as this can be a problem as well since there are 2 'standards') > > e.g. if you use RADIUS on port 1645 (instead of 1812) and config the > clients to expect it on 192.168.1.43, start up radiusd as so. > > radiusd -i 192.168.1.43 -p 1645 > > If you still see problems, > add the -x and run it in debug mode and see if there are any messages. > > ---Mike > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message