From owner-freebsd-stable Thu Jul 11 7:30:42 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 945A537B400 for ; Thu, 11 Jul 2002 07:30:36 -0700 (PDT) Received: from obsidian.sentex.ca (obsidian.sentex.ca [64.7.128.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08EB543E52 for ; Thu, 11 Jul 2002 07:30:36 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by obsidian.sentex.ca (8.12.5/8.12.4) with ESMTP id g6BEUYmW014265; Thu, 11 Jul 2002 10:30:34 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20020711102924.036b6230@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 11 Jul 2002 10:34:31 -0400 To: Mark Hennessy , From: Mike Tancsa Subject: Re: Cistron 1.6.6 freeze-ups (fwd) In-Reply-To: <20020711101547.A89350-100000@earl-grey.cloud9.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (obsidian/20020220) 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 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