headers
Alexander | 30 May 2011 14:06
Picon

bridges and vlans...

Hello.
On FreeBSD host system I have the following configuration:
on physical interface I created vlan, connected it to bridge, created epair and added it end to bridge. In
such way I can connect several jailed systems (VNET) to one vlan, providing one virtual interface to each jail.
I'm trying to achieve this functionality on OpenIndiana system (oi_151) so that severals zones could be
connected to one vlan with own vnic, but I didn't managed yet. I can't create  vnic based on vlan and can't
bridge vlan...
--

-- 
This message posted from opensolaris.org
Permalink | Reply |
headers
James Carlson | 30 May 2011 18:45

Re: bridges and vlans...

On 5/30/2011 8:06 AM, Alexander wrote:
> Hello.
> On FreeBSD host system I have the following configuration:
> on physical interface I created vlan, connected it to bridge, created epair and added it end to bridge. In
such way I can connect several jailed systems (VNET) to one vlan, providing one virtual interface to each jail.
> I'm trying to achieve this functionality on OpenIndiana system (oi_151) so that severals zones could be
connected to one vlan with own vnic, but I didn't managed yet. I can't create  vnic based on vlan and can't
bridge vlan...

Bridges exist logically below the level of VLANs, so you can't really
just bridge two distinct VLANs together.  It doesn't make sense, at
least to me.

You can create VNICs on top of an etherstub to connect zones together
with a virtual link.  I'm not certain, but I suspect that's what you're
trying to do.  See:

http://www.sun.com/bigadmin/features/articles/crossbow_net_virt.jsp

--

-- 
James Carlson         42.703N 71.076W         <carlsonj@...>
Permalink | Reply |
headers
Alexander | 30 May 2011 19:29
Picon

Re: bridges and vlans...

> On 5/30/2011 8:06 AM, Alexander wrote:
> > Hello.
> > On FreeBSD host system I have the following
> configuration:
> > on physical interface I created vlan, connected it
> to bridge, created epair and added it end to bridge.
> In such way I can connect several jailed systems
> (VNET) to one vlan, providing one virtual interface
> to each jail.
> > I'm trying to achieve this functionality on
> OpenIndiana system (oi_151) so that severals zones
> could be connected to one vlan with own vnic, but I
> didn't managed yet. I can't create  vnic based on
> vlan and can't bridge vlan...
> 
> Bridges exist logically below the level of VLANs, so
> you can't really
> just bridge two distinct VLANs together.  It doesn't
> make sense, at
> least to me.

Let me try to explain in more details.
I'd like to create the following configuration:

physicalInterface => vlanInterface <=> bridge   <=> etherstub <=> VirutalInterfaces for zones

In such way I'd like to achieve the following: each zone has exclusive ip stack and multiple zones can be in
one vlan, which is seen from outside. 
It seems, that most of our tasks can be solved with usual configuration (shared ip stack), but on our FreeBSD
hosts such configuration (exclusive ip stack + bridge per vlan) is quite convinient.  I was suprised that I
(Continue reading)

Permalink | Reply |
headers
Sebastien Roy | 1 Jun 2011 13:58
Picon
Favicon

Re: bridges and vlans...

On 05/30/11 13:29, Alexander wrote:
>> On 5/30/2011 8:06 AM, Alexander wrote:
>>> Hello. On FreeBSD host system I have the following
>> configuration:
>>> on physical interface I created vlan, connected it
>> to bridge, created epair and added it end to bridge. In such way I
>> can connect several jailed systems (VNET) to one vlan, providing
>> one virtual interface to each jail.
>>> I'm trying to achieve this functionality on
>> OpenIndiana system (oi_151) so that severals zones could be
>> connected to one vlan with own vnic, but I didn't managed yet. I
>> can't create  vnic based on vlan and can't bridge vlan...
>>
>> Bridges exist logically below the level of VLANs, so you can't
>> really just bridge two distinct VLANs together.  It doesn't make
>> sense, at least to me.
>
> Let me try to explain in more details. I'd like to create the
> following configuration:
>
> physicalInterface =>  vlanInterface<=>  bridge<=>  etherstub<=>
> VirutalInterfaces for zones
>
> In such way I'd like to achieve the following: each zone has
> exclusive ip stack and multiple zones can be in one vlan, which is
> seen from outside. It seems, that most of our tasks can be solved
> with usual configuration (shared ip stack), but on our FreeBSD hosts
> such configuration (exclusive ip stack + bridge per vlan) is quite
> convinient.  I was suprised that I can't achive similar configuration
> on Solaris host.
(Continue reading)

Permalink | Reply |
headers
Bob Palowoda | 4 Jun 2011 22:59

Re: bridges and vlans...

> On 05/30/11 13:29, Alexander wrote:
> >> On 5/30/2011 8:06 AM, Alexander wrote:
> >>> Hello. On FreeBSD host system I have the
> following
> >> configuration:
> >>> on physical interface I created vlan, connected
> it
> >> to bridge, created epair and added it end to
> bridge. In such way I
> >> can connect several jailed systems (VNET) to one
> vlan, providing
> >> one virtual interface to each jail.
> >>> I'm trying to achieve this functionality on
> >> OpenIndiana system (oi_151) so that severals zones
> could be
> >> connected to one vlan with own vnic, but I didn't
> managed yet. I
> >> can't create  vnic based on vlan and can't bridge
> vlan...
> >>
> >> Bridges exist logically below the level of VLANs,
> so you can't
> >> really just bridge two distinct VLANs together.
>  It doesn't make
> > sense, at least to me.
> >
> > Let me try to explain in more details. I'd like to
> create the
> > following configuration:
> >
(Continue reading)

Permalink | Reply |

Gmane