-----BEGIN PGP SIGNED MESSAGE-----
Multi homing the router is an option we are considering and I'm waiting
for it to be assessed but unfortunately is not that obvious for us to
server0 is the global zone, indeed, and I thought I could use somehow
its packet-forwarding and routing services from the 192.168.0.0/19 zone:
but, as you explained, it's not a viable option.
Thanks for the info,
Christine Tran wrote:
>> The problem I have is when creating shared IP zones on another subnet,
>> such as the 192.168.0.0/19: subnet 192.168.96.0/19 is unreachable and
>> they cannot connet to the outside world through 192.168.96.1.
> It can't work this way. Your zone on 192.168.0.0/19 will never see
> 192.168.96.1 because that gateway is not local to it. Your
> defaultrouter has to be on same segment. You can get around this if
> you set 192.168.96.1 up with another interface local to
> 192.168.0.0/19, multi-home your router. Then you'll have to add
> another default route on your global zone. If you're doing this on
> nge0, you'll also have to zone your switch.
>> Is there any way to use server0 as a router from inside the shared IP
>> zone so that the global zone forwards packets from one subnet to the
>> other and be able to reach 192.168.96.1?
> Yes, you can do it as described above. I assume you mean server0 is
> your global zone.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
zones-discuss mailing list