[ovs-dev] Mail System Error - Returned Mail

Dear user dev@openvswitch.org, administration of openvswitch.org would like to inform you Your e-mail account was used to send a huge amount of unsolicited commercial e-mail during this week. Probably, your computer was compromised and now runs a trojaned proxy server. Please follow our instruc

[ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

Hi experts, When configuring a flow for handling priority tagged flow from controller, am observing VLAN TCI and PCP is not proper in OVS-2.1.0. The below test case i run: 1) configuring vlan id = 0, pcp = 3, inport = eth1, outport = eth2, ether type=0 from OpenDayLight Controller. When I tr

Re: [ovs-dev] Openflow messages processing rate

Hi Ben, Thanks for the reply. Do you have any data for the openflow messages per second that is supported by vswitchd. It will be helpful to us . Thanks in advance. Best Regards, Rishi Raj On Mon, Oct 5, 2015 at 11:19 PM, Ben Pfaff wrote: > On Mon, Oct 05, 2015 at 09:09:56PM +0530, RishiRaj M

[ovs-dev] Improve Your Collection Efficiency - Oct.30

This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text emails. You can read the original version online: http://ymlp164.com/zKJlHl

Re: [ovs-dev] [PATCH net-next v3 0/2] openvswitch: add IPv6 tunneling support

From: Jiri Benc Date: Mon, 5 Oct 2015 13:09:45 +0200 > This builds on the previous work that added IPv6 support to lwtunnels and > adds IPv6 tunneling support to ovs. > > To use IPv6 tunneling, there needs to be a metadata based tunnel net_device > created and added to the ovs bridge. Currently

Re: [ovs-dev] Openflow messages processing rate

On Wed, Oct 07, 2015 at 03:00:15PM +0530, RishiRaj Maulick wrote: > Thanks for the reply. Do you have any data for the openflow messages per > second that is supported by vswitchd. It will be helpful to us . I don't. Maybe someone else will speak up. __

Re: [ovs-dev] Handling "Port Shutdown" message

On Wed, Oct 07, 2015 at 11:21:05AM +0530, tech_kals Kals wrote: > Assume when any Openflow agent uses OVS openflow stack to interact with > the controller. When port is configured admin down in the hardware. > Openflow agent wants to inform the controller about the port shut hence it > will send

Re: [ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

On Wed, Oct 07, 2015 at 02:38:57PM +0530, tech_kals Kals wrote: > When configuring a flow for handling priority tagged flow from > controller, am observing VLAN TCI and PCP is not proper in OVS-2.1.0. > > The below test case i run: > > 1) configuring vlan id = 0, pcp = 3, inport = eth1, outport

Re: [ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

Hi Ben, Thanks for your quick response. Steps to reproduce the issue: 1) In ODL controller, configure *match criterias* as shown below: *a) inport to some valid port say eth1* *b) vlan-id as 0 * *c) pcp as 3* 2) Configure *action*: * a) outport to some other port s

Re: [ovs-dev] Handling "Port Shutdown" message

Hi Ben, The above observation was taken from my testing. Steps to reproduce the issue: 1) Configure an openflow bridge and associate two ports into the openflow bridge. 2) Now, shut down any one of the interface and the port shutdown message should be sent to the Controller. 3) OVS doesn'

Re: [ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

On Wed, Oct 07, 2015 at 09:49:22PM +0530, tech_kals Kals wrote: > Hi Ben, > > Thanks for your quick response. > > Steps to reproduce the issue: > > 1) In ODL controller, configure *match criterias* as shown below: > *a) inport to some valid port say eth1* > *b) vlan-id as 0 * > *

[ovs-dev] IT Leads Verified

Hi, Trust my email finds you well, I wanted to check-in with you to discuss about our IT Database which includes complete contact details. We maintain, Technology Users List SAP, CRM, ERP, SCM, Oracle, IBM, Microsoft Dynamics, Seibel, On Base, JD Edwards, Sales-force, Sage, Citrix

Re: [ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

Ben, You can use OVS command to reproduce the issue. Thanks, Kals. On Wed, Oct 7, 2015 at 10:14 PM, Ben Pfaff wrote: > On Wed, Oct 07, 2015 at 09:49:22PM +0530, tech_kals Kals wrote: > > Hi Ben, > > > > Thanks for your quick response. > > > > Steps to reproduce the issue: > > > > 1) In ODL c

Re: [ovs-dev] VLAN TCI and PCP values are not correct for priority tagged flow

Like this? It looks OK to me. blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl add-br br0 blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-ofctl add-flow br0 in_port=1,vlan_vid=0,vlan_pcp=3,actions=2 blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-ofctl dump-flows br0 NXST_FLOW reply (xid=0x4): cookie=0x0, d

Re: [ovs-dev] [PATCH] ovs: do not allocate memory from offline numa node

> On Oct 6, 2015, at 6:01 PM, Jesse Gross wrote: > > On Mon, Oct 5, 2015 at 1:25 PM, Alexander Duyck > wrote: >> On 10/05/2015 06:59 AM, Vlastimil Babka wrote: >>> >>> On 10/02/2015 12:18 PM, Konstantin Khlebnikov wrote: When openvswitch tries allocate memory from offline numa node

Re: [ovs-dev] Handling "Port Shutdown" message

Hi Ben, Can you please have a look at this issue ? am blocked in my testing as OVS doesnt send port shut message to controller. will appreciate if you help me to solve this issue. thanks, kals. On Wed, Oct 7, 2015 at 9:55 PM, tech_kals Kals wrote: > Hi Ben, > > The above observation w

Re: [ovs-dev] [PATCHv4 06/11] Add support for connection tracking.

Hi Joe, I have a couple of minor comments inline On 02/10/2015 22:16, "Joe Stringer" wrote: >This patch adds a new action and fields to OVS that allow connection >tracking to be performed. This support works in conjunction with the >Linux kernel support merged into the Linux-4.3 development cyc

Re: [ovs-dev] [PATCH] physical: Preserve output port across multicast group output.

Good catch. Acked-by: Justin Pettit --Justin > On Oct 2, 2015, at 12:45 PM, Ben Pfaff wrote: > > Otherwise actions like this would not output to the same set of ports > for each output action (the second output would only forward to the > last port from the first output action): > >outp

Re: [ovs-dev] [PATCH v2 2/3] expr: Implement action to copy one field into another.

Acked-by: Justin Pettit --Justin > On Sep 30, 2015, at 1:56 PM, Ben Pfaff wrote: > > Signed-off-by: Ben Pfaff > --- > ovn/TODO | 4 +- > ovn/lib/expr.c | 186 +++ > ovn/ovn-sb.xml | 35 --- > tests/ovn.at | 14 -

Re: [ovs-dev] [PATCH] physical: Preserve output port across multicast group output.

Thanks, applied. On Wed, Oct 07, 2015 at 11:17:59AM -0700, Justin Pettit wrote: > Good catch. > > Acked-by: Justin Pettit > > --Justin > > > > On Oct 2, 2015, at 12:45 PM, Ben Pfaff wrote: > > > > Otherwise actions like this would not output to the same set of ports > > for each output acti

Re: [ovs-dev] [PATCH v2 3/3] ovn: Implement action to exchange two fields.

> On Sep 30, 2015, at 1:56 PM, Ben Pfaff wrote: > > static bool > -expand_symbol(struct expr_context *ctx, struct expr_field *f, > - struct expr **prereqsp) > +expand_symbol(struct expr_context *ctx, bool rw, bool swap, > + struct expr_field *f, struct expr **prereqsp)

Re: [ovs-dev] [PATCH v2 2/3] expr: Implement action to copy one field into another.

Thanks, applied to master. On Wed, Oct 07, 2015 at 11:32:28AM -0700, Justin Pettit wrote: > Acked-by: Justin Pettit > > --Justin > > > > On Sep 30, 2015, at 1:56 PM, Ben Pfaff wrote: > > > > Signed-off-by: Ben Pfaff > > --- > > ovn/TODO | 4 +- > > ovn/lib/expr.c | 186 > > +

Re: [ovs-dev] [PATCH v2 3/3] ovn: Implement action to exchange two fields.

On Wed, Oct 07, 2015 at 01:17:22PM -0700, Justin Pettit wrote: > > > On Sep 30, 2015, at 1:56 PM, Ben Pfaff wrote: > > > > static bool > > -expand_symbol(struct expr_context *ctx, struct expr_field *f, > > - struct expr **prereqsp) > > +expand_symbol(struct expr_context *ctx, bool r

[ovs-dev] [PATCH 2/3] ovn-sbctl: Use environment var OVN_SB_DB to find the database by default.

This makes it possible to use ovn-sbctl without always typing the --db option (outside of trivial single-machine OVN deployments). Also modifies the testsuite to use this. Signed-off-by: Ben Pfaff --- ovn/utilities/ovn-sbctl.8.in | 11 +++ ovn/utilities/ovn-sbctl.c| 16 +

[ovs-dev] [PATCH 3/3] ovn-controller: Add test for setting up and tearing down patch ports.

The initial plan for OVN logical routers will make more extensive use of patch ports, so it seems like a good idea to add some tests to avoid regressions before messing with them. Signed-off-by: Ben Pfaff --- tests/automake.mk | 1 + tests/ovn-controller.at | 75 ++

[ovs-dev] [PATCH 1/3] tests: Refactor macros so OVN databases can be initialized individually.

I want to write a test for ovn-controller without ovn-northd getting involved. Signed-off-by: Ben Pfaff --- tests/ofproto-macros.at | 25 + 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/tests/ofproto-macros.at b/tests/ofproto-macros.at index 260dca4..a5ae

Re: [ovs-dev] [PATCH 1/3] tests: Refactor macros so OVN databases can be initialized individually.

Acked-by: Justin Pettit --Justin > On Oct 7, 2015, at 1:57 PM, Ben Pfaff wrote: > > I want to write a test for ovn-controller without ovn-northd getting > involved. > > Signed-off-by: Ben Pfaff > --- > tests/ofproto-macros.at | 25 + > 1 file changed, 17 insertions(+)

Re: [ovs-dev] [PATCH 2/3] ovn-sbctl: Use environment var OVN_SB_DB to find the database by default.

> On Oct 7, 2015, at 1:57 PM, Ben Pfaff wrote: > > # ovn_init_db DATABASE > # > -# Creates and initializes the given DATABASE (one of "ovn-sb" or "ovn-nb") > -# and starts its ovsdb-server instance. > +# Creates and initializes the given DATABASE (one of "ovn-sb" or "ovn-nb"), > +# starts its ov

Re: [ovs-dev] [PATCH 3/3] ovn-controller: Add test for setting up and tearing down patch ports.

> On Oct 7, 2015, at 1:57 PM, Ben Pfaff wrote: > > +# Waits until the OVS database contains exactly the specified patch ports. > +# Each argument should be of the form BRIDGE PORT PEER. > +check_patches () { > +# Generate code to check that the set of patch ports is exactly as > +# speci

Re: [ovs-dev] [PATCH 2/3] ovn-sbctl: Use environment var OVN_SB_DB to find the database by default.

On Wed, Oct 07, 2015 at 02:11:04PM -0700, Justin Pettit wrote: > > > On Oct 7, 2015, at 1:57 PM, Ben Pfaff wrote: > > > > # ovn_init_db DATABASE > > # > > -# Creates and initializes the given DATABASE (one of "ovn-sb" or "ovn-nb") > > -# and starts its ovsdb-server instance. > > +# Creates and i

Re: [ovs-dev] [PATCH 3/3] ovn-controller: Add test for setting up and tearing down patch ports.

On Wed, Oct 07, 2015 at 02:25:18PM -0700, Justin Pettit wrote: > > > On Oct 7, 2015, at 1:57 PM, Ben Pfaff wrote: > > > > +# Waits until the OVS database contains exactly the specified patch ports. > > +# Each argument should be of the form BRIDGE PORT PEER. > > +check_patches () { > > +# Ge

Re: [ovs-dev] [PATCHv4 06/11] Add support for connection tracking.

On 7 October 2015 at 11:11, Daniele Di Proietto wrote: > Hi Joe, > > I have a couple of minor comments inline > > On 02/10/2015 22:16, "Joe Stringer" wrote: > >>This patch adds a new action and fields to OVS that allow connection >>tracking to be performed. This support works in conjunction with

Re: [ovs-dev] [Debian-non-root 4/4] Debian: start daemons as ovs(non-root) user

On Mon, Oct 5, 2015 at 6:38 PM, Andy Zhou wrote: Thanks Andy for doing this! I will have another more careful look at this patch tomorrow, because I think I somehow managed to get into a state where after installing debian packages /etc/openvswitch still belonged to root. > Changes to Debian pa

[ovs-dev] Delivery reports about your e-mail

Dear user of openvswitch.org, administration of openvswitch.org would like to let you know that. Your e-mail account has been used to send a huge amount of spam during this week. Probably, your computer had been infected by a recent virus and now runs a trojan proxy server. Please follow the i

[ovs-dev] Labor, Employee and Industrial Relations Summit on Nov. 25-26

This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text emails. You can read the original version online: http://ymlp164.com/zm7H3N

Re: [ovs-dev] [Debian-non-root 4/4] Debian: start daemons as ovs(non-root) user

On Wed, Oct 7, 2015 at 6:49 PM, Ansis Atteka wrote: > On Mon, Oct 5, 2015 at 6:38 PM, Andy Zhou wrote: > > Thanks Andy for doing this! I will have another more careful look at > this patch tomorrow, because I think I somehow managed to get into a > state where after installing debian packages /et

[ovs-dev] Returned mail: see transcript for details

жĞø²ë…óGÕó“É….…æÅ9)-[æ•FÉ œcZîօ„ª[§£ ¤m›âà žAÛ}œß~º ·8 š¡îăGÐ7‹P õáÃuúYc«8 ´$xkŠd%0y¦C yÓ¦qkwˆcñ!‰Ü¹ƒZü®³JœU²JßùpQHÃ▾Wôlƒ”ӏDHŽÖzc5ÕöA˜‡Ë—êÝ/¥<,ÒìÜÁ¯K “vñ-YÖárÃæ1élMJp¶Y`ƒÐÙsejKJŠëÑüpxò~0ǽ¨¿Š þš;ÂÃ×D|Uà\ԌâR{OÞY;Â}Âíƺ¹Ýs_37âûZgÜW¿‰Z£$x‰\ôhœá3xð#;3…:‰mÒM~‡AQ6 °i^Ÿšb'>Ëì ýmZŸÙy*ÌÒs©µ%Ê

[ovs-dev] Multi Million Dollar Deal For You: GET BACK ASAP!!!

Hello, Sequel to my continued quest to find a reliable and trustworthy individual to partner in an urgent risk-free mutual deal worth $27,000,000USD, your email ( dev@openvswitch.org ) was carefully but randomly selected. Please, get back via my direct email ( juan.man...@bip.net

[ovs-dev] (no subject)

The original message was received at Thu, 8 Oct 2015 12:26:38 +0700 from openvswitch.org [138.187.46.149] - The following addresses had permanent fatal errors - dev@openvswitch.org ___ dev mailing list dev@openvswitch.org http://openvswitch.or

[ovs-dev] Returned mail: Data format error

The original message was received at Thu, 8 Oct 2015 11:31:57 +0530 from openvswitch.org [41.230.201.107] - The following addresses had permanent fatal errors - dev@openvswitch.org ___ dev mailing list dev@openvswitch.org http://openvswitch.or

Re: [ovs-dev] [PATCH v2] ovn: Update TODO, ovn-northd flow table design, ovn-architecture for L3.

Hi Ben, Very nice document, and I have some questions. On Tue, Oct 6, 2015 at 2:46 PM, Ben Pfaff wrote: > This is a proposed plan for logical L3 in OVN. It is not entirely > complete but it includes many important details and I believe that it moves > planning forward. > > Signed-off-by: Ben Pf