From owner-freebsd-current Sat Jun 8 13:37:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15162 for current-outgoing; Sat, 8 Jun 1996 13:37:41 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15147; Sat, 8 Jun 1996 13:37:36 -0700 (PDT) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id NAA06737; Sat, 8 Jun 1996 13:37:01 -0700 (PDT) Message-Id: <199606082037.NAA06737@precipice.shockwave.com> To: Garrett Wollman cc: "Jordan K. Hubbard" , current@freefall.freebsd.org Subject: Re: As of 960608, routed now complains bitterly.. In-reply-to: Your message of "Sat, 08 Jun 1996 14:52:48 EDT." <9606081852.AA02677@halloran-eldar.lcs.mit.edu> Date: Sat, 08 Jun 1996 13:37:00 -0700 From: Paul Traina Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Garrett Wollman Subject: As of 960608, routed now complains bitterly.. <>freebsd.org> said: > Messages of the form: > Jun 8 01:10:39 time routed[57]: rnh_addaddr() failed for 204.216.27.0 mask >>=0xfffffff0 > Jun 8 01:11:09 time routed[57]: rnh_addaddr() failed for 204.216.27.0 mask >>=0xfffffff0 > Spew where no messages spewed in former times. Just FYI.. This means that your netmasks are not configured correctly, either on the host, or a router to that network, or both. It happens when routed is listening to RIP packets labeled with one netmask on an interface which is locally configured for another. For example, for a while I had one router configured for 255.255.255.0 and one for 255.255.240.0 (both on the same subnet), and it complained bitterly until I fixed the configurations to agree. How are RIPv1 packets labeled with a netmask? You're not telling me that the new routed defaults to v2, are you? :-( grrr... Curious, Paul