shared-IP and have addresses on only the internal network.
I'm just not sure where to look for the problem source.
-Michael
___
zones-discuss mailing list
zones-discuss@opensolaris.org
--
Jon Anderson
Solaris Revenue Product Engineering
, bge0, bge1 all didn't work.
The IP-type is exclusive.
Can anyone please help? I would also like to set up an exclusive-IP zone with
an externally-visible IP address that is either assigned by the external DHCP
server or pre-assigned to the zone. Thanks!
--
Jon Anderson
--
Jon Anderson
Solaris Revenue Product Engineering
Sun Microsystems Inc.
SPARC House (UK)
Tel: ++44 (0)1252 421 868
Mob: ++44 (0)7747 180 910
___
zones-discuss mailing list
zones-discuss@opensolaris.org
stack zones.
Thanks.
CT
___
zones-discuss mailing list
zones-discuss@opensolaris.org
--
Jon Anderson
Solaris Revenue Product Engineering
Sun Microsystems Inc.
SPARC House (UK)
Tel: ++44 (0)1252 421 868
and destination
was the same then we would still send via loopback. You should be
able to avoid this if the zone IP addresses are configured on
different physical interfaces.
CT
--
Jon Anderson
Solaris Revenue Product Engineering
Sun Microsystems Inc.
SPARC House (UK
You can't disable loopback traffic routing on a shared stack zone if the source
and destination are
on the same interface. This would be a data link loopback which most L2 devices
wouldn't handle
properly (i.e. you are trying to send from e1000g0 to a an address on e1000g0)
--
This message
