On 02/24/09 21:26, Mike Gerdts wrote:
On Tue, Feb 24, 2009 at 7:51 PM, Bangalore, Suresh
<suresh.bangal...@railcorp.nsw.gov.au> wrote:
Hi Mike
The netmask is /24.


This implies that you have three different subnets and you either have
three distinct cables going to the machine or you are using three

In the global zone you will have "" in /etc/defaultrouter.

In zone1's zone configuration, you will have a network configured like
the following (assuming VLAN 10 tagged on on e1000g0):

zonecfg:zone1> info net
        physical: e1000g10000

In zone2's zone configuration, you will have something like (assuming
VLAN 20 tagged on e1000g0):

zonecfg:zone1> info net
        physical: e1000g20000

This could also work if they are all on a single 'data link' as seen by 'dladm show-link', although I only do that in my play situations.


specifically [10] in section 5.

-----Original Message-----
From: Mike Gerdts [mailto:mger...@gmail.com]
Sent: Wednesday, 25 February 2009 12:51 PM
To: Bangalore, Suresh
Cc: zones-discuss@opensolaris.org
Subject: Re: [zones-discuss] Zones on multiple subnets

On Tue, Feb 24, 2009 at 7:19 PM, Bangalore, Suresh 
<suresh.bangal...@railcorp.nsw.gov.au> wrote:
Hi Gurus

I need to setup zones as shown below.
Zone1: 10.10.10.X with default router
Zone2: 10.10.20.X with default router And Global zone
10.10.30.X with default router

Is this achievable. As shown above, I need the zones to have a
separate default router than  the default router for the global zone.

I don't have the luxury of using dedicated ports to achieve this.
Any suggestions/workarounds are greatly appreciated.
What is the netmask?  That is, the story is completely different between:




If it is the second, then you are dealing with three distinct subnets
and life is much easier.   If you really only have one subnet, I'm not
sure there is a solution.

Mike Gerdts

This e-mail and any attachments may contain confidential information that is 
intended solely for the use of the intended recipient and may be subject to 
copyright. If you receive this e-mail in error, please notify the sender 
immediately and delete the email and its attachments from your system. You must 
not disclose, copy or use any part of this e-mail if you are not the intended 
recipient. Any opinion expressed in this e-mail and any attachments is not an 
opinion of RailCorp unless stated or apparent from its content. RailCorp is not 
responsible for any unauthorised alterations to this e-mail or any attachments. 
RailCorp will not incur any liability resulting directly or indirectly as a 
result of the recipient accessing any of the attached files that may contain a 

zones-discuss mailing list

Reply via email to