Why is TC flow offload APIs being added in netdev-vport ?
For linux TC offloads I believe a device needs to be present in linux
to operate on. As per my understanding netdev-vport classes are used
to represent tunnels (vxlan, gre etc.) and none of them creates a linux device.
All the TC offload
You seem to be confusing things. "OpenFlow connections" and "controller
connections" are the same thing, and the --db option to ovs-vsctl is
entirely different.
On Sun, Jan 21, 2018 at 04:57:48PM -0600, Ashish Kashinath wrote:
> Okay, I see, it makes sense. So is it that the switch should have
Hi Ben,
> I don't understand the question. These are always linked together.
I want to write a new ofproto provider and netdev provider and have them as
dynamic libraries. The requirement is to have the implementation of the
provider Apis contained in a separate dynamic library and not modify
Okay, I see, it makes sense. So is it that the switch should have an
additional port listening for openflow connections using ptcp (in addition
to the port listening to controller connections)?
I guess this should be a ovs-vsctl command on the lines of
ovs-vsctl --db=tcp::
Is that right?
On
On Sun, Jan 21, 2018 at 02:17:56PM -0600, Ashish Kashinath wrote:
> Hi everyone, we were trying to add flows to a switch remotely via tcp. But
> are not able to do so. The command we used is:
>
> *ak7@ubuntu:~/Repositories/qos_synthesis/src/experiments$ ovs-ofctl
> add-flow tcp:192.168.1.101
Hi everyone, we were trying to add flows to a switch remotely via tcp. But
are not able to do so. The command we used is:
*ak7@ubuntu:~/Repositories/qos_synthesis/src/experiments$ ovs-ofctl
add-flow tcp:192.168.1.101 action=normal*
*2018-01-21T19:23:21Z|1|stream|WARN|The default OpenFlow port
Hello Jean,
Can you describe a little how you could implement that?
How you made netfilter ran on the packets before OVS? I have tried
netfilter, ebtales in both mode pre-routing and pos-routing, but got
nothing.
Thanks in advance.
On Thu, Jul 13, 2017 at 1:08 AM, Jean Tourrilhes
