SUMMARY: Solaris 2.6 routing problem

From: Roy Culley (
Date: Thu Jun 17 1999 - 02:33:08 CDT

Original question:

> We recently upgraded a server from 2.5.1 to 2.6 + recommended patches
> as of 24th May. This server is multi-homed and on one of the
> interfaces we delete the route entry for the subnet it is connected to
> and add a single host route. For example, if the subnet is
> 24 then after booting the interface has a route as follows:
> UH 3 30 hme1
> On 2.5.1 run the following 2 route commands:
> route add host 0
> route delete hme1
> On Solaris 2.6 the first command fails as the system knows that the
> current subnet route handles this host route so in 2.6 we reversed the
> commands:
> route delete hme1
> route add host 0
> This all appears to work and after this the routing table entry looks
> like this:
> UH 3 30 hme1
> This looks the same on 2.5.1 and 2.6. However on 2.6
> cannot be accessed from whereas under 2.5.1 it can. Does
> anyone know why this doesn't work on 2.6 or know of a work around?
> ifconfig shows the following for the interface after these route
> changes:
> inet netmask ffffff00 broadcast
> ether 8:0:20:7b:db:5a

I received help from: Casper Dik <>
                      Joe Doetzl <>
                      Wolf Schaefer <>

Many thanks to them.

Unfortunately none of them were able to solve my problem. Further
investigation by me showed that I could reproduce the problem on
any Solaris 2.6 system. I opened a bug report with Sun and they
have confirmed that the problem exists but only in Solaris 2.6.
2.5.1 and 2.7 don't have this bug. The problem is being looked into
by Sun but they cannot give a deadline for when a fix will be
available. Apparently, there are numerous routing bugs in 2.6 and
they will release a patch when they have all been fixed.


This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:21 CDT