Has anyone else seen a problem where "route add foo bar" will choose an
interface which cannot reach bar?  For instance, we have le0 configured
to reach 192.129.84.0-15.  I do a "route add foo 192.129.84.4", and it
selects ppp0.  ppp0, of course, does not reach the host on the local
ethernet.

I have existing routes through this host which work fine.

It may be that this has to do with ppp0 being convinced that it's
running, and connected to 0.0.0.0, but I can't get it to go away.
(ppp0 is already down, but keeps the "running" flag.  The pppd's running
are on ppp1 and ppp2.)

-s