Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-17 Thread Scott Lowe 
On 01/16/2017 11:39 PM, Shravan S K wrote:
> How to do the IP connectivity part using OVS internal ports?


[SL] Take a look at either of these blog posts:





Both posts illustrate the use of an OVS internal port as an IP interface.

Hope this helps!


> Thanks.
> 
> Shravan
> 
> On 16 January 2017 at 04:40, Scott Lowe  > wrote:
> 
> On 01/13/2017 03:20 AM, Shravan S K wrote:
>> My motive is to simulate VXLAN functionality on a bigger topology using
>> mininet.
>> My plan - As Mininet uses OVS bridges to simulate vswitch functionality,
>> we can use ovs-vsctl to configure VXLAN functionality on the bridges. I
>> thought let me try for a simple topology without using Mininet and just
>> using OVS on a single host and 2 VMs. If it works, then I can make a
>> similar configuration for a bigger topology using mininet.
>>
>> OVS on a single host and 2 VMs : vm1-br1---br2-vm2
>> I am confused on how to perform the vxlan config for the above setup.
>>
>> If the above one works, I could try on the mininet topologies.
>> For the mininet topology ( --topo=linear,2 )
>> h1 - s1 -- s2  h2 (h1,h2 are hosts, s1,s2 are switches -
>> actually ovs bridges)
> 
> 
> Setting aside the mininet question for the moment, the way to get VXLAN
> working between two OVS bridges is to establish an IP endpoint (also
> known as a VXLAN Tunnel Endpoint, or VTEP) for each bridge. So, in your
> example configuration, br1 and br2 each need an interface (of some sort)
> with an IP address. You'd then configure a VXLAN port on br1 that points
> to the IP endpoint for br2, and configure a VXLAN port on br2 that
> points to the IP endpoint for br1. Since you're trying to do this within
> a single host, you might consider using OVS internal ports as the IP
> endpoints for each bridge. As long as each IP endpoint can reach the
> other, then in theory it should work.

-- 
Scott

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-15 Thread Scott Lowe 
On 01/13/2017 03:20 AM, Shravan S K wrote:
> My motive is to simulate VXLAN functionality on a bigger topology using
> mininet.
> My plan - As Mininet uses OVS bridges to simulate vswitch functionality,
> we can use ovs-vsctl to configure VXLAN functionality on the bridges. I
> thought let me try for a simple topology without using Mininet and just
> using OVS on a single host and 2 VMs. If it works, then I can make a
> similar configuration for a bigger topology using mininet.
> 
> OVS on a single host and 2 VMs : vm1-br1---br2-vm2
> I am confused on how to perform the vxlan config for the above setup.
> 
> If the above one works, I could try on the mininet topologies.
> For the mininet topology ( --topo=linear,2 )
> h1 - s1 -- s2  h2 (h1,h2 are hosts, s1,s2 are switches -
> actually ovs bridges)


Setting aside the mininet question for the moment, the way to get VXLAN
working between two OVS bridges is to establish an IP endpoint (also
known as a VXLAN Tunnel Endpoint, or VTEP) for each bridge. So, in your
example configuration, br1 and br2 each need an interface (of some sort)
with an IP address. You'd then configure a VXLAN port on br1 that points
to the IP endpoint for br2, and configure a VXLAN port on br2 that
points to the IP endpoint for br1. Since you're trying to do this within
a single host, you might consider using OVS internal ports as the IP
endpoints for each bridge. As long as each IP endpoint can reach the
other, then in theory it should work.

-- 
Scott

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-13 Thread Michael Ben-Ami via discuss 
Shravan, these mininet branches seem to address our problem:

https://github.com/mininet/mininet/pull/577
https://github.com/mininet/mininet/pull/524

I've had more luck with the first one.

On Fri, Jan 13, 2017 at 1:40 PM, Michael Ben-Ami 
wrote:

> Thanks Joe, I'm looking at feasibility submitting a PR to mininet so that
> it can natively accomplish exactly this.
>
> On Fri, Jan 13, 2017 at 1:31 PM, Joe Stringer  wrote:
>
>> On 13 January 2017 at 08:20, Michael Ben-Ami via discuss
>>  wrote:
>> > I'm in a very similar boat as Shravan. The utility for me is to be able
>> to
>> > test flow sets on arbitrary mininet topologies that simulate real world
>> > topologies that may or may not use VXLAN. The root cause as I see it is
>> that
>> > mininet must put all OVS bridges in the same namespace. This is
>> probably an
>> > OVS limitation not mininet. Has been discussed a little here:
>> > https://mail.openvswitch.org/pipermail/ovs-discuss/2015-Sept
>> ember/038543.html
>>
>> For what it's worth, I believe that this is a limitation for each OVS
>> instance - each instance can only run bridges in the namespace it is
>> running. If you ran multiple copies of OVS in different network
>> namespaces / containers, it should work. (So would running the copies
>> in different VMs)
>>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-12 Thread Justin Pettit 
Assuming that you're running on Linux, you could try setting up network 
namespaces. 

--Justin


> On Jan 12, 2017, at 6:36 PM, Raymond Burkholder <r...@oneunified.net> wrote:
> 
> Try running VirtualBox, and build two guests with shared networking.   That 
> will get you an appropriate simulation of computer to computer vxlan 
> mechanisms.
>  
> From: ovs-discuss-boun...@openvswitch.org 
> [mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Shravan S K
> Sent: Thursday, January 12, 2017 22:34
> To: Scott Lowe <scott.l...@scottlowe.org>
> Cc: ovs-discuss@openvswitch.org
> Subject: Re: [ovs-discuss] VXLAN support in OVS 2.5.0
>  
> Because of lack of hardware, I'm trying a vxlan setup on a single computer.
> 
> On 13-Jan-2017 04:47, "Scott Lowe" <scott.l...@scottlowe.org> wrote:
> Please don't drop the list.
> 
> Before we go down that path, can you help me understand what you're
> trying to achieve by building a VXLAN tunnel between two VMs on the same
> host?
> 
> 
> 
> On 01/12/2017 10:15 AM, Shravan S K wrote:
> > I am not sure how to do the config for what you said.
> > Can you please explain how to configure the setup that you're suggesting ?
> >
> > Shravan
> >
> > On 12 January 2017 at 02:17, Scott Lowe <scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>> wrote:
> >
> > On 01/11/2017 03:54 AM, Shravan S K wrote:
> > > Like this?
> > > vm01---|
> > > |--vm03
> > >
> > > 
> > br1(vxlanport1)br-int1=br-int2--(vxlanport2)br2
> > > vm02---|
> > > |---vm04
> > >
> > > What is the need for the bridges br-int1 and br-int2? Why is it not
> > > possible without them(as the topology shown earlier in this thread)?
> >
> >
> > [SL] No, I don't think this is the configuration you'd want to use. The
> > "br-int" bridges aren't strictly required; you could use br1 and br2.
> > The trick here---as you're trying to create a VXLAN tunnel within a
> > host---would be that you'll need 2 IP endpoints (one for each end of the
> > tunnel), and you'd need each bridge with a VXLAN port to be associated
> > with one of those IP endpoints.
> >
> > As I said, though, I haven't tested a configuration like this. Further,
> > to be honest, I'm not really sure what you're trying to accomplish with
> > such a configuration.
> >
> >
> > > Shravan
> > >
> > > On 11 January 2017 at 11:59, Scott Lowe <scott.l...@scottlowe.org 
> > <mailto:scott.l...@scottlowe.org>
> > > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>> 
> > wrote:
> > >
> > > Please see my response inline, prefixed with [SL].
> > >
> > >
> > > On 01/10/2017 09:50 PM, Shravan S K wrote:
> > >> I am asking if that can be done on a single physical host having
> > >> OVS. Say, as mininet creates bridges which act as switches. Can
> > >> vxlan be setup using Mininet?
> > >
> > >
> > > [SL] I don't know if it's possible for Mininet to set up VXLAN;
> > > that's a question best asked on a Mininet-related forum.
> > >
> > > As for whether it can be done on a single host, I suppose if you were
> > > to use 2 separate bridges for physical connectivity along with 2
> > > separate bridges for the tunnels, it might work. I've never tried it,
> > > though, so this is just conjecture.
> > >
> > >
> > >> Shravan
> > >>
> > >> On 10 January 2017 at 23:33, Scott Lowe <scott.l...@scottlowe.org 
> > <mailto:scott.l...@scottlowe.org>
> > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>
> > >> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>>>> wrote:
> > >>
> > >> Please see my response below.
> > >>
> > >>
> > >> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > >>> Is it possible to create a VXLAN setup using just bridges created
> > >>> by OVS? (using ovs-vsctl to create these bridges,ports and vxlan
> >

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-12 Thread Shravan S K 
I know that. But I wanted to experiment with OVS bridges first, and then if
it worked I wanted to re-create the config for a larger topology using
Mininet(which uses OVS bridges(for switches) using OVS).

Thanks.

Shravan

On 13 January 2017 at 08:06, Raymond Burkholder <r...@oneunified.net> wrote:

> Try running VirtualBox, and build two guests with shared networking.
> That will get you an appropriate simulation of computer to computer vxlan
> mechanisms.
>
>
>
> *From:* ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-bounces@
> openvswitch.org] *On Behalf Of *Shravan S K
> *Sent:* Thursday, January 12, 2017 22:34
> *To:* Scott Lowe <scott.l...@scottlowe.org>
> *Cc:* ovs-discuss@openvswitch.org
> *Subject:* Re: [ovs-discuss] VXLAN support in OVS 2.5.0
>
>
>
> Because of lack of hardware, I'm trying a vxlan setup on a single
> computer.
>
> On 13-Jan-2017 04:47, "Scott Lowe" <scott.l...@scottlowe.org> wrote:
>
> Please don't drop the list.
>
> Before we go down that path, can you help me understand what you're
> trying to achieve by building a VXLAN tunnel between two VMs on the same
> host?
>
>
>
> On 01/12/2017 10:15 AM, Shravan S K wrote:
> > I am not sure how to do the config for what you said.
> > Can you please explain how to configure the setup that you're suggesting
> ?
> >
> > Shravan
> >
> > On 12 January 2017 at 02:17, Scott Lowe <scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>> wrote:
> >
> > On 01/11/2017 03:54 AM, Shravan S K wrote:
> > > Like this?
> > > vm01---|
> > > |--vm03
> > >
> > > br1(vxlanport1)br-int1=br-int2--
> (vxlanport2)br2
> > > vm02---|
> > > |---vm04
> > >
> > > What is the need for the bridges br-int1 and br-int2? Why is it not
> > > possible without them(as the topology shown earlier in this
> thread)?
> >
> >
> > [SL] No, I don't think this is the configuration you'd want to use.
> The
> > "br-int" bridges aren't strictly required; you could use br1 and br2.
> > The trick here---as you're trying to create a VXLAN tunnel within a
> > host---would be that you'll need 2 IP endpoints (one for each end of
> the
> > tunnel), and you'd need each bridge with a VXLAN port to be
> associated
> > with one of those IP endpoints.
> >
> > As I said, though, I haven't tested a configuration like this.
> Further,
> > to be honest, I'm not really sure what you're trying to accomplish
> with
> > such a configuration.
> >
> >
> > > Shravan
> > >
> > > On 11 January 2017 at 11:59, Scott Lowe <scott.l...@scottlowe.org
> <mailto:scott.l...@scottlowe.org>
> > > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>>
> wrote:
> > >
> > > Please see my response inline, prefixed with [SL].
> > >
> > >
> > > On 01/10/2017 09:50 PM, Shravan S K wrote:
> > >> I am asking if that can be done on a single physical host having
> > >> OVS. Say, as mininet creates bridges which act as switches. Can
> > >> vxlan be setup using Mininet?
> > >
> > >
> > > [SL] I don't know if it's possible for Mininet to set up VXLAN;
> > > that's a question best asked on a Mininet-related forum.
> > >
> > > As for whether it can be done on a single host, I suppose if you
> were
> > > to use 2 separate bridges for physical connectivity along with 2
> > > separate bridges for the tunnels, it might work. I've never tried
> it,
> > > though, so this is just conjecture.
> > >
> > >
> > >> Shravan
> > >>
> > >> On 10 January 2017 at 23:33, Scott Lowe <scott.l...@scottlowe.org
> <mailto:scott.l...@scottlowe.org>
> > <mailto:scott.l...@scottlowe.org <mailto:scott.l...@scottlowe.org>>
> > >> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org> <mailto:scott.l...@scottlowe.org
> > <mailto:scott.l...@scottlowe.org>>>> wrote:
> > >>
> > >> Please see my response below.
> > >>
> > >>
> > >> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > >>> Is it

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-11 Thread Scott Lowe 
On 01/11/2017 03:54 AM, Shravan S K wrote:
> Like this?
> vm01---|  
>   
> |--vm03
>  
> br1(vxlanport1)br-int1=br-int2--(vxlanport2)br2
> vm02---|  
>
> |---vm04
> 
> What is the need for the bridges br-int1 and br-int2? Why is it not
> possible without them(as the topology shown earlier in this thread)?


[SL] No, I don't think this is the configuration you'd want to use. The
"br-int" bridges aren't strictly required; you could use br1 and br2.
The trick here---as you're trying to create a VXLAN tunnel within a
host---would be that you'll need 2 IP endpoints (one for each end of the
tunnel), and you'd need each bridge with a VXLAN port to be associated
with one of those IP endpoints.

As I said, though, I haven't tested a configuration like this. Further,
to be honest, I'm not really sure what you're trying to accomplish with
such a configuration.


> Shravan
> 
> On 11 January 2017 at 11:59, Scott Lowe  > wrote:
> 
> Please see my response inline, prefixed with [SL].
> 
> 
> On 01/10/2017 09:50 PM, Shravan S K wrote:
>> I am asking if that can be done on a single physical host having
>> OVS. Say, as mininet creates bridges which act as switches. Can
>> vxlan be setup using Mininet?
> 
> 
> [SL] I don't know if it's possible for Mininet to set up VXLAN;
> that's a question best asked on a Mininet-related forum.
> 
> As for whether it can be done on a single host, I suppose if you were
> to use 2 separate bridges for physical connectivity along with 2
> separate bridges for the tunnels, it might work. I've never tried it,
> though, so this is just conjecture.
> 
> 
>> Shravan
>>
>> On 10 January 2017 at 23:33, Scott Lowe > 
>> >> wrote:
>>
>> Please see my response below.
>>
>>
>> On 01/10/2017 02:26 AM, Shravan S K wrote:
>>> Is it possible to create a VXLAN setup using just bridges created
>>> by OVS? (using ovs-vsctl to create these bridges,ports and vxlan
>>> config)
>>>
>>> vm01---| |--vm03
>>>   br1---br2
>>> vm02---| |---vm04
>>
>>
>> Yes, this is possible. On each hypervisor where OVS is running and
>> where you have VMs you'd like to connect over VXLAN tunnels, create
>> a bridge ("br-tun", for example). Create and configure a VXLAN port
>> appropriately on br-tun on each hypervisor, and then connect your
>> VMs. You should be good to go. My website has an example of doing
>> this with GRE; VXLAN should be nearly identical.
>>
>> Hope this helps,


-- 
Scott




signature.asc
Description: OpenPGP digital signature
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-11 Thread Shravan S K 
Like this?
vm01---|
|--vm03

br1(vxlanport1)br-int1=br-int2--(vxlanport2)br2
vm02---|
|---vm04

What is the need for the bridges br-int1 and br-int2? Why is it not
possible without them(as the topology shown earlier in this thread)?




Shravan

On 11 January 2017 at 11:59, Scott Lowe  wrote:

> Please see my response inline, prefixed with [SL].
>
>
> On 01/10/2017 09:50 PM, Shravan S K wrote:
> > I am asking if that can be done on a single physical host having OVS.
> > Say, as mininet creates bridges which act as switches. Can vxlan be
> > setup using Mininet?
>
>
> [SL] I don't know if it's possible for Mininet to set up VXLAN; that's a
> question best asked on a Mininet-related forum.
>
> As for whether it can be done on a single host, I suppose if you were to
> use 2 separate bridges for physical connectivity along with 2 separate
> bridges for the tunnels, it might work. I've never tried it, though, so
> this is just conjecture.
>
>
> > Shravan
> >
> > On 10 January 2017 at 23:33, Scott Lowe  > > wrote:
> >
> > Please see my response below.
> >
> >
> > On 01/10/2017 02:26 AM, Shravan S K wrote:
> > > Is it possible to create a VXLAN setup using just bridges created
> by
> > > OVS? (using ovs-vsctl to create these bridges,ports and vxlan
> config)
> > >
> > > vm01---| |--vm03
> > >   br1---br2
> > > vm02---| |---vm04
> >
> >
> > Yes, this is possible. On each hypervisor where OVS is running and
> where
> > you have VMs you'd like to connect over VXLAN tunnels, create a
> bridge
> > ("br-tun", for example). Create and configure a VXLAN port
> appropriately
> > on br-tun on each hypervisor, and then connect your VMs. You should
> be
> > good to go. My website has an example of doing this with GRE; VXLAN
> > should be nearly identical.
> >
> > Hope this helps,
>
>
> --
> Scott
>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-10 Thread Scott Lowe 
Please see my response inline, prefixed with [SL].


On 01/10/2017 09:50 PM, Shravan S K wrote:
> I am asking if that can be done on a single physical host having OVS.
> Say, as mininet creates bridges which act as switches. Can vxlan be
> setup using Mininet?


[SL] I don't know if it's possible for Mininet to set up VXLAN; that's a
question best asked on a Mininet-related forum.

As for whether it can be done on a single host, I suppose if you were to
use 2 separate bridges for physical connectivity along with 2 separate
bridges for the tunnels, it might work. I've never tried it, though, so
this is just conjecture.


> Shravan
> 
> On 10 January 2017 at 23:33, Scott Lowe  > wrote:
> 
> Please see my response below.
> 
> 
> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > Is it possible to create a VXLAN setup using just bridges created by
> > OVS? (using ovs-vsctl to create these bridges,ports and vxlan config)
> >
> > vm01---| |--vm03
> >   br1---br2
> > vm02---| |---vm04
> 
> 
> Yes, this is possible. On each hypervisor where OVS is running and where
> you have VMs you'd like to connect over VXLAN tunnels, create a bridge
> ("br-tun", for example). Create and configure a VXLAN port appropriately
> on br-tun on each hypervisor, and then connect your VMs. You should be
> good to go. My website has an example of doing this with GRE; VXLAN
> should be nearly identical.
> 
> Hope this helps,


-- 
Scott




signature.asc
Description: OpenPGP digital signature
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-10 Thread Shravan S K 
I am asking if that can be done on a single physical host having OVS.
Say, as mininet creates bridges which act as switches. Can vxlan be setup
using Mininet?

Shravan

On 10 January 2017 at 23:33, Scott Lowe  wrote:

> Please see my response below.
>
>
> On 01/10/2017 02:26 AM, Shravan S K wrote:
> > Is it possible to create a VXLAN setup using just bridges created by
> > OVS? (using ovs-vsctl to create these bridges,ports and vxlan config)
> >
> > vm01---| |--vm03
> >   br1---br2
> > vm02---| |---vm04
>
>
> Yes, this is possible. On each hypervisor where OVS is running and where
> you have VMs you'd like to connect over VXLAN tunnels, create a bridge
> ("br-tun", for example). Create and configure a VXLAN port appropriately
> on br-tun on each hypervisor, and then connect your VMs. You should be
> good to go. My website has an example of doing this with GRE; VXLAN
> should be nearly identical.
>
> Hope this helps,
>
> --
> Scott
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2017-01-10 Thread Shravan S K 
Is it possible to create a VXLAN setup using just bridges created by OVS?
(using ovs-vsctl to create these bridges,ports and vxlan config)

vm01---| |--vm03
  br1---br2
vm02---| |---vm04



Shravan

On 29 December 2016 at 10:42, Shravan S K  wrote:

> Thanks, Scott.
>
> Beautiful explanation in the post!
>
> Shravan
>
> On 28 December 2016 at 21:29, Scott Lowe  wrote:
>
>> Please see my responses inline, prefixed by [SL].
>>
>>
>> On Dec 28, 2016, at 4:15 AM, Shravan S K  wrote:
>> >
>> > I am trying this - http://docs.openvswitch.org/en
>> /latest/howto/userspace-tunneling/
>> >
>> > 1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
>> shown in the diagram ?
>>
>>
>> [SL] I haven't worked with userspace tunneling yet, but I believe the
>> principles here are much the same as with a "traditional" kernel-mode
>> implementation. Traffic from the vxlan0 port on br-int is directed out the
>> physical interfaces attached to br-phy via the kernel's routing table
>> (which is why step #5 is necessary).
>>
>> This article may help you understand the various traffic patterns you may
>> encounter with OVS:
>>
>> > -traffic-patterns/>
>>
>>
>> > 2) What should I do if also want to access(from the VM) the network
>> that my host is in ?
>>
>>
>> [SL] You would need to either a) add an additional interface to the VM,
>> or b) create a VXLAN-to-VLAN gateway. In the case of a), this additional
>> interface would need to be connected to br-phy (or its equivalent). In the
>> case of b), this would be another system (guest or VM) that receives VXLAN
>> traffic and handles decapsulation of the traffic and placement onto a VLAN
>> outside the overlay.
>>
>> I hope this helps.
>>
>> --
>> Scott
>>
>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2016-12-28 Thread Shravan S K 
Thanks, Scott.

Beautiful explanation in the post!

Shravan

On 28 December 2016 at 21:29, Scott Lowe  wrote:

> Please see my responses inline, prefixed by [SL].
>
>
> On Dec 28, 2016, at 4:15 AM, Shravan S K  wrote:
> >
> > I am trying this - http://docs.openvswitch.org/
> en/latest/howto/userspace-tunneling/
> >
> > 1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
> shown in the diagram ?
>
>
> [SL] I haven't worked with userspace tunneling yet, but I believe the
> principles here are much the same as with a "traditional" kernel-mode
> implementation. Traffic from the vxlan0 port on br-int is directed out the
> physical interfaces attached to br-phy via the kernel's routing table
> (which is why step #5 is necessary).
>
> This article may help you understand the various traffic patterns you may
> encounter with OVS:
>
>  vswitch-traffic-patterns/>
>
>
> > 2) What should I do if also want to access(from the VM) the network that
> my host is in ?
>
>
> [SL] You would need to either a) add an additional interface to the VM, or
> b) create a VXLAN-to-VLAN gateway. In the case of a), this additional
> interface would need to be connected to br-phy (or its equivalent). In the
> case of b), this would be another system (guest or VM) that receives VXLAN
> traffic and handles decapsulation of the traffic and placement onto a VLAN
> outside the overlay.
>
> I hope this helps.
>
> --
> Scott
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2016-12-28 Thread Scott Lowe 
Please see my responses inline, prefixed by [SL].


On Dec 28, 2016, at 4:15 AM, Shravan S K  wrote:
> 
> I am trying this - 
> http://docs.openvswitch.org/en/latest/howto/userspace-tunneling/
> 
> 1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as shown 
> in the diagram ?


[SL] I haven't worked with userspace tunneling yet, but I believe the 
principles here are much the same as with a "traditional" kernel-mode 
implementation. Traffic from the vxlan0 port on br-int is directed out the 
physical interfaces attached to br-phy via the kernel's routing table (which is 
why step #5 is necessary).

This article may help you understand the various traffic patterns you may 
encounter with OVS:




> 2) What should I do if also want to access(from the VM) the network that my 
> host is in ?


[SL] You would need to either a) add an additional interface to the VM, or b) 
create a VXLAN-to-VLAN gateway. In the case of a), this additional interface 
would need to be connected to br-phy (or its equivalent). In the case of b), 
this would be another system (guest or VM) that receives VXLAN traffic and 
handles decapsulation of the traffic and placement onto a VLAN outside the 
overlay.

I hope this helps.

-- 
Scott

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2016-12-28 Thread Shravan S K 
I am trying this -
http://docs.openvswitch.org/en/latest/howto/userspace-tunneling/

1) Which step connects vxlan interface,vxlan0, to the bridge,br-phy, as
shown in the diagram ?

2) What should I do if *also* want to access(from the VM) the network that
my host is in ?

Thanks.

Shravan

On 28 December 2016 at 11:13, Shravan S K  wrote:

> I found info in this http://openvswitch.org/releases/NEWS-2.6.0
>
>
>
>
> Shravan
>
> On 28 December 2016 at 11:07, Shravan S K  wrote:
>
>> Does OVS 2.5.0 support VXLANs ?
>>
>>
>>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

2016-12-27 Thread Shravan S K 
I found info in this http://openvswitch.org/releases/NEWS-2.6.0




Shravan

On 28 December 2016 at 11:07, Shravan S K  wrote:

> Does OVS 2.5.0 support VXLANs ?
>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss