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

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