Thanks, Ben! It works! So the command that substitutes ovs-openflowd <dp> tcp:<ip>:<port> is ovs-vsctl set-controller br0 tcp:<ip of controller>:<port>?
Another question, I used to tell every dp to the controller.. Is it still necessary? Do I use the same command you told me? Best regards, 2011/9/8 Ben Pfaff <[email protected]>: > On Thu, Sep 08, 2011 at 04:26:27PM -0300, Lucas Henrique Mauricio wrote: >> I have the NOX (Zaku) controller installed in my host and an >> openvswitch (v1.2.1) running as openflow switch in a virtual machine >> created with VirtualBox. The virtual machine has an interface (eth1) >> connected to the host. Before setting datapaths, the vm can reach the >> host, but when I set a datapath, the vm can't. When I used openvswitch >> (v1.1.0) and NOX (v0.5) in the same machine, I just had to do >> ovs-openflowd dp# tcp:<ip of controller>:<port> to connect the switch >> to the controller. >> >> What can I do to solve this? I don't even know the command that >> substitutes ovs-openflowd in the openvswitch v1.2.1.. =( Is it >> ovs-ofctl? How can I use it? > > Please set up OVS according to INSTALL.Linux. After that, to > configure a controller on br0: > ovs-vsctl set-controller br0 tcp:<ip of controller>:<port> > -- Lucas Henrique Mauricio Brasil Universidade Federal do Rio de Janeiro Escola Politécnica Engenharia Eletrônica e de Computação _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
