Very Computer

> I'm seeing the problem described below.  How do I get rid of the default
> routes that appear with "--" as the gateway in netstat?  It's not an easy
> thing to look for in databases with the "--". =)  Once the "--" appears, the
> system only uses that as the default route and never touches the real one.

> I'm using Solaris 2.5.1 and upgrading to a higher version of Solaris is not
> an option at this time, but I can patch if needed.  This clears up on a
> reboot, but I would prefer to keep the box running.

> > I'm seeing the problem described below.  How do I get rid of the default
> > routes that appear with "--" as the gateway in netstat?  It's not an easy
> > thing to look for in databases with the "--". =)  Once the "--" appears, the
> > system only uses that as the default route and never touches the real one.

> > I'm using Solaris 2.5.1 and upgrading to a higher version of Solaris is not
> > an option at this time, but I can patch if needed.  This clears up on a
> > reboot, but I would prefer to keep the box running.

> I've never heard of such a problem... Hmm.

> It sounds like you have in.routed running on the system, and it's
> auto-discovering this problem route from a misconfigured router/switch. If you
> don't have in.routed running, I'm totally stumped.

> What does the routing table look like? Post the output of netstat -rn.

> If you only have one "default" route, just put its IP in /etc/defaultrouter
> and reboot. That will prevent in.routed from running.

> in.routed was indeed running, but since my defaultroute changes due to
> the dynamic nature of my DHCP cable modem (yay...) I can't use that
> file, so I've just commented the portion out in /etc/rc2.d/S69inet for
> now.

> in.routed was indeed running, but since my defaultroute changes due to
> the dynamic nature of my DHCP cable modem (yay...) I can't use that
> file, so I've just commented the portion out in /etc/rc2.d/S69inet for
> now.

> The routes look like this...
> vader:/var/named#>netstat -nr

> Routing Table:
>   Destination           Gateway           Flags  Ref   Use   Interface
> -------------------- -------------------- ----- ----- ------ ---------
> 127.0.0.1            127.0.0.1             UH       0      2  lo0
> 216.164.212.1            --                UH       5      0
> 255.255.255.255          --                UH       5      0
> 216.164.212.255          --                UH       5      0
> 192.168.0.0          192.168.0.100         U        2    292  hme0
> default                  --                U        5   3467  le0

> which DHCP then makes this once an address is discovered...
> vader:/var/named#>netstat -nr

> Routing Table:
>   Destination           Gateway           Flags  Ref   Use   Interface
> -------------------- -------------------- ----- ----- ------ ---------
> 127.0.0.1            127.0.0.1             UH       0      2  lo0
> 149.112.50.99        127.0.0.1             UGH      0      0
> 216.164.212.1            --                UH      10      0
> 216.164.212.1        149.112.50.99         UH      10      0  le0
> 255.255.255.255          --                UH      10      0
> 255.255.255.255      149.112.50.99         UH      10      0  le0
> 216.164.212.255          --                UH      10      0
> 216.164.212.255      149.112.50.99         UH      10      0  le0
> 149.112.50.64        149.112.50.99         U       10      1  le0
> 192.168.0.0          192.168.0.100         U        2    298  hme0
> default                  --                U       10   4417
> default              149.112.50.99         U       10      0  le0

> Ernie

> > > I'm seeing the problem described below.  How do I get rid of the
default
> > > routes that appear with "--" as the gateway in netstat?  It's not an
easy
> > > thing to look for in databases with the "--". =)  Once the "--"
appears, the
> > > system only uses that as the default route and never touches the real
one.

> > > I'm using Solaris 2.5.1 and upgrading to a higher version of Solaris
is not
> > > an option at this time, but I can patch if needed.  This clears up on
a
> > > reboot, but I would prefer to keep the box running.

> > I've never heard of such a problem... Hmm.

> > It sounds like you have in.routed running on the system, and it's
> > auto-discovering this problem route from a misconfigured router/switch.
If you
> > don't have in.routed running, I'm totally stumped.

> > What does the routing table look like? Post the output of netstat -rn.

> > If you only have one "default" route, just put its IP in
/etc/defaultrouter
> > and reboot. That will prevent in.routed from running.