The defrouter feature doesn't change any existing kernel functionality.
It simply automates setting up routes which could have been established
by the global zone administrator. Whether those routes are useful
depends on factors beyond the zone configuration.
Steffen Weiberle wrote:
> On 10/06/08 21:38, Glenn Faden wrote:
>> The default route option is not specific to TX zones. However, it is
>> intended for environments where your zones aren't sharing the same
>> physical interfaces. This feature sets the default route for an
>> interface so I don't think it will provide the functionality you are
>> looking for.
> Hi Glenn,
> The preliminary documents say the same thing, that the 'defrouter' is
> for the interface.
> I see an opportunity to clarify the behavior as my initial expectation
> was that since the defrouter attribute is set in a zone's configuration,
> it applies to the zone.
> What happens when multiple zone configurations have different defrouter
> definitions for the same interface or the same subnet (given the
> complexity should multiple subnets be configured on a single interface)?
>> Max Levine wrote:
>>> We have a need to define a separate defaultroute for some of the
>>> shared-ip zones in our environment. All of the zones are on the same
>>> subnet, but only some need to have a different default route. I was
>>> reading psarc/2008/057 but I am confused if the functionality applies
>>> to zones on same subnet? Also I saw that this functionality was
>>> backported to Solaris 10 zoneadm patch, but it mentiones TX zones.
>>> Does this only apply to TX or regular zones as well?
>> zones-discuss mailing list
> zones-discuss mailing list
zones-discuss mailing list