From owner-freebsd-bugs Wed Jun 6 8: 0: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0C69037B403 for ; Wed, 6 Jun 2001 08:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f56F02P32978; Wed, 6 Jun 2001 08:00:03 -0700 (PDT) (envelope-from gnats) Date: Wed, 6 Jun 2001 08:00:03 -0700 (PDT) Message-Id: <200106061500.f56F02P32978@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ruslan Ermilov Subject: Re: kern/27890: FreeBSD not always seems to take the best route Reply-To: Ruslan Ermilov Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/27890; it has been noted by GNATS. From: Ruslan Ermilov To: Andre Albsmeier Cc: bug-followup@FreeBSD.org Subject: Re: kern/27890: FreeBSD not always seems to take the best route Date: Wed, 6 Jun 2001 17:56:15 +0300 On Wed, Jun 06, 2001 at 04:29:33PM +0200, Andre Albsmeier wrote: > On Wed, 06-Jun-2001 at 15:32:05 +0300, Ruslan Ermilov wrote: > > On Wed, Jun 06, 2001 at 12:29:04PM +0200, Andre Albsmeier wrote: > > > > : 127.0.0.1 127.0.0.1 UH 1 6 lo0 > > > > : 192.168.1 link#1 UC 4 0 rl0 => > > > > : 192.168.2 192.168.1.2 UGSc 1 3 rl0 > > > > > > > > The refcount on 192.168.2 route has grown to 1, indicating that the > > > > UDP socket now holds on this route. The `Use' count of 3 corresponds > > > > to our three UDP datagrams (ping4, ping5, and ping6). > > > > > > > > Could you please repeat these steps in your environment, and try to > > > > detect where it behaved differently in your case. > > > > > > It doesn't behave differently, that's interesting. May I ask you to > > > try it using syslogd? > > > > > > - Let host C log to host S (with the route installed). > > > - Watch C's messages appear on S. > > > - Delete C's route to S (via router 2) > > > - Let host C log again (run tcpdump on router 1 to see the packets come in) > > > - Install the route to S (via router 2) again on C > > > - Log more stuff. If you don't see the packets go into router 1 anymore > > > I am really lost... > > > > > Yes, I have reproduced the problem here. My test misses one step. > > Hmm, I just wonder why syslogd behaves differently... > Because my test missed one step: the route to S through router 2 should exist initially to reproduce this with netcat(1). You then send some data, delete the route, again send data so that the "default" route gets cached, and install the route to S again. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message