Subject: routed behavior
To: None <netbsd-users@netbsd.org>
From: Andrew Brown <atatat@atatdot.net>
List: netbsd-users
Date: 08/14/2000 18:59:50
my machine's (i386/1.3.3 and 1.4.1) environment is moving from one of
a plain old static route to one of two default routes controlled by
routed.  routed should be listening for idrp updates and change my
default route appropriately.  but i've not ever actually gotten that
far with it yet.

i killed routed (and undid the damage) after a few seconds when i
first started it, since it screwed up my routing table very badly.  my
routing table used to look like this:

# netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            198.67.15.15       UGS         3    53449      -  de0
127.0.0.1          127.0.0.1          UH         17       29      -  lo0
198.67.15          link#1             UC          0        0      -  de0
198.67.15.20       00:00:c0:65:9a:e3  UHL         1   709836      -  lo0
198.67.15.21       127.0.0.1          UGHS        0        7      -  lo0 =>
198.67.15.21/32    link#1             UC          0        0      -  de0
198.67.15.22       127.0.0.1          UGHS        0        0      -  lo0 =>
198.67.15.22/32    link#1             UC          0        0      -  de0
...

but after routed starts up, it looks like this:

# netstat -rn | head -16
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            198.67.15.15       UGS         9    53883      -  de0
127.0.0.1          127.0.0.1          UH          1       29      -  lo0
198.67.15          link#1             UC          0        0      -  de0
198.67.15.20       00:00:c0:65:9a:e3  UHL         1   709856      -  lo0
198.67.15.21       198.67.15.21       UGHS        1        7      -  de0 =>
198.67.15.21/32    link#1             UC          0        0      -  de0
198.67.15.22       198.67.15.22       UGHS        1        0      -  de0 =>
198.67.15.22/32    link#1             UC          0        0      -  de0
...

which is *entirely* suboptimal.  it leaves my machine with no
connectivity to itself, except via 127.0.0.1.

is this a "known bug", a "feature", or "something which upgrading will
eliminate"?

ps - routed seems also not to be seeing any of the multicast icmp idrp
messages, but i can see them with tcpdump and the headers all look
okay to me.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."