From owner-freebsd-net@FreeBSD.ORG  Wed Sep 24 00:28:09 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E6E3116A4B3
	for <net@freebsd.org>; Wed, 24 Sep 2003 00:28:09 -0700 (PDT)
Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su
	[213.184.65.80])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1F01243F3F
	for <net@freebsd.org>; Wed, 24 Sep 2003 00:28:08 -0700 (PDT)
	(envelope-from eugen@kuzbass.ru)
Received: from kuzbass.ru (kost [213.184.65.82])h8O7S3Tr015494
	for <net@freebsd.org>; Wed, 24 Sep 2003 15:28:05 +0800 (KRAST)
	(envelope-from eugen@kuzbass.ru)
Message-ID: <3F71471E.B92E7DF9@kuzbass.ru>
Date: Wed, 24 Sep 2003 15:26:22 +0800
From: Eugene Grosbein <eugen@kuzbass.ru>
Organization: SVZServ
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: net@freebsd.org
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Subject: routed(8) strangeness in 4.8-STABLE
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2003 07:28:10 -0000

Hi!

I run routed(8) on a multihomed machine (3 NICs up and running).
In that cases routed will not inject route from its RIP trable
into the kernel (kernel does not have more general route
through the same inteface)? 

For example, consider route to 172.20.11.1/32:

# rtquery -n | fgrep 172.20.11
  172.20.11.16/29    metric  1           
  172.20.11.0/27     metric  3            nhop=172.20.15.66   

That's right, RIPv2 has the route.

# route -n get 172.20.15.66
route to: 172.20.15.66
destination: 172.20.15.66
  interface: rl1
      flags: <UP,HOST,DONE,LLINFO,WASCLONED>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu    
expire
       0         0         0         0         0         0      1500       611 

And gateway is reachable.

# route -n get 172.20.11.1
   route to: 172.20.11.1
destination: default
       mask: default
    gateway: 172.20.2.101
  interface: fxp0
      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu    
expire
       0         0         0         0         0         0      1500         0 

But kernel does not have specific route and uses default that is wrong.
I run it as routed -s, here is my /etc/gateways:

ripv2
rdisc_interval=45
no_ag
no_super_ag
redirect_ok

Eugene Grosbein