[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:<IP of the switch>:<any port number>

Is that right?

On Sun, Jan 21, 2018 at 3:15 PM, Ben Pfaff <blp at ovn.org> 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 at ubuntu:~/Repositories/qos_synthesis/src/experiments$ ovs-ofctl
> > add-flow tcp:192.168.1.101 action=normal*
> > *2018-01-21T19:23:21Z|00001|stream|WARN|The default OpenFlow port number
> > has changed from 6633 to 6653*
> > *ovs-ofctl: tcp:192.168.1.101 <http://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
> > <http://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:).
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180121/05e3fd63/attachment.html>