From owner-freebsd-questions Wed Jun 24 14:51:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09057 for freebsd-questions-outgoing; Wed, 24 Jun 1998 14:51:33 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from m5.columbus.rr.com (m5.columbus.rr.com [204.210.252.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09007 for ; Wed, 24 Jun 1998 14:51:08 -0700 (PDT) (envelope-from radams@siscom.net) Received: from wize1 (alc239023.columbus.rr.com [204.210.239.23]) by m5.columbus.rr.com (8.8.8/8.8.8) with SMTP id RAA05641 for ; Wed, 24 Jun 1998 17:50:58 -0400 (EDT) Message-ID: <05d201bd9fba$2bec93e0$17efd2cc@wize1.columbus.rr.com> From: "Robert Adams" To: Subject: [FBSD & OSPF w/ GateD] Date: Wed, 24 Jun 1998 17:50:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone, I'm trying to get GateD up and running on a fresh 2.6 install. From what I can tell I'm seeing the OSPF announcements from the other eq.. but I'm getting this in my /var/log/gated.log Jun 24 21:59:26 OSPF RECV 209.57.241.249 -> 224.0.0.6: IP: bad destination Jun 24 21:59:26 OSPF RECV 209.57.241.250 -> 224.0.0.5: IP: bad destination Jun 24 21:59:26 OSPF RECV 209.57.241.252 -> 224.0.0.5: IP: bad destination I do a netstat -nr and notice the following.. 224.0.0.5 127.0.0.1 UH 1 378957 lo0 224.0.0.6 127.0.0.1 UH 1 2 lo0 Anyone have a idea what it's trying to do here? And how to go about fixing it? -Jason --- Robert J. Adams radams@siscom.net http://www.siscom.net Looking to outsource news? http://www.newshosting.com SISCOM Network Administration - President, SISCOM Inc. Phone: 888-4-SISCOM 937-222-8150 FAX: 937-222-8153 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message