Glad you got it figured out. For further clarification: "ptcp" means "passive tcp" -- a server socket. "tcp" in this case means "active tcp" -- a client socket. So you need one of each to get a connection.
-- Murphy On Jul 12, 2012, at 5:14 AM, Neha Jatav wrote: > Hey all, > > The following worked for me: > > > > $./nox_core -v -I ptcp: pyswitch > > $sudo ovs-vsctl set-controller ovsbr0 tcp:127.0.0.1:6633 > > > > -Neha > > > On Thu, Jul 12, 2012 at 12:46 AM, Neha Jatav <[email protected]> wrote: > Hey, > > > > I was trying to run the NOX controller pyswitch script and my mini net setup > on a VM could communicate the same script. However, my OVS couldn't connect > to it. I did the following: > > > > $./nox_core –v –i ptcp: pyswitch > > > > $sudo ovs-vsctl set-controller ovs-br0 ptcp: > > $sudo ovs-vsctl show > > Bridge "ovsbr0" > > Controller "ptcp:" > > Port "ovsbr0" > > Interface "ovsbr0" > > type: internal > > Port "vnet0" > > Interface "vnet0" > > Port "vnet1" > > Interface "vnet1" > > > > vnet0 and vnet1 are tap interfaces of VMs. Vms corresponding to vnet0 & vnet1 > can ping each other but there's no activity in now script (I.e. Its not > connected) > > Is there a mistake in what I'm doing? Is there any way to debug or find out > where is the problem in the setup? > > > > Regards, > > Neha Jatav > >
