Re: [ovs-discuss] Bonding slave disabled
Hi, When one interface is down, the interface showing may_enable to false. But the up interface becoming active slave and is enabled. I am using virtual ethernet driver which doesn't have mii tool support. The carrier link is up always , but still may_enable set to false. Is there any other criteria for may_enable becoming false. Thanks Neelakantam On Feb 11, 2017 12:36 AM, "O'Reilly, Darragh" wrote: What kind of nics are you using? Try using miimon instead of carrier for failure detection. See the ovs-vswitchd.conf.db man page. Darragh. *From:* ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-bounces@ openvswitch.org] *On Behalf Of *Neelakantam Gaddam *Sent:* 10 February 2017 07:58 *To:* ovs-discuss@openvswitch.org *Subject:* Re: [ovs-discuss] Bonding slave disabled One more observation is that if any of the interface link status is down, then the add-bond operation is showing the down interface as disabled and up interface as enabled with proper mac address. On Fri, Feb 10, 2017 at 1:25 PM, Neelakantam Gaddam wrote: Hi all, I am observing strange issue while configuring bonding in ovs 2.6.1. *Configuration: * ovs-vsctl add-br br0 ifconfig eth0 up ifconfig eth1 up ovs-vsctl add-bond br0 bond0 eth0 eth1 bond_mode=active-backup ovs-appctl bond/show bond0 bond0 bond_mode: active-backup bond may use recirculation: no, Recirc-ID : -1 bond-hash-basis: 0 updelay: 0 ms downdelay: 0 ms lacp_status: off active slave mac: 00:00:00:00:00:00(none) slave eth0: disabled may_enable: false slave eth1: disabled may_enable: false Even though, interfaces eth0 and eth1 having the link status showing UP, the bond show command always showing the eth0/eth1 as disabled. What are the possible reasons for slave interface displaying as disabled? When I debug further, I observed that may_enable is 0 always. What are the possibilities of this variable becoming zero? -- Thanks & Regards Neelakantam Gaddam -- Thanks & Regards Neelakantam Gaddam ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Understand GRE IPSEC tunnels in 2.5/2.6/2.7
I am trying to understand a few things about the implementation of GRE over IPSec tunnels across some of the more recent OVS releases. As I understand it, 2.5 had support for it but in 2.6 the IPSec scripts (and effectively the support) were pulled out in 2.6 due to concerns around mark usage. I have also seen patches proposed that migrated from racoon to strongswan but I don't think they were ever fully accepted. So I have three questions: 1) What is the plan for IPSec support in 2.7 and/or future releases? 2) Is there any plan to move away from racoon to something else? The patch proposed a while ago didn't seem to have any comments or debate against it that I could find. 3) Can someone explain a bit of the mark behavior? First as it exists in 2.5? Apparently part of the problem with it was the fact that OVS expects to use the LSB of the mark for it's own purposes and it will conflict with other uses of the mark. I think this is problem I have in places where the mark is used for other behaviors. Is it that after the ESP packet arrives and is transformed back into the GRE packet, the mark is set to 0x1 by the xfrm policy and then the OVS layer is expecting that when decap'ing the GRE packet? And it is in this manner that a GRE-IPSec packet (with mark 0x1) is distinguished from a regular GRE packet (with mark 0x0)? But once this tunnel port is found and the GRE packet is decapped - what is the state of the mark, connmark/connstate? I may have some of it wrong but tried to learn and trace it out through iptables using the "TRACE" action, by messing with the mark, and by looking at OVS logs. And is there an agreed upon way to to fix this mark usage when returning the IPSec support to OVS? If so what does that behavior look like. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] License of the OvS logo
Thanks for doing that, David. I can't help with German, but the English Wikipedia article on Open vSwitch could use some updating. If you wanted to do any editing on that, I'd be happy to lend a hand. I just don't have any experience working on Wikipedia. --Justin > On Feb 5, 2017, at 2:40 AM, David Rabel wrote: > > Hi together, > > I hope I am at the right place for my question. If not, please let me know. > > I want to write a Wikipedia article about Open vSwitch for the German > Wikipedia. And of course I would like to include the official logo. But > this is only possible if the logo is released under an appropriate license. > > So my question is: What is the license of the official OvS logo? > > Regards, > David > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Is of-ctl add-flow persistent across reboots ?
Before a controller connects, by default, OVS acts as a MAC-learning switch. See "Controller Failure Settings" in ovs-vsctl(8). On Fri, Feb 10, 2017 at 08:22:05PM +0100, Jannis Ohms wrote: > The main purpose of this bridge is to enable an indirect connection to the > Controller across multiple Switches so the flow needs to exist before the > Controller is connected. > Is there another way to enable classic forwarding on a bridge ? > The main problem is that my switch runs ovs but needs a dedicated port for > the controller connection.. The purpose of the second bridge is to forward > traffic to this port. > > Am 10.02.17 19:57 schrieb Ben Pfaff : > > > > OpenFlow switches generally consider flows to be "soft state". The > > controller is expected to install whatever flows are needed. If you > > need persistent flows, using a controller is the typical way. > > > > On Fri, Feb 10, 2017 at 06:15:19PM +0100, Jannis Ohms wrote: > > > > > > Ok > > > Are there any reasons Why this design was chosen? > > > Are there other ways to persist a flow in OVS ? > > > > > > Am 10.02.17 17:51 schrieb Guru Shetty : > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 10 February 2017 at 04:43, Jannis Ohms > > > > wrote: > > > > > > > > > I am currently using a setup consisting of 2 bridges per switch. > > > > > > > > > > Bridge 0 is configured to use an SDN controller > > > > > > > > > > Bridge 1 uses a single flow which contains a single flow which uses > > > > > the normal action to enable classic forwarding. > > > > > > > > > > I added the flow using ovs-ofctl, the hard and idle timeouts are both > > > > > 0 the fail-mode of the bridge is secure. > > > > > The flow dose not persist across restarts. > > > > > > > > > > > > > > Is this normal or is this a problem of my NOS ? > > > > > > > > > > > > > > > > > This is normal. > > > > > > > > > > > > > > > > > > > > > > greethings > > > > > > > > > > Jannis > > > > > > > > > > -- > > > > > Ostfalia University of Applied Sciences > > > > > Research Group IP-based Communication Systems > > > > > Salzdahlumer Straße 46/48 > > > > > 38302 Wolfenbüttel, Germany > > > > > > > > > > Tel.: + 49 (0)5331 939 43320(tel:%2B%2049%20%280%295331%20939%2043320) > > > > > Fax: + 49 (0)5331 939 43322(tel:%2B%2049%20%280%295331%20939%2043322) > > > > > E-Mail: jannis.oh...@ostfalia.de > > > > > Web: http://www.ostfalia.de/cms/de/e > > > > > > > > > > ___ > > > > > discuss mailing list > > > > > disc...@openvswitch.org > > > > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > > > > > > > > > > > > > > > > > > > > > > > ___ > > > discuss mailing list > > > disc...@openvswitch.org > > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Is of-ctl add-flow persistent across reboots ?
The main purpose of this bridge is to enable an indirect connection to the Controller across multiple Switches so the flow needs to exist before the Controller is connected. Is there another way to enable classic forwarding on a bridge ? The main problem is that my switch runs ovs but needs a dedicated port for the controller connection.. The purpose of the second bridge is to forward traffic to this port. Am 10.02.17 19:57 schrieb Ben Pfaff : > > OpenFlow switches generally consider flows to be "soft state". The > controller is expected to install whatever flows are needed. If you > need persistent flows, using a controller is the typical way. > > On Fri, Feb 10, 2017 at 06:15:19PM +0100, Jannis Ohms wrote: > > > > Ok > > Are there any reasons Why this design was chosen? > > Are there other ways to persist a flow in OVS ? > > > > Am 10.02.17 17:51 schrieb Guru Shetty : > > > > > > > > > > > > > > > > > > > > > On 10 February 2017 at 04:43, Jannis Ohms > > > wrote: > > > > > > > I am currently using a setup consisting of 2 bridges per switch. > > > > > > > > Bridge 0 is configured to use an SDN controller > > > > > > > > Bridge 1 uses a single flow which contains a single flow which uses the > > > > normal action to enable classic forwarding. > > > > > > > > I added the flow using ovs-ofctl, the hard and idle timeouts are both 0 > > > > the fail-mode of the bridge is secure. > > > > The flow dose not persist across restarts. > > > > > > > > > > > Is this normal or is this a problem of my NOS ? > > > > > > > > > > > > > This is normal. > > > > > > > > > > > > > > > > > greethings > > > > > > > > Jannis > > > > > > > > -- > > > > Ostfalia University of Applied Sciences > > > > Research Group IP-based Communication Systems > > > > Salzdahlumer Straße 46/48 > > > > 38302 Wolfenbüttel, Germany > > > > > > > > Tel.: + 49 (0)5331 939 43320(tel:%2B%2049%20%280%295331%20939%2043320) > > > > Fax: + 49 (0)5331 939 43322(tel:%2B%2049%20%280%295331%20939%2043322) > > > > E-Mail: jannis.oh...@ostfalia.de > > > > Web: http://www.ostfalia.de/cms/de/e > > > > > > > > ___ > > > > discuss mailing list > > > > disc...@openvswitch.org > > > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > > > > > > > > > > > > > > > > ___ > > discuss mailing list > > disc...@openvswitch.org > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Bonding slave disabled
What kind of nics are you using? Try using miimon instead of carrier for failure detection. See the ovs-vswitchd.conf.db man page. Darragh. From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Neelakantam Gaddam Sent: 10 February 2017 07:58 To: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] Bonding slave disabled One more observation is that if any of the interface link status is down, then the add-bond operation is showing the down interface as disabled and up interface as enabled with proper mac address. On Fri, Feb 10, 2017 at 1:25 PM, Neelakantam Gaddam mailto:neelugad...@gmail.com>> wrote: Hi all, I am observing strange issue while configuring bonding in ovs 2.6.1. Configuration: ovs-vsctl add-br br0 ifconfig eth0 up ifconfig eth1 up ovs-vsctl add-bond br0 bond0 eth0 eth1 bond_mode=active-backup ovs-appctl bond/show bond0 bond0 bond_mode: active-backup bond may use recirculation: no, Recirc-ID : -1 bond-hash-basis: 0 updelay: 0 ms downdelay: 0 ms lacp_status: off active slave mac: 00:00:00:00:00:00(none) slave eth0: disabled may_enable: false slave eth1: disabled may_enable: false Even though, interfaces eth0 and eth1 having the link status showing UP, the bond show command always showing the eth0/eth1 as disabled. What are the possible reasons for slave interface displaying as disabled? When I debug further, I observed that may_enable is 0 always. What are the possibilities of this variable becoming zero? -- Thanks & Regards Neelakantam Gaddam -- Thanks & Regards Neelakantam Gaddam ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Bonding slave disabled
On Thu, Feb 9, 2017 at 11:58 PM, Neelakantam Gaddam wrote: > One more observation is that if any of the interface link status is down, > then the add-bond operation is showing the down interface as disabled and up > interface as enabled with proper mac address. When one port is enabled, what does 'ovs-appctl bond/show" say? Is may_enabled still set to 0? I was not able to reproduce this from a fresh install with branch 2.6. Does vswitchd log provide any clue? > > > On Fri, Feb 10, 2017 at 1:25 PM, Neelakantam Gaddam > wrote: >> >> Hi all, >> >> I am observing strange issue while configuring bonding in ovs 2.6.1. >> >> Configuration: >> >> ovs-vsctl add-br br0 >> ifconfig eth0 up >> ifconfig eth1 up >> ovs-vsctl add-bond br0 bond0 eth0 eth1 bond_mode=active-backup >> >> >> ovs-appctl bond/show bond0 >> >> bond0 >> bond_mode: active-backup >> bond may use recirculation: no, Recirc-ID : -1 >> bond-hash-basis: 0 >> updelay: 0 ms >> downdelay: 0 ms >> lacp_status: off >> active slave mac: 00:00:00:00:00:00(none) >> >> slave eth0: disabled >> may_enable: false >> >> slave eth1: disabled >> may_enable: false >> >> >> Even though, interfaces eth0 and eth1 having the link status showing UP, >> the bond show command always showing the eth0/eth1 as disabled. >> >> What are the possible reasons for slave interface displaying as disabled? >> >> When I debug further, I observed that may_enable is 0 always. What are the >> possibilities of this variable becoming zero? >> >> >> >> -- >> Thanks & Regards >> Neelakantam Gaddam > > > > > -- > Thanks & Regards > Neelakantam Gaddam > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Is of-ctl add-flow persistent across reboots ?
OpenFlow switches generally consider flows to be "soft state". The controller is expected to install whatever flows are needed. If you need persistent flows, using a controller is the typical way. On Fri, Feb 10, 2017 at 06:15:19PM +0100, Jannis Ohms wrote: > > Ok > Are there any reasons Why this design was chosen? > Are there other ways to persist a flow in OVS ? > > Am 10.02.17 17:51 schrieb Guru Shetty : > > > > > > > > > > > > > > On 10 February 2017 at 04:43, Jannis Ohms wrote: > > > > > I am currently using a setup consisting of 2 bridges per switch. > > > > > > Bridge 0 is configured to use an SDN controller > > > > > > Bridge 1 uses a single flow which contains a single flow which uses the > > > normal action to enable classic forwarding. > > > > > > I added the flow using ovs-ofctl, the hard and idle timeouts are both 0 > > > the fail-mode of the bridge is secure. > > > The flow dose not persist across restarts. > > > > > > > > Is this normal or is this a problem of my NOS ? > > > > > > > > > This is normal. > > > > > > > > > > > > greethings > > > > > > Jannis > > > > > > -- > > > Ostfalia University of Applied Sciences > > > Research Group IP-based Communication Systems > > > Salzdahlumer Straße 46/48 > > > 38302 Wolfenbüttel, Germany > > > > > > Tel.: + 49 (0)5331 939 43320(tel:%2B%2049%20%280%295331%20939%2043320) > > > Fax: + 49 (0)5331 939 43322(tel:%2B%2049%20%280%295331%20939%2043322) > > > E-Mail: jannis.oh...@ostfalia.de > > > Web: http://www.ostfalia.de/cms/de/e > > > > > > ___ > > > discuss mailing list > > > disc...@openvswitch.org > > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > > > > > > > > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Is of-ctl add-flow persistent across reboots ?
Ok Are there any reasons Why this design was chosen? Are there other ways to persist a flow in OVS ? Am 10.02.17 17:51 schrieb Guru Shetty : > > > > > > > On 10 February 2017 at 04:43, Jannis Ohms wrote: > > > I am currently using a setup consisting of 2 bridges per switch. > > > > Bridge 0 is configured to use an SDN controller > > > > Bridge 1 uses a single flow which contains a single flow which uses the > > normal action to enable classic forwarding. > > > > I added the flow using ovs-ofctl, the hard and idle timeouts are both 0 the > > fail-mode of the bridge is secure. > > The flow dose not persist across restarts. > > > > > Is this normal or is this a problem of my NOS ? > > > > > This is normal. > > > > > > > greethings > > > > Jannis > > > > -- > > Ostfalia University of Applied Sciences > > Research Group IP-based Communication Systems > > Salzdahlumer Straße 46/48 > > 38302 Wolfenbüttel, Germany > > > > Tel.: + 49 (0)5331 939 43320(tel:%2B%2049%20%280%295331%20939%2043320) > > Fax: + 49 (0)5331 939 43322(tel:%2B%2049%20%280%295331%20939%2043322) > > E-Mail: jannis.oh...@ostfalia.de > > Web: http://www.ostfalia.de/cms/de/e > > > > ___ > > discuss mailing list > > disc...@openvswitch.org > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > > > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Is of-ctl add-flow persistent across reboots ?
On 10 February 2017 at 04:43, Jannis Ohms wrote: > I am currently using a setup consisting of 2 bridges per switch. > > Bridge 0 is configured to use an SDN controller > > Bridge 1 uses a single flow which contains a single flow which uses the > normal action to enable classic forwarding. > > I added the flow using ovs-ofctl, the hard and idle timeouts are both 0 > the fail-mode of the bridge is secure. > The flow dose not persist across restarts. > Is this normal or is this a problem of my NOS ? > This is normal. > > greethings > > Jannis > > -- > Ostfalia University of Applied Sciences > Research Group IP-based Communication Systems > Salzdahlumer Straße 46/48 > 38302 Wolfenbüttel, Germany > > Tel.: + 49 (0)5331 939 43320 > Fax:+ 49 (0)5331 939 43322 > E-Mail: jannis.oh...@ostfalia.de > Web:http://www.ostfalia.de/cms/de/e > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Is of-ctl add-flow persistent across reboots ?
I am currently using a setup consisting of 2 bridges per switch. Bridge 0 is configured to use an SDN controller Bridge 1 uses a single flow which contains a single flow which uses the normal action to enable classic forwarding. I added the flow using ovs-ofctl, the hard and idle timeouts are both 0 the fail-mode of the bridge is secure. The flow dose not persist across restarts. Is this normal or is this a problem of my NOS ? greethings Jannis -- Ostfalia University of Applied Sciences Research Group IP-based Communication Systems Salzdahlumer Straße 46/48 38302 Wolfenbüttel, Germany Tel.: + 49 (0)5331 939 43320 Fax:+ 49 (0)5331 939 43322 E-Mail: jannis.oh...@ostfalia.de Web:http://www.ostfalia.de/cms/de/e ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] custom field in OVS flow rules
Dear Ben, Thanks for your answer again. I would go for the datapath modification. I found a similar commit for CT_MARK added to the datapath, i.e., https://github.com/openvswitch/ovs/commit/372ce9737d2bca509f9717672d95d08b6978f4a3 I mostly followed the description of the commit, however did not go deeply in the source-code of OVS as a whole. In this commit, I don't see modifications to lib/odp-util.c. I suspect that odp-util.c is a place, in which OVS sends the key from user-space to kernel-space? Is that correct? So in order to make datapath modifications operating, I guess that I need to mirror all the modification for CT_MARK in odp-util.c too? Best regards, Thx in advance for your help, Eryk Schiller On 02/09/2017 07:38 PM, Ben Pfaff wrote: To add support for a new field to the datapath, I'd look for another commit that does that and use it as a template. To make every packet go to userspace, the most general way is to make odp_flow_key_to_flow() return ODP_FIT_TOO_LITTLE for flows that should have the field. For example, if your new field is present in every packet, then return ODP_FIT_TOO_LITTLE for every packet; if your new field is present in every TCP packet, then it's better to just return ODP_FIT_TOO_LITTLE for TCP packets. As an alternative you can add one of SLOW_* bits to ctx->xout->slow during flow translation, look around ofproto-dpif-xlate.c for examples. On Thu, Feb 09, 2017 at 06:12:01PM +0100, Eryk Schiller wrote: Dear Ben, Yes, done. Thx. Another question; it seems to be that only the first packet of the flow is appropriately matched through my user-space rule, while the rest are pretty much ignored. Is there any manual about extending the kernel datapath to appropriately cache my field? I think that for the moment, I could also live without the cache. Is there any way to switch it off so that all packets (for example for a certain flow) always go through ovs-vswitchd? Best regards, Eryk Schiller Quoting Ben Pfaff : On Wed, Feb 08, 2017 at 10:29:29PM +0100, Eryk Schiller wrote: Dear all, I am writing this post, because I saw a discussion from the beginning of 2016 about the implementation of an additional matching field of UDP in OVS. Maybe you can help with a similar implementation. The discussion is here, https://mail.openvswitch.org/pipermail/ovs-discuss/2016-April/040894.html and I found another similar patch implementing some IGMP functionality here. https://patchwork.ozlabs.org/patch/555337/ I went through the FAQ, discussion, and the aforementioned patch, and implemented a new custom user-space matching rule. However, when I add my field to flow rules, i.e., ovs-ofctl --verbose -O OpenFlow15 add-flow ovs-br in_port=4,ip,udp,my_field=0x6,action=normal 2017-02-08T20:42:13Z|1|hmap|DBG|lib/shash.c:112: 7 nodes in bucket (64 nodes, 32 buckets) 2017-02-08T20:42:13Z|2|hmap|DBG|lib/shash.c:112: 6 nodes in bucket (128 nodes, 64 buckets) 2017-02-08T20:42:13Z|3|hmap|DBG|lib/shash.c:112: 7 nodes in bucket (128 nodes, 64 buckets) 2017-02-08T20:42:13Z|4|hmap|DBG|lib/shash.c:112: 7 nodes in bucket (128 nodes, 64 buckets) 2017-02-08T20:42:13Z|5|stream_unix|DBG|/var/run/openvswitch/ovs-br: connection failed (No such file or directory) 2017-02-08T20:42:13Z|6|ofctl|DBG|connecting to unix:/var/run/openvswitch/ovs-br.mgmt 2017-02-08T20:42:13Z|7|hmap|DBG|lib/ofp-msgs.c:1143: 6 nodes in bucket (128 nodes, 64 buckets) 2017-02-08T20:42:13Z|8|hmap|DBG|lib/ofp-msgs.c:1143: 6 nodes in bucket (256 nodes, 128 buckets) 2017-02-08T20:42:13Z|9|hmap|DBG|lib/ofp-msgs.c:1143: 7 nodes in bucket (512 nodes, 256 buckets) 2017-02-08T20:42:13Z|00010|hmap|DBG|lib/ofp-msgs.c:1143: 8 nodes in bucket (512 nodes, 256 buckets) 2017-02-08T20:42:13Z|00011|hmap|DBG|lib/ofp-msgs.c:1143: 6 nodes in bucket (512 nodes, 256 buckets) 2017-02-08T20:42:13Z|00012|hmap|DBG|lib/ofp-msgs.c:1143: 7 nodes in bucket (512 nodes, 256 buckets) 2017-02-08T20:42:13Z|00013|vconn|DBG|unix:/var/run/openvswitch/ovs-br.mgmt: sent (Success): OFPT_HELLO (OF1.5) (xid=0x1): version bitmap: 0x06 2017-02-08T20:42:13Z|00014|vconn|DBG|unix:/var/run/openvswitch/ovs-br.mgmt: received: OFPT_HELLO (OF1.5) (xid=0x39): version bitmap: 0x01, 0x02, 0x03, 0x04, 0x05, 0x06 2017-02-08T20:42:13Z|00015|vconn|DBG|unix:/var/run/openvswitch/ovs-br.mgmt: negotiated OpenFlow version 0x06 (we support version 0x06, peer supports version 0x06 and earlier) 2017-02-08T20:42:13Z|00016|vconn|DBG|unix:/var/run/openvswitch/ovs-br.mgmt: sent (Success): OFPT_FLOW_MOD (OF1.5) (xid=0x2): ADD *udp,in_port=4* actions=NORMAL 2017-02-08T20:42:13Z|00017|vconn|DBG|unix:/var/run/openvswitch/ovs-br.mgmt: sent (Success): OFPT_BARRIER_REQUEST (OF1.5) (xid=0x3): 2017-02-08T20:42:13Z|00018|poll_loop|DBG|wakeup due to 0-ms timeout 2017-02-08T20:42:13Z|00019|poll_loop|DBG|wakeup due to [POLLIN] on fd 4 (<->/var/run/openvswitch/ovs-br.mgmt) at lib/stream-fd.c:155 2017-02-08T20:42:13Z|00020|vconn|DBG|unix:/var/run/openvswitch/o
[ovs-discuss] Auxiliary Connection
Hello, As far as I have seen from the documentation: "An implementation in generic code might be a week’s worth of work. The value of an implementation in generic code is questionable, though, since much of the benefit of axuiliary connections is supposed to be to take advantage of hardware support. (We could make the kernel module somehow send packets across the auxiliary connections directly, for some kind of “hardware” support, if we judged it useful enough.) (optional for OF1.3+)" We do find some value in implementation of auxiliary connections. Do you have any hints for us on how to implement it? Where should we start? Thanks and regards, Akın ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
