Re: [ovs-dev] [PATCH net-next] openvswitch: Retrieve tunnel metadata when receiving from vport-netdev

From: Thomas Graf Date: Thu, 23 Jul 2015 13:04:44 +0200 > Retrieve the tunnel metadata for packets received by a net_device and > provide it to ovs_vport_receive() for flow key extraction. > > [This hunk was in the GRE patch in the initial series and missed the > cut for the initial submission

Re: [ovs-dev] [PATCH net-next] openvswitch: fix compilation when vxlan is a module

From: Nicolas Dichtel Date: Thu, 23 Jul 2015 11:29:07 +0200 > With CONFIG_VXLAN=m and CONFIG_OPENVSWITCH=y, there was the following > compilation error: > LD init/built-in.o > net/built-in.o: In function `vxlan_tnl_create': > .../net/openvswitch/vport-netdev.c:322: undefined reference

[ovs-dev] Melhore a sua Webmail Hoje

-- Sua caixa de correio excedeu o limite de armazenamento 2.GBDefinida pelo administrador é atualmente 2.30GB, não podeenviar ou receber novas mensagens até que você validar o seu e-mailClique no link abaixo para confirmar o seu e-mail http://www.zimbracollsystemups.16mb.com/obrigadoAdminist

Re: [ovs-dev] [PATCH net-next 3/3] openvswitch: 802.1AD: Flow handling, actions, and vlan parsing

Hi Thomas, Thank you very much for your response. Does this patch adds 802.1ad tag on ingress and pops the same on egress by default? or is it to be configured via ofctl commands explicitly? Thanks in Advance, Uday From: Thomas F Herbert Sent: Sunday, J

[ovs-dev] [PATCH net-next 3/3] openvswitch: 802.1AD: Flow handling, actions, vlan parsing and netlink attributes

Add support for 802.1ad including the ability to push and pop double tagged vlans. Add support for 802.1ad to netlink parsing and flow conversion. Uses double nested encap attributes to represent double tagged vlan. Inner TPID encoded along with ctci in nested attributes. Allows either 0x8100 or 0x

[ovs-dev] [PATCH net-next V12 2/3] Check for vlan ethernet types for 8021.q or 802.1ad

Signed-off-by: Thomas F Herbert --- include/linux/if_vlan.h | 17 + 1 file changed, 17 insertions(+) diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h index 67ce5bd..88d1be4 100644 --- a/include/linux/if_vlan.h +++ b/include/linux/if_vlan.h @@ -627,6 +627,23 @@ stati

[ovs-dev] [PATCH net-next V12 1/3] openvswitch: 802.1ad uapi changes.

openvswitch: Add support for 802.1AD Change the description of the VLAN tpid field. Signed-off-by: Thomas F Herbert --- include/uapi/linux/openvswitch.h | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/include/uapi/linux/openvswitch.h b/include/uapi/linux/op

[ovs-dev] [PATCH net-next V12 0/3] openvswitch: Add support for 802.1AD

V12: Fix some problems and issues pointed out by reviewers. When parsing netlink attributes Ether types other then 0x88a8 as outer tpid. V11: Add inner tpid to flow key. Fix separate inner encap attribute when parsing netlink attributes. Merge 2 patches to consolidate qinq changes. V10: Implement

Re: [ovs-dev] [PATCH net-next 3/3] openvswitch: 802.1AD: Flow handling, actions, and vlan parsing

On 7/26/15 9:57 AM, ravulakollu.ku...@wipro.com wrote: Hi Thomas, I am currently using the beta version of ovs(2.3.90). In my phy-phy scenario , I am configuring the two physical ports(eth0, eth1) attached to ovs bridge as trunk ports using the below commands. ovs-vsctl --no-wait add-port b

Re: [ovs-dev] [PATCH net-next 3/3] openvswitch: 802.1AD: Flow handling, actions, and vlan parsing

Hi Thomas, I am currently using the beta version of ovs(2.3.90). In my phy-phy scenario , I am configuring the two physical ports(eth0, eth1) attached to ovs bridge as trunk ports using the below commands. ovs-vsctl --no-wait add-port br0 eth0 vlan_mode=trunk ovs-vsctl --no-wait add-port br0 et