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

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

[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 ---

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

[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

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 > > >> On Jan 24, 2017, at 9:57 PM, Pravin B Shelar

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

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

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

[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!!  

[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,

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]

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

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

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.

[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

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