Re: [ovs-discuss] VXLAN offload not work on openvswitch 2.6.0 + 3.10.45

On 24 October 2016 at 19:39, 张东亚 wrote: > Hi List, > > We have now testing openvswitch 2.6.0 on kernel 3.10.45, however we noticed > there is performance drop than openvswitch 2.5.0 on the same kernel, which > iperf can only have a 2G bandwidth for a pair of 10G links. > > After check the code, it

Re: [ovs-discuss] VXLAN offload not work on openvswitch 2.6.0 + 3.10.45

I really encourage you to use flent with the rrul test suite when doing testing. Iperf is too simplistic and suffers from burstiness. http://flent.org On 24 October 2016 at 20:51, 张东亚 wrote: > I am afraid my observation for openvswitch 2.6.0 is wrong, for 3.10.45, > USE_UPSTREAM_TUNNEL is al

Re: [ovs-discuss] VXLAN offload not work on openvswitch 2.6.0 + 3.10.45

I am afraid my observation for openvswitch 2.6.0 is wrong, for 3.10.45, USE_UPSTREAM_TUNNEL is also not defined, and after confirm with my colleague, openvswitch 2.5.0 + 3.10.45 also face the same poor bandwidth issue. So the problem applies for both openvswitch 2.5.0 and 2.6.0 on 3.10.45, is vxla

[ovs-discuss] VXLAN offload not work on openvswitch 2.6.0 + 3.10.45

Hi List, We have now testing openvswitch 2.6.0 on kernel 3.10.45, however we noticed there is performance drop than openvswitch 2.5.0 on the same kernel, which iperf can only have a 2G bandwidth for a pair of 10G links. After check the code, it seems on openvswitch 2.5.0, HAVE_METADATA_DST macro

Re: [ovs-discuss] [vxlan]openvswitch-2.5.0 coredump issue

On Tue, Oct 18, 2016 at 5:53 AM, Huanglili (lee) wrote: > Hi, all: > > I have met a core dump issue when I ifconfig down vxlan-port > durning sending vxlan packets. > > We know that when ifconfig down vxlan port, the udp socket will be > freed, but vxlan_xmit_one will still using

[ovs-discuss] [vxlan]openvswitch-2.5.0 coredump issue

Hi, all: I have met a core dump issue when I ifconfig down vxlan-port durning sending vxlan packets. We know that when ifconfig down vxlan port, the udp socket will be freed, but vxlan_xmit_one will still using the socket to do the send action, and then a NULL is read.

Re: [ovs-discuss] VXLAN doesn't work in OVS-DPDK

Regards _Sugesh From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of zhi Sent: Thursday, October 13, 2016 11:29 AM To: discuss@openvswitch.org Subject: [ovs-discuss] VXLAN doesn't work in OVS-DPDK hi, all I configured native tunneling by this guide[1]. And follow this gu

[ovs-discuss] VXLAN doesn't work in OVS-DPDK

hi, all I configured native tunneling by this guide[1]. And follow this guide[2] to install OVS-DPDK. The OVS version is 2.6.0. The DPDK version is dpdk-16.07. My local Linux environment is CentOS 7.1.1503 and the kernel version is 3.10.0-327.el7.x86_64. And the network topology shows below: [i

Re: [ovs-discuss] vxlan over IPv6

HI，does support for IPv6 tunneling backport to the OVS out-of-tree kernel module for now? On 01/25/2016 23:53, Jesse Gross wrote: On Sat, Jan 23, 2016 at 3:59 AM, zhangqunjian wrote: > > Hi, I use OVS created vxlan tunnel based on IPv6. As far as I know, GitHub > master branch has been commi

Re: [ovs-discuss] vxlan over IPv6

No, the situation is the same as before. I think you'll have to wait until the OVS 2.6 release later this year. On Wed, Jul 6, 2016 at 4:56 AM, zhangqunjian wrote: > > > HI，does support for IPv6 tunneling backport to the OVS out-of-tree kernel > module for now? > On 01/25/2016 23:53, Jesse Gross

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

On Thu, Feb 25, 2016 at 5:14 AM, kldeng wrote: > Hi, ALL. > > Recently, we're trying to fix the poor VXLAN throughput issue by applying > the series of patches @Ramu posted in ovs-dev mailing-list. > http://openvswitch.org/pipermail/dev/2015-August/059337.html > > Our test environment are as below

[ovs-discuss] vxlan udp csum and openstack ovs performance

Hi, ALL. Recently, we're trying to fix the poor VXLAN throughput issue by applying the series of patches @Ramu posted in ovs-dev mailing-list. http://openvswitch.org/pipermail/dev/2015-August/059337.html Our test environment are a

[ovs-discuss] vxlan udp csum and openstack ovs performance

Hi, ALL. Recently, we're trying to fix the poor VXLAN throughput issue by applying the series of patches @Ramu posted in ovs-dev mailing-list. http://openvswitch.org/pipermail/dev/2015-August/059337.html Our test environment are as belows. -- OVS: 2.4.0

Re: [ovs-discuss] vxlan over IPv6

On Sat, Jan 23, 2016 at 3:59 AM, zhangqunjian wrote: > > Hi, I use OVS created vxlan tunnel based on IPv6. As far as I know, GitHub > master branch has been commited part code of this function. when I used it > into my project，I found that vxlan over IPv6 configuration is working > properly，but f

[ovs-discuss] vxlan over IPv6

Hi, I use OVS created vxlan tunnel based on IPv6. As far as I know, GitHub master branch has been commited part code of this function. when I used it into my project，I found that vxlan over IPv6 configuration is working properly，but function worked not well. I built the vxlan tunnel over IPv6

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

Jan 22, 2016 12:49 PM > To: "康敬亭"; > Cc: "discuss"; > Subject: Re: [ovs-discuss] vxlan udp csum and openstack ovs performance > > On Thu, Jan 21, 2016 at 7:41 PM, 康敬亭 wrote: >> Hi Gross: >> Thank you for your reply. >> I know that OVS2

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

uss"; Subject: Re: [ovs-discuss] vxlan udp csum and openstack ovs performance On Thu, Jan 21, 2016 at 7:41 PM, 康敬亭 wrote: > Hi Gross: > Thank you for your reply. > I know that OVS2.4 already supports vxlan csum，and I create a port in > accordance with the following comman

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

On Thu, Jan 21, 2016 at 7:41 PM, 康敬亭 wrote: > Hi Gross: > Thank you for your reply. > I know that OVS2.4 already supports vxlan csum，and I create a port in > accordance with the following command: > “ovs-vsctl add-port ovs-vx vxlan0 -- set interface vxlan0 type=vxlan > options:remote_i

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

-- eth3（10.0.28.65）《-- Best wish！ -- Original -- From: "Jesse Gross"; Date: Fri, Jan 22, 2016 01:08 AM To: "康敬亭"; Cc: "discuss"; Subject: Re: [ovs-discuss] vxlan udp csum and openstack ovs performance On Wed, Jan 20, 2016

Re: [ovs-discuss] vxlan udp csum and openstack ovs performance

On Wed, Jan 20, 2016 at 11:41 PM, 康敬亭 wrote: > Hi ALL： >We are running openstack J with neutron OVS2.4 using intel 10G > adapters(82599es) with vxlan tunnels. >We find this patch below to resolve problem of vxlan throughput. > http://openvswitch.org/pipermail/dev/2015-August/059335.ht

[ovs-discuss] vxlan udp csum and openstack ovs performance

Hi ALL： We are running openstack J with neutron OVS2.4 using intel 10G adapters(82599es) with vxlan tunnels. We find this patch below to resolve problem of vxlan throughput. http://openvswitch.org/pipermail/dev/2015-August/059335.html We modify vport-vxlan.c as the patch，and mak

Re: [ovs-discuss] Vxlan encapsulation exceeds the MTU of dpdk port .

On 2015/7/1 22:57, Kavanagh, Mark B wrote: As following topology, two VMs communicate via Vxlan tunnel. TCP pkts may be droped for exceeding the mtu of host DPDK port in br2. Now I can change the VMs' mtu from default to smaller to accommodate the traffics, it works well. The way I have not fin

Re: [ovs-discuss] Vxlan encapsulation exceeds the MTU of dpdk port .

>As following topology, two VMs communicate via Vxlan tunnel. >TCP pkts may be droped for exceeding the mtu of host DPDK port in br2. >Now I can change the VMs' mtu from default to smaller to accommodate the >traffics, it works well. > >The way I have not find to change mtu of DPDK phy port, is the

[ovs-discuss] Vxlan encapsulation exceeds the MTU of dpdk port .

As following topology, two VMs communicate via Vxlan tunnel. TCP pkts may be droped for exceeding the mtu of host DPDK port in br2. Now I can change the VMs' mtu from default to smaller to accommodate the traffics, it works well. The way I have not find to change mtu of DPDK phy port, is there

Re: [ovs-discuss] VxLAN kernel module.

On Thu, Mar 12, 2015 at 2:29 AM, Sudipto Biswas wrote: > Hi Pravin, Fan Du, > > Appreciate your help. > > To conclude, for VxLAN to work on Kernel 3.10 - do I need to explicitly load > the vxlan.ko and then re-build OVS to make use of it? > > I can see that CONFIG_VXLAN is set to 'm' > > Do I need

Re: [ovs-discuss] VxLAN kernel module.

To correct myself, will unloading and re-loading the openvswitch module reference the vxlan.ko module automatically, if it's loaded? Thanks, Sudipto On Thursday 12 March 2015 02:59 PM, Sudipto Biswas wrote: Hi Pravin, Fan Du, Appreciate your help. To conclude, for VxLAN to work on Kernel 3.10

Re: [ovs-discuss] VxLAN kernel module.

Hi Pravin, Fan Du, Appreciate your help. To conclude, for VxLAN to work on Kernel 3.10 - do I need to explicitly load the vxlan.ko and then re-build OVS to make use of it? I can see that CONFIG_VXLAN is set to 'm' Do I need to re-build OVS to use this module? (after i have used modprobe to

Re: [ovs-discuss] VxLAN kernel module.

On Wednesday 11 March 2015 12:36 PM, Sudipto Biswas wrote: On Wednesday 11 March 2015 12:12 PM, Fan Du wrote: 于 2015年03月11日 14:42, Sudipto Biswas 写道: On Wednesday 11 March 2015 11:35 AM, Fan Du wrote: 于 2015年03月11日 01:38, Sudipto Biswas 写道: Hi, I have a very small query. I am using OVS 2.

Re: [ovs-discuss] VxLAN kernel module.

On Wednesday 11 March 2015 12:12 PM, Fan Du wrote: 于 2015年03月11日 14:42, Sudipto Biswas 写道: On Wednesday 11 March 2015 11:35 AM, Fan Du wrote: 于 2015年03月11日 01:38, Sudipto Biswas 写道: Hi, I have a very small query. I am using OVS 2.3.1 and i have built the kernel module etc following the ins

Re: [ovs-discuss] VxLAN kernel module.

On Wednesday 11 March 2015 11:35 AM, Fan Du wrote: 于 2015年03月11日 01:38, Sudipto Biswas 写道: Hi, I have a very small query. I am using OVS 2.3.1 and i have built the kernel module etc following the instructions in the INSTALL file. I was also, able to create vxlan ports and communicate across

Re: [ovs-discuss] VxLAN kernel module.

于 2015年03月11日 01:38, Sudipto Biswas 写道: Hi, I have a very small query. I am using OVS 2.3.1 and i have built the kernel module etc following the instructions in the INSTALL file. I was also, able to create vxlan ports and communicate across two VMs on two different machines using VxLAN tunnel

Re: [ovs-discuss] VxLAN kernel module.

On Tue, Mar 10, 2015 at 10:38 AM, Sudipto Biswas wrote: > Hi, > > I have a very small query. I am using OVS 2.3.1 and i have built the kernel > module etc following the instructions in the INSTALL file. > > I was also, able to create vxlan ports and communicate across two VMs on two > different ma

Re: [ovs-discuss] VXLAN tunnel incoming packets are not captured on mirror port

Hi, I am too facing the same issue. Can you please tell me how you resolved it? Thanks, Priyanka ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss

[ovs-discuss] VxLAN Flow setup not working.

Hi, I have a basic query. I have 2 machines with OVS 2.3.1 on it. I have done the following to create a VxLAN tunnel: ovs-vsctl add-port br0 vxlan -- set interface vxlan type=vxlan options:remote_ip= After this, I have created a virtual machine using virsh on the OVS bridge br0. Following t

Re: [ovs-discuss] VXLAN tunnels and routing

Message- > From: Jesse Gross [mailto:je...@nicira.com ] > Sent: Sunday, December 21, 2014 17:48 > To: Tal Yaniv > Cc: discuss@openvswitch.org > Subject: Re: [ovs-discuss] VXLAN tunnels and routing > > On Sun, Dec 21, 2014 at 5:39 AM, Tal Yaniv > wrote: > > Hi,

Re: [ovs-discuss] VXLAN tunnels and routing

@openvswitch.org Subject: Re: [ovs-discuss] VXLAN tunnels and routing On Sun, Dec 21, 2014 at 5:39 AM, Tal Yaniv wrote: > Hi, > > > > I’d like Linux network stack to handle my routing, if I define an OVS > bridge, with several interfaces (eth0-eth2) , which are on different &g

Re: [ovs-discuss] VXLAN tunnels and routing

On Sun, Dec 21, 2014 at 5:39 AM, Tal Yaniv wrote: > Hi, > > > > I’d like Linux network stack to handle my routing, if I define an OVS > bridge, with several interfaces (eth0-eth2) , which are on different > networks. > > Plus, several VXLAN ports on the same bridge. > > And I define a flow with a

[ovs-discuss] VXLAN tunnels and routing

Hi, I'd like Linux network stack to handle my routing, if I define an OVS bridge, with several interfaces (eth0-eth2) , which are on different networks. Plus, several VXLAN ports on the same bridge. And I define a flow with a VXLAN encapsulation action and output to LOCAL (meaning to the Linux n

Re: [ovs-discuss] VXLAN under OVS

So I’m now using option:key=1 and 2 instead of key=flow. I’m attempting to tag 1 -> 2 with VNID 2, and 2 -> 1 with VNID 1. *** Setting VXLAN 1 -> 2 ovs-vsctl set bridge s1 protocols=OpenFlow13 ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan option:remote_ip=localhost option:key=1 ofport_

Re: [ovs-discuss] VXLAN under OVS

Sorry, I should have clarified, 172.16.4.1 is a dummy UDP server reflecting packets back to the sender (since localhost wasn’t working). Indeed VXLAN packets are arriving on the dummy server, though they’re not being accepted back by OVS. I was hoping to specify the VNID in flows as it much more dy

Re: [ovs-discuss] VXLAN under OVS

#switch 1 sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan option:remote_ip=172.16.4.1 option:key=flow ofport_request=11 sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1' sh ovs-ofctl add-flow s1 'in_port=1,actions=set_field:1->tun_id,output:11' #switch 2 sh ovs-vsctl add

Re: [ovs-discuss] VXLAN under OVS

On Wed, Sep 24, 2014 at 11:07:06AM +1000, Jaime Pillora wrote: > #switch 1 > sh ovs-vsctl add-port s1 vx1 -- set interface vx1 type=vxlan > option:remote_ip=172.16.4.1 option:key=flow ofport_request=11 > sh ovs-ofctl add-flow s1 'in_port=11,tun_id=2,actions=output:1' > sh ovs-ofctl add-flow s1 'in_

Re: [ovs-discuss] VXLAN under OVS

On Mon, Sep 22, 2014 at 11:13:45AM +1000, Jaime Pillora wrote: > I???ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the > first VXLAN port I create works. Is this a bug or am I only able to use one > VXLAN port for each OVS instance? It's probably a configuration error. How did

[ovs-discuss] VXLAN under OVS

I’ve added a VXLAN ports to vx1,2 to bridges s1,2 and it seems only the first VXLAN port I create works. Is this a bug or am I only able to use one VXLAN port for each OVS instance? Jaime ___ discuss mailing list discuss@openvswitch.org http://openvswitch

[ovs-discuss] VXLAN is not getting loaded in openvswitch-2.1.2

Hi, I have compiled and installed openvswitch-2.1.2 source code on Fedora machine version 3.11.10-301.fc20.x86_64. As I can see gre module is getting loaded but I need vxlan module to be loaded which is not coming. Please help me out. Following is the command which I am using to display module

Re: [ovs-discuss] VXLAN problems

On Fri, May 16, 2014 at 5:31 AM, Jesse Gross wrote: > On Wed, May 14, 2014 at 6:33 PM, Han Zhou wrote: >> On Thu, May 15, 2014 at 8:07 AM, Jesse Gross wrote: >>> On Tue, May 13, 2014 at 6:29 PM, Han Zhou wrote: Hi Jesse, On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: >

Re: [ovs-discuss] VXLAN problems

On Wed, May 14, 2014 at 6:33 PM, Han Zhou wrote: > On Thu, May 15, 2014 at 8:07 AM, Jesse Gross wrote: >> On Tue, May 13, 2014 at 6:29 PM, Han Zhou wrote: >>> Hi Jesse, >>> >>> On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: > In

Re: [ovs-discuss] VXLAN problems

On Thu, May 15, 2014 at 8:07 AM, Jesse Gross wrote: > On Tue, May 13, 2014 at 6:29 PM, Han Zhou wrote: >> Hi Jesse, >> >> On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: >>> On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: In fact, MTU specified by VM doesn't make any sense in a virt

Re: [ovs-discuss] VXLAN problems

On Tue, May 13, 2014 at 6:29 PM, Han Zhou wrote: > Hi Jesse, > > On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: >> On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: >>> In fact, MTU specified by VM doesn't make any sense in a virtualized >>> environment. Maybe you can try this patch if you

Re: [ovs-discuss] VXLAN problems

@openvswitch.org Subject: Re: [ovs-discuss] VXLAN problems Hi Jesse, On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: > On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: >> In fact, MTU specified by VM doesn't make any sense in a virtualized >> environment. Maybe you can t

Re: [ovs-discuss] VXLAN problems

Hi Jesse, On Wed, May 14, 2014 at 5:05 AM, Jesse Gross wrote: > On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: >> In fact, MTU specified by VM doesn't make any sense in a virtualized >> environment. Maybe you can try this patch if you are interested: >> >> http://openvswitch.org/pipermail/de

Re: [ovs-discuss] VXLAN problems

On Tue, May 13, 2014 at 12:20 AM, Zhou, Han wrote: > In fact, MTU specified by VM doesn't make any sense in a virtualized > environment. Maybe you can try this patch if you are interested: > > http://openvswitch.org/pipermail/dev/2014-May/040027.html This message seems to be have been taken by my

Re: [ovs-discuss] VXLAN problems

On 5/13/14, 2:00 AM, Yinpeijun wrote: if needed, we should increase PYH NIC MTU or decrease VM NIC MTU ? Increase the physical NIC MTU to 1550; this will be more compatible since the VMs will be able to use standard 1500 MTU. Be sure the physical switches have jumbo frames enabled. -- Wes

Re: [ovs-discuss] VXLAN problems

Hi Yinpeijun, On Tue, 2014-05-13 at 02:13 +, Yinpeijun wrote: > >Date: Thu, 19 Dec 2013 14:45:33 +0100 > >From: Igor Sever > >Subject: Re: [ovs-discuss] VXLAN problems > >To: Jesse Gross > >Cc: "discuss@openvswitch.org" > >Message-ID: > >

Re: [ovs-discuss] VXLAN problems

>> >This is due to the tunnel outer header that adds VXLAN + UDP + IP + ETH = >> >50 bytes to the inner packets. When TCP stream is tested between VMs, TCP >> >buffer is segmented to 1500 bytes, but with outer header added, it will be >> >1550 that slightly exceed PHY NIC MTU, and results in an

Re: [ovs-discuss] VXLAN problems

Hi, On Tue, 2014-05-13 at 07:00 +, Yinpeijun wrote: > >> >Subject: Re: [ovs-discuss] VXLAN problems > >> >To: Jesse Gross > >> >Cc: "discuss@openvswitch.org" > >> >Message-ID: > >> > > >> > > >&

Re: [ovs-discuss] VXLAN problems

>> >Subject: Re: [ovs-discuss] VXLAN problems >> >To: Jesse Gross >> >Cc: "discuss@openvswitch.org" >> >Message-ID: >> > >> > >> >Content-Type: text/plain; charset="iso-8859-1" >> > >> >I man

Re: [ovs-discuss] VXLAN problems

Hi Yinpeijun, On Tue, 2014-05-13 at 02:13 +, Yinpeijun wrote: > >Date: Thu, 19 Dec 2013 14:45:33 +0100 > >From: Igor Sever > >Subject: Re: [ovs-discuss] VXLAN problems > >To: Jesse Gross > >Cc: "discuss@openvswitch.org" > >Message-ID: > >

Re: [ovs-discuss] VXLAN problems

>Date: Thu, 19 Dec 2013 14:45:33 +0100 >From: Igor Sever >Subject: Re: [ovs-discuss] VXLAN problems >To: Jesse Gross >Cc: "discuss@openvswitch.org" >Message-ID: > >Content-Type: text/plain; charset="iso-8859-1" > >I managed to solve this

[ovs-discuss] vxlan configuration remote_ip=flow

the configuration of vxlan with remote_ip=flow return vxlan type requires valid 'remote_ip' argument what's the problem please BR ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss

Re: [ovs-discuss] VXLAN problems

I managed to solve this by setting VM NIC MTU to 1400, 1450 wasn't enough. Thanks. ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss

Re: [ovs-discuss] VXLAN problems

On Wed, Dec 18, 2013 at 12:19 AM, Igor Sever wrote: > I tried to implement tunneling between KVM virtual machines on two hosts > that are using public IP-s but are on the same LAN (Hetzner provider). > Virtual machines on both hosts are using same private 192. network. > > I installed and configur

[ovs-discuss] VXLAN problems

I tried to implement tunneling between KVM virtual machines on two hosts that are using public IP-s but are on the same LAN (Hetzner provider). Virtual machines on both hosts are using same private 192. network. I installed and configured Open vSwitch 2.0.0 on Centos 6.5. Standard networking, brid

Re: [ovs-discuss] VXLAN using OVS

I didn't check before. thanks a lot ... kyle :) On Tue, Oct 22, 2013 at 10:22 PM, Kyle Mestery (kmestery) < kmest...@cisco.com> wrote: > On Oct 22, 2013, at 2:15 AM, Romil Gupta wrote: > > > > Hi All, > > > > We are using OVS as neutron plugin to use VLAN/ VXLAN. We found that OVS > does mu

Re: [ovs-discuss] VXLAN using OVS

On Tue, Oct 22, 2013 at 9:52 AM, Kyle Mestery (kmestery) wrote: > On Oct 22, 2013, at 2:15 AM, Romil Gupta wrote: >> >> Hi All, >> >> We are using OVS as neutron plugin to use VLAN/ VXLAN. We found that OVS >> does multiple unicast to send the ARP request instead of sending via >> Multicast add

Re: [ovs-discuss] VXLAN using OVS

On Oct 22, 2013, at 2:15 AM, Romil Gupta wrote: > > Hi All, > > We are using OVS as neutron plugin to use VLAN/ VXLAN. We found that OVS does > multiple unicast to send the ARP request instead of sending via Multicast > address. But by default Linux bridge supports Multicast. > > Is there any

[ovs-discuss] VXLAN using OVS

Hi All, We are using OVS as neutron plugin to use VLAN/ VXLAN. We found that OVS does multiple unicast to send the ARP request instead of sending via Multicast address. But by default Linux bridge supports Multicast. Is there any reason behind why OVS doesn't support Multicast? Thanks in Advance

Re: [ovs-discuss] vxlan remote_ip flow help

On Tue, Sep 10, 2013 at 06:28:18PM +0300, Andrei Andone wrote: > The problem was I had the tunnel configured as follows: > ovs-vscl add-port br-vnet tun-port -- set Interface tun-port > type=... options:remote_ip=*flow* options:key=*20 > > *After looking into the code for flow matching I decided t

Re: [ovs-discuss] vxlan remote_ip flow help

Hello all, I finally figured out what my problem was. As I was saying in the previous post, I thought that the tunnel does not get identified by the bridge. Seems that I was right. The problem was I had the tunnel configured as follows: ovs-vscl add-port br-vnet tun-port -- set Interface tun-p

Re: [ovs-discuss] vxlan remote_ip flow help

Hello, Host 2 is configured with options:remote_ip=192.168.56.142 (host 1 IP). But I don't think that host 2 is the problem since on host 1 I can see the arp reply packets coming in on br-eth0 and on eth0. I do not see the reply packet being forwarded to the vm's port (vnet0). I'm attaching

Re: [ovs-discuss] vxlan remote_ip flow help

On Mon, Sep 9, 2013 at 5:14 AM, Andrei Andone wrote: > Hello Jesse, > > I tried what you said and to only deal with the br-vnet bridge. I also > switched to GRE tunnels for ease of viewing packets. Here's how it went: > > First config (host h1): > > > [root@localhost ~]# ovs-vsctl show > 0383aec

Re: [ovs-discuss] vxlan remote_ip flow help

Hello Jesse, I tried what you said and to only deal with the br-vnet bridge. I also switched to GRE tunnels for ease of viewing packets. Here's how it went: First config (host h1): [root@localhost ~]# ovs-vsctl show 0383aece-fb49-47ab-b9d2-c1ee13c16a89 Bridge br-vnet Port "vnet0"

Re: [ovs-discuss] vxlan remote_ip flow help

It shouldn't matter that you have two bridges, the only one that applies in this case is br_vnet. I would use ovs-appctl dpif/dump-flows and ofproto/trace to debug where your packets are currently going and then write a flow to match using fields such as tun_id, tun_src, etc. similar to what you ar

Re: [ovs-discuss] vxlan remote_ip flow help

Hello Jesse, Sorry for the delay on my reply, I couldn't reply any sooner. To answer your question: No, I don't have a flow for receiving, because I couldn't really understand where I'm supposed to add the flow and how it should look like. I've seen examples with only one bridge but I'm using

Re: [ovs-discuss] vxlan remote_ip flow help

Do you have a corresponding flow to receive the VXLAN traffic? You only showed one for sending. As you mentioned before, you should be able to use ofproto/trace to see what OpenFlow rules are being hit. On Wed, Aug 28, 2013 at 4:48 AM, Andrei Andone wrote: > Hello Jesse, > > Yes, on Wireshark

Re: [ovs-discuss] vxlan remote_ip flow help

Hello Jesse, Yes, on Wireshark listening to eth0, I see udp packets being sent and received between the hosts (udp, destination port: 4789, which is vxlan port). So the hosts are comunicating (the tunnel is) but I can't see any reply on my br-vnet wireshark, or my VM receiving the answer that

Re: [ovs-discuss] vxlan remote_ip flow help

On Tue, Aug 27, 2013 at 5:51 AM, Andrei Andone wrote: > Hello guys, > > I have a question related to the "options:remote_ip=flow" feature. > > My config looks like this for one host: > > [root@localhost ~]# ovs-vsctl show > e927ea5a-41d8-4bf5-9145-5be06e18bc9f > Bridge "br-eth0" > Por

[ovs-discuss] vxlan remote_ip flow help

Hello guys, I have a question related to the "options:remote_ip=flow" feature. My config looks like this for one host: [root@localhost ~]# ovs-vsctl show e927ea5a-41d8-4bf5-9145-5be06e18bc9f Bridge "br-eth0" Port "br-eth0" Interface "br-eth0" type: intern

[ovs-discuss] Vxlan support in OVS.

Hi, Please let me know if we want to use VXLAN for OVS 1.10 or more version. What is the best Linux Kernel to use. Does it have any dependency on Linux - VxLan support / Kernel version number?. Regards, Balaji.P ___ discuss mailing list discuss@openvs

Re: [ovs-discuss] VXLAN tunnel issue

Thanks Kyle. I guess i was not following the instructions in the INSTALL file correctly. It is working now, thanks for the help. On Tue, Jul 30, 2013 at 2:43 PM, Kyle Mestery (kmestery) wrote: > On Jul 30, 2013, at 6:43 AM, Shahryar Ali wrote: > > > > Thanks for the reply Kyle. Here is the out

Re: [ovs-discuss] VXLAN tunnel issue

Thanks for the reply Kyle. Here is the output of the modinfo openvswitch: # modinfo openvswitch filename: /lib/modules/3.8.0-27-generic/kernel/net/openvswitch/openvswitch.ko license:GPL description:Open vSwitch switching datapath srcversion: 15C32AD9E04F379CAC3D68E depends: intree:

[ovs-discuss] VXLAN tunnel issue

Hi i am newbie in Openvswitch and trying to create a VXLAN tunnel. I am having issue in connectivity. I am not able to ping the isolated bridges through VXLAN tunnel. The tunnel end points do have the connectivity. Here is my configuration: Host 1: Bridge "br0" Port "br0" Inte

Re: [ovs-discuss] VXLAN

Hi Kyle, it's working now, not sure where the problem in the first place was. Thanks, for your help. -martin On 03.03.2013 03:25, Kyle Mestery (kmestery) wrote: > On Mar 2, 2013, at 2:29 PM, Martin Mailand wrote: >> Hi Kyle, >> >> I found the patch and applied it. So far so good, gre tunnel ar

Re: [ovs-discuss] VXLAN

On Mar 2, 2013, at 2:29 PM, Martin Mailand wrote: > Hi Kyle, > > I found the patch and applied it. So far so good, gre tunnel are still > working, but I cannot get a vxlan tunnel to work. > > I tried the following command. > > ovs-vsctl add-port br-tun vx1 -- set interface vx1 type=vxlan > opti

Re: [ovs-discuss] VXLAN

Hi Kyle, I found the patch and applied it. So far so good, gre tunnel are still working, but I cannot get a vxlan tunnel to work. I tried the following command. ovs-vsctl add-port br-tun vx1 -- set interface vx1 type=vxlan options:remote_ip=192.168.194.1 I get this error. 2013-03-02T20:10:40Z|

Re: [ovs-discuss] VXLAN

On Mar 1, 2013, at 8:26 AM, Martin Mailand wrote: > Hi Kyle, > > thanks for the quick response, where could I find this patch? > The latest version (v7) was posted to the dev list yesterday I believe. > -martin > > On 01.03.2013 15:18, Kyle Mestery (kmestery) wrote: >> On Mar 1, 2013, at 6:54

Re: [ovs-discuss] VXLAN

Hi Kyle, thanks for the quick response, where could I find this patch? -martin On 01.03.2013 15:18, Kyle Mestery (kmestery) wrote: > On Mar 1, 2013, at 6:54 AM, Martin Mailand wrote: >> Hi, >> >> are there any updates regarding the patch for VXLAN? >> > VXLAN should be stable and working on mas

Re: [ovs-discuss] VXLAN

On Mar 1, 2013, at 6:54 AM, Martin Mailand wrote: > Hi, > > are there any updates regarding the patch for VXLAN? > VXLAN should be stable and working on master and 1.10 again once one additional patch from Pravin (with the title "Tunnel: Cleanup old tunnel infrastructure") goes into main. I've

Re: [ovs-discuss] VXLAN

Hi, are there any updates regarding the patch for VXLAN? -martin On 22.02.2013 17:48, Jesse Gross wrote: > On Fri, Feb 22, 2013 at 7:22 AM, Martin Mailand wrote: >> Hi, >> >> after a bit of try and error everything is working now, except for vxlan. >> I found in the devel mail archive, that it

Re: [ovs-discuss] VXLAN implementation in OVS

Thank you so much Kyle for the quick response. I will surely check in the NVO3 group. Best Regards, Sudhakar. On Wed, Nov 7, 2012 at 7:52 PM, Kyle Mestery (kmestery) wrote: > On Nov 7, 2012, at 7:01 AM, Sudhakar Gariganti < > sudhakar.gariga...@gmail.com> wrote: > > > > Hi Friends, > > > > I

Re: [ovs-discuss] VXLAN implementation in OVS

On Nov 7, 2012, at 7:01 AM, Sudhakar Gariganti wrote: > > Hi Friends, > > I am trying to understand the VXLAN spec and stumbled on how multicasting is > being used in the communication of VMs across tenants. I want to understand > how this is being implemented > in the current OVS- VXLAN imp

[ovs-discuss] VXLAN implementation in OVS

Hi Friends, I am trying to understand the VXLAN spec and stumbled on how multicasting is being used in the communication of VMs across tenants. I want to understand how this is being implemented in the current OVS- VXLAN implementation. I came across this link http://openvswitch.org/pipermail/dev

Re: [ovs-discuss] vxlan and vdp with OVS

On Wed, Aug 22, 2012 at 02:14:00PM -0700, Milton Xu wrote: > In the link you included, it is about "How to Submit Patches for Open > vSwitch" so I assume "Patch" means functionality addition as well. "Patch" refers to the format of the submission, not the content. All changes should be submitted

Re: [ovs-discuss] vxlan and vdp with OVS

* Milton Xu (mi...@yahoo.com) wrote: > VDP stands for VSI discovery and configuration protocol as specified in IEEE > P802.1Qbg draft. VDP (on linux) is supported via the userspace daemon, lldpad. The way it's typically used is in conjuction with libvirt and a special purpose switch called macvt

Re: [ovs-discuss] vxlan and vdp with OVS

On Aug 22, 2012, at 2:14 PM, Milton Xu wrote: > VDP stands for VSI discovery and configuration protocol as specified in IEEE > P802.1Qbg draft. I don't know of anyone working to add support for this. > In the link you included, it is about "How to Submit Patches for Open > vSwitch" so I assum

Re: [ovs-discuss] vxlan and vdp with OVS

ion as well. Milton From: Ben Pfaff To: Milton Xu Cc: "discuss@openvswitch.org" Sent: Tuesday, August 21, 2012 9:48 PM Subject: Re: [ovs-discuss] vxlan and vdp with OVS On Tue, Aug 21, 2012 at 05:10:03PM -0700, Milton Xu wrote: > Does anybody know when vxlan wil

Re: [ovs-discuss] vxlan and vdp with OVS

On Tue, Aug 21, 2012 at 05:10:03PM -0700, Milton Xu wrote: > Does anybody know when vxlan will be supported in OVS?  I got the same > question for VDP as well. What is VDP? > BTW, what is the process of adding functionality to OVS?  I see the > following general statement in the ovs site: See ht

[ovs-discuss] vxlan and vdp with OVS

Hi, Does anybody know when vxlan will be supported in OVS?  I got the same question for VDP as well. BTW, what is the process of adding functionality to OVS?  I see the following general statement in the ovs site: "Open vSwitch is developed as an open source project under the Apache 2 license*

Re: [ovs-discuss] VXLAN: How to pass VNI while setting up VXLAN Tunnel

As Ben mentioned, VXLAN isn't merged yet into the main codebase--the patch is currently being reworked--so we can't support it. In the meantime, I'd recommend using GRE, which should do everything you need and has been supported by OVS for a long time, so the interfaces are more stable. --Just

[ovs-discuss] VXLAN: How to pass VNI while setting up VXLAN Tunnel

HiI could set up vxlan tunnel across 2 hosts- sudo ovs-vsctl add-port br0 vx0 -- set interface vx0 type=vxlan options:remote_ip=10.0.0.2I am looking at a way by which I can pass VNI (VXLAN NETWORK IDENTIFIER) while setting tp this tunnel;I tried with following command that is accepted.- sudo ovs-v

  1   2   >