Glenn Faden writes:
> If we're going to remove the route when the zone is halted, then we have
> to prevent the another zone from using the same route. However, I think
> that adding this complexity will not improve the customer experience.
> For example, I'm afraid that there may be race conditions between a zone
> that is booting and one that is shutting down with the same default
> route. The simpler solution seemed adequate to me.
I don't think it is. Try this:
- set up a default route to 10.0.0.1 for a zone.
- boot it.
- shut it down.
- change that default route to 10.0.0.2.
- boot it again.
- examine the kernel's forwarding (routing) table.
You should end up with two default routes; one to the new destination,
and another to the old destination. The system caches these things.
("-nostatic" might do the trick, but I'm not positive.)
As for the overlap case, I'm happy with just saying in the
documentation that this configuration is a mistake: don't do it.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
