Re: [ovs-discuss] Q: Using netfilter to classify packets in OVS ?

[sougol gheissi]

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  wrote:

> On Wed, Jul 12, 2017 at 10:54:34AM -0700, Joe Stringer wrote:
> >
> > Hi Jean,
> >
> > There's no native integration, but I could imagine that if Netfilter
> > ran on the packets first then modified the skb mark field, then OVS
> > ran later on that packet then plausibly you could match on the
> > pkt_mark.
>
> I tried it, and it works great.
> Thanks a lot !
>
> Jean
> ___
> 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] Regarding adding flows on a remote switch using ovs-ofctl

[Ashish Kashinath]

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 number
has changed from 6633 to 6653*
*ovs-ofctl: tcp:192.168.1.101 : failed to connect to
socket (Connection refused)*

At the switch command line, we use the ovs-vsctl set-controller to ensure
the switch is listing to openflow commands The command we used is:

*ovs-vsctl set-controller br0 tcp:192.168.1.102:6633
*

192.168.1.101 is the IP address of our switch running ovs.
192.168.1.102 is the IP address of the controller.

We were referring to an archived thread

http://discuss.openvswitch.narkive.com/eGESU38o/ovs-discuss-is-it-possible-to-use-the-ovs-ofctl-command-to-control-the-remote-ovs

but were still unable to get this working. Could someone give any pointers?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Regarding adding flows on a remote switch using ovs-ofctl

[Ben Pfaff]

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 action=normal*
> *2018-01-21T19:23:21Z|1|stream|WARN|The default OpenFlow port number
> has changed from 6633 to 6653*
> *ovs-ofctl: tcp:192.168.1.101 : failed to connect to
> socket (Connection refused)*
> 
> At the switch command line, we use the ovs-vsctl set-controller to ensure
> the switch is listing to openflow commands The command we used is:
> 
> *ovs-vsctl set-controller br0 tcp:192.168.1.102:6633
> *
> 
> 192.168.1.101 is the IP address of our switch running ovs.
> 192.168.1.102 is the IP address of the controller.

You have both sides connecting outbound, but one side needs to be
listening for a connection (with ptcp:).
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Regarding adding flows on a remote switch using ovs-ofctl

[Ashish Kashinath]

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 Sun, Jan 21, 2018 at 3:15 PM, Ben Pfaff  wrote:

> 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 action=normal*
> > *2018-01-21T19:23:21Z|1|stream|WARN|The default OpenFlow port number
> > has changed from 6633 to 6653*
> > *ovs-ofctl: tcp:192.168.1.101 : failed to connect
> to
> > socket (Connection refused)*
> >
> > At the switch command line, we use the ovs-vsctl set-controller to ensure
> > the switch is listing to openflow commands The command we used is:
> >
> > *ovs-vsctl set-controller br0 tcp:192.168.1.102:6633
> > *
> >
> > 192.168.1.101 is the IP address of our switch running ovs.
> > 192.168.1.102 is the IP address of the controller.
>
> You have both sides connecting outbound, but one side needs to be
> listening for a connection (with ptcp:).
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Linking of OFPROTO and NETDEV libraries to OVS

[Aravind Prasad]

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 ovs
code base by adding private patches to register providers.
Hence, with this, I can download the OVS-Package, replace the dynamic
library for registering providers and start using OVS without touching the
OVS code base.

Is the above possible today? Thanks for the response and support.

Thanks,
S. Aravind Prasad


On Sat, Jan 20, 2018 at 2:09 AM, Ben Pfaff  wrote:

> On Fri, Jan 19, 2018 at 10:15:46AM +0530, Aravind Prasad wrote:
> > Is there a way to link OFPROTO and NETDEV libraries directly to OVS
> binary
> > without recompiling the OVS codebase. Like, downloading the OVS debian
> > binary directly and link the ofproto and netdev dynamic libraries to it.
>
> I don't understand the question.  These are always linked together.
>
> > Afaik, currently, we need to compile the OVS code with ofproto and netdev
> > libraries manually. And if thats the way, is supporting multiple datapath
> > elements the possible reason to mandate the recompilation of OVS codebase
> > with the libraries. Just curious to know :).
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Regarding adding flows on a remote switch using ovs-ofctl

[Ben Pfaff]

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 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 Sun, Jan 21, 2018 at 3:15 PM, Ben Pfaff  wrote:
> 
> > 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 action=normal*
> > > *2018-01-21T19:23:21Z|1|stream|WARN|The default OpenFlow port number
> > > has changed from 6633 to 6653*
> > > *ovs-ofctl: tcp:192.168.1.101 : failed to connect
> > to
> > > socket (Connection refused)*
> > >
> > > At the switch command line, we use the ovs-vsctl set-controller to ensure
> > > the switch is listing to openflow commands The command we used is:
> > >
> > > *ovs-vsctl set-controller br0 tcp:192.168.1.102:6633
> > > *
> > >
> > > 192.168.1.101 is the IP address of our switch running ovs.
> > > 192.168.1.102 is the IP address of the controller.
> >
> > You have both sides connecting outbound, but one side needs to be
> > listening for a connection (with ptcp:).
> >
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Reg. tc flow offload apis in netdev-vport

[Vishal Deep Ajmera]

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 related APIs will anyway fail because these netdev's do
not have if-index in linux.

Do we have a representation of netdev-vport netdev's in linux
similar to netdev-linux ?

Warm Regards,
Vishal Ajmera

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss