Re: [ovs-dev] [PATCH] extract-ofp-fields: Define .TQ directive in nroff output.

On Wed, Jan 25, 2017 at 11:10:19PM -0800, Daniele Di Proietto wrote: > 2017-01-25 20:31 GMT-08:00 Ben Pfaff : > > This missing directive caused groff warnings and probably some erroneous > > output too. > > > > Fixes: 96fee5e0a2a0 ("ovs-fields: New manpage to document Open vSwitch and > > OpenFlow

Re: [ovs-dev] [PATCH] extract-ofp-fields: Define .TQ directive in nroff output.

2017-01-25 20:31 GMT-08:00 Ben Pfaff : > This missing directive caused groff warnings and probably some erroneous > output too. > > Fixes: 96fee5e0a2a0 ("ovs-fields: New manpage to document Open vSwitch and > OpenFlow fields.") > Reported-by: Daniele Di Proietto > Signed-off-by: Ben Pfaff Acked

Re: [ovs-dev] [PATCH] ovs-fields: Eliminate non-ASCII characters from groff input.

On Wed, Jan 25, 2017 at 05:48:42PM -0800, Daniele Di Proietto wrote: > 2017-01-25 17:07 GMT-08:00 Ben Pfaff : > > It's difficult to make groff portably accept non-ASCII characters. It's > > easier to replace them by groff escapes for the same characters, which > > this commit does. > > > > Fixes:

[ovs-dev] [PATCH] extract-ofp-fields: Define .TQ directive in nroff output.

This missing directive caused groff warnings and probably some erroneous output too. Fixes: 96fee5e0a2a0 ("ovs-fields: New manpage to document Open vSwitch and OpenFlow fields.") Reported-by: Daniele Di Proietto Signed-off-by: Ben Pfaff --- build-aux/extract-ofp-fields | 6 ++ 1 file chang

Re: [ovs-dev] [PATCH v2] ovn-northd: Add flows in DHCP_OPTIONS pipeline to support renew requests

On Wed, Jan 25, 2017 at 2:55 AM, Numan Siddique wrote: > ovn-northd adds the flows to send the DHCPv4 packets to ovn-controller > only with the match ip4.src = 0.0.0.0 and ip4.dst = 255.255.255.255. > > When a DHCPv4 lease is about to expire, before sending a DHCPDISCOVER > packet, the client can

Re: [ovs-dev] [PATCH 1/1] dpif-netdev: Conditional EMC insert

2017-01-25 7:52 GMT-08:00 Loftus, Ciara : >> 2017-01-22 11:45 GMT-08:00 Jan Scheurich : >> > >> >> It's not a big deal, since the most important use case we have for >> >> dpif-netdev is with dpdk, but I'd still like the code to behave >> >> similarly on different platforms. How about defining a f

Re: [ovs-dev] [PATCH] selinux: Allow creating tap devices.

On 25/01/2017 00:01, "Ansis Atteka" wrote: > > >On Jan 25, 2017 4:22 AM, "Daniele Di Proietto" wrote: > >Current SELinux policy in RHEL and Fedora doesn't allow the creation of >TAP devices. > >A tap device is used by dpif-netdev to create internal devices. > >Without this patch, adding any

Re: [ovs-dev] [PATCH] ovs-fields: Eliminate non-ASCII characters from groff input.

2017-01-25 17:07 GMT-08:00 Ben Pfaff : > It's difficult to make groff portably accept non-ASCII characters. It's > easier to replace them by groff escapes for the same characters, which > this commit does. > > Fixes: 96fee5e0a2a0 ("ovs-fields: New manpage to document Open vSwitch and > OpenFlow f

[ovs-dev] [PATCH] ovs-fields: Eliminate non-ASCII characters from groff input.

It's difficult to make groff portably accept non-ASCII characters. It's easier to replace them by groff escapes for the same characters, which this commit does. Fixes: 96fee5e0a2a0 ("ovs-fields: New manpage to document Open vSwitch and OpenFlow fields.") Signed-off-by: Ben Pfaff --- build-aux/

Re: [ovs-dev] [userspace meter v3 2/5] dp-packet: Enhance packet batch APIs.

Trusting you address the comments below: Acked-by: Jarno Rajahalme > On Jan 24, 2017, at 10:45 PM, Andy Zhou wrote: > > One common use case of 'struct dp_packet_batch' is to process all > packets in the batch in order. Add an iterator for this use case > to simplify the logic of calling sites

Re: [ovs-dev] [userspace meter v3 1/5] netdev-dummy: Add --len option for netdev-dummy/receive command

With two small nits below: Acked-by: Jarno Rajahalme > On Jan 24, 2017, at 10:45 PM, Andy Zhou wrote: > > Currently, there is no way to specify the packet size when injecting > a packet via "netdev-dummy/receive" with a flow specification. Thus > far, packet size is not important for testing O

Re: [ovs-dev] [PATCH v2 3/3] ovs-router: introduce pkt-mark.

Also, IMO this series is good to go to the branch-2.7 as well. Jarno > On Jan 25, 2017, at 2:54 PM, Jarno Rajahalme wrote: > > With a few remarks below, > > Acked-by: Jarno Rajahalme mailto:ja...@ovn.org>> > >> On Jan 24, 2017, at 9:57 PM, Pravin B Shelar wrote: >> >> OVS router is basica

Re: [ovs-dev] [PATCH v2 3/3] ovs-router: introduce pkt-mark.

With a few remarks below, Acked-by: Jarno Rajahalme > On Jan 24, 2017, at 9:57 PM, Pravin B Shelar wrote: > > OVS router is basically partial copy of linux kernel FIB. > kernel routing table uses skb-mark along with usual routing > parameters. Following patch brings in support for skb-mark > t

Re: [ovs-dev] [PATCH v2 1/3] tunnel: Add support to configure ptk_mark

With one correction below, Acked-by: Jarno Rajahalme > On Jan 24, 2017, at 9:57 PM, Pravin B Shelar wrote: > > Today packet mark action is broken for Tunnel ports with > tunnel monitoring. User can write a flow to set pkt-mark for > any tunnel traffic, but there is no way to set the packet > m

Re: [ovs-dev] OVS - ODL Sync on OF Bundle in 1.3

This came with too short notice for me, sorry. Jarno > On Jan 24, 2017, at 11:48 PM, Jan Scheurich > wrote: > > <>We’ll use below webex instead of Lync/SkypeFB: > https://meetings.webex.com/collabs/#/meetings/detail?uuid=MBFUHFYE8TRG3NPX76F4PLRS2N-3OWH&rnd=231184.55753 >

Re: [ovs-dev] [PATCH 2/2] ovs-fields: New manpage to document Open vSwitch and OpenFlow fields.

On Tue, Jan 24, 2017 at 05:13:15PM -0800, Justin Pettit wrote: > > > On Jan 24, 2017, at 5:11 PM, Justin Pettit wrote: > > > > This was a lot of work. Thanks for doing it! > > > > --Justin > > Whoops! > > Acked-by: Justin Pettit Thanks. I applied these to master and branch-2.7. __

[ovs-dev] Meat / Poultry

  [ View in browser ]( http://r.newsletter.bonescamail.nl/nru6r04eoatrf.html )    [ ]( http://r.newsletter.bonescamail.nl/2n3cr00h9aoatrd.html )     Special offers meat and poultry :   Turkeytails / Putenschwanz / Kalkoenstaart / Croupions de Dinde 10 kilo - 10 box € 0,65 per kilo!!   Ch

[ovs-dev] Updated Sugar CRM Users

Hi, Would you be interested in Targeted “*Sugar CRM”* leads? We are happy to provide the database across globe, specifically *North America, EMEA, APAC* and *Latin America*. We also have other users like *Salesforce CRM, Nimble, PipelineDeals, Pipedrive, Hubspot CRM, Workbooks, Zoho CRM, Mic

Re: [ovs-dev] [PATCH 1/1] dpif-netdev: Conditional EMC insert

> 2017-01-22 11:45 GMT-08:00 Jan Scheurich : > > > >> It's not a big deal, since the most important use case we have for > >> dpif-netdev is with dpdk, but I'd still like the code to behave > >> similarly on different platforms. How about defining a function that > >> uses random_uint32 when compi

Re: [ovs-dev] OVS - ODL Sync on OF Bundle in 1.3

Before the meeting will start. Have made some [1] documentation for ODL and [2] few patch sets with rpc implementation of openflow bundles extension. [1] https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Bundles_extension_support [2] https://git.opendaylight.org/gerrit/#/c/5095

Re: [ovs-dev] [ovn] What's the manner of sending GARP for distributed dnat_and_snat?

Thanks, get it. On 2017/1/25 16:30, Mickey Spiegel wrote: On Wed, Jan 25, 2017 at 12:26 AM, Dong Jun > wrote: Hi I learned about the distributed dnat_and_snat. Now I don't see what's the manner of sending GARP for distributed dnat_and_snat IP. I

Re: [ovs-dev] Invitation: OVS-DPDK bi-weekly meeting...

Cancelling for 26th Jan. Next meeting 9th Feb. thanks, Kevin. On 12/13/2016 05:47 PM, ktray...@redhat.com wrote: > You have been invited to the following event. > > Title: OVS-DPDK bi-weekly meeting > Hi All, > > At the OVS-DPDK Meetup after the OVS conference, it was suggested to > have a regu

Re: [ovs-dev] [ovn] What's the manner of sending GARP for distributed dnat_and_snat?

On Wed, Jan 25, 2017 at 12:26 AM, Dong Jun wrote: > Hi > > I learned about the distributed dnat_and_snat. Now I don't see what's > the manner of sending GARP for distributed dnat_and_snat IP. In the past, > we set nat_addresses column in lsp that connected to gateway lrp. Now the > type of lr

[ovs-dev] [ovn] What's the manner of sending GARP for distributed dnat_and_snat?

Hi I learned about the distributed dnat_and_snat. Now I don't see what's the manner of sending GARP for distributed dnat_and_snat IP. In the past, we set nat_addresses column in lsp that connected to gateway lrp. Now the type of lrp was changed from l3gateway to patch, does this affect GA

Re: [ovs-dev] [PATCH] selinux: Allow creating tap devices.

On Jan 25, 2017 4:22 AM, "Daniele Di Proietto" wrote: Current SELinux policy in RHEL and Fedora doesn't allow the creation of TAP devices. A tap device is used by dpif-netdev to create internal devices. Without this patch, adding any bridge backed by the userspace datapath would fail. This doe