From owner-freebsd-stable Thu Nov 12 17:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27676 for freebsd-stable-outgoing; Thu, 12 Nov 1998 17:26:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (mh2.cts.com [209.68.192.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27671 for ; Thu, 12 Nov 1998 17:26:25 -0800 (PST) (envelope-from mdavis@cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id RAA21989 for ; Thu, 12 Nov 1998 17:26:06 -0800 (PST) Received: from davis (ion.cts.com [198.68.174.38]) by io.cts.com (8.8.8/8.8.8) with SMTP id RAA04128 for ; Thu, 12 Nov 1998 17:26:06 -0800 (PST) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: Subject: routed questions Date: Thu, 12 Nov 1998 17:26:05 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0707.2700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a 2.2.7-release system, routed randomly disappears (completely) or stays and stops listening to announcements, repeatedly. It should not do that at all, of course. Could it be due to anemic kernel parameters? Or is this a known problem with -release? routed is being run with these options: router_enable="YES" # Set to YES to enable a routing daemon. router="routed" # Name of routing daemon to use if enabled. router_flags="-P ripv2,rdisc_interval=45,no_rdisc_adv" # Flags for routing daem On a somewhat related note, running routed on a network that has more than one router to/from the Internet often causes arp errors about addresses being moved. This is really just people who may have an ingress router that differs from the egress router. Is there some routed option that turns off these syslog messages? Or perhaps it can be done with syslog.conf in some way? And yet on another related note, often routed coughs up "unexepect interface" and "discard" errors. Comments on any of these? --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message