A bridge and a switch are the same thing. I don't understand the distinction that you are attempting to match.
There are various ways to make 2 bridges communicate, but it's usually better to just use a single bridge. On Mon, Sep 12, 2011 at 04:49:40PM -0700, Aishwarya wrote: > Hmmm.. ok.. but a bridge in openvswitch can be assigned an ip address right, > unlike a switch? Also, is there a way to get 2 bridges on the same machine > to communicate to each other? > > Thanks, > Aish > > On Mon, Sep 12, 2011 at 4:43 PM, Ben Pfaff <b...@nicira.com> wrote: > > > A bridge and a switch are the same thing. > > > > On Mon, Sep 12, 2011 at 04:42:49PM -0700, Aishwarya wrote: > > > Hi ben, > > > > > > Thanks for your input. I was confused because as you said, the man page > > > suggests all the connection methods, but when i use for eg: > > > > > > ofctl show br0, it is connecting to a bridge right? A single openvswitch > > can > > > also have more then one bridge, so in that case, if I want to connect to > > the > > > switch as a whole, how different will it be? I guess I am just a little > > > confused between the switch/bridge terminologies. > > > > > > Thanks, > > > Aish > > > > > > On Mon, Sep 12, 2011 at 3:48 PM, Ben Pfaff <b...@nicira.com> wrote: > > > > > > > Please read the ovs-ofctl manpage. It explains all the allowed forms > > > > at the very top. > > > > > > > > Of course a Unix socket doesn't work on another machine. Add a > > > > "ptcp:" controller to access OpenFlow over TCP from another machine. > > > > > > > > On Mon, Sep 12, 2011 at 03:43:25PM -0700, Aishwarya wrote: > > > > > Hi Ben, > > > > > > > > > > That is correct. Right now, I am doing it from the same machine > > running > > > > > vswitchd. The ofctl doc says the argument should be show *switch* > > > > > > > > > > and the methos of connection seemed to me like I need to give the > > switch > > > > > argument as unix:... or tcp:.... . Is my understanding wrong? (is it > > > > > different if I need to connect to the switch from a different > > machine?) > > > > > > > > > > Thanks, > > > > > Aish > > > > > > > > > > On Mon, Sep 12, 2011 at 3:38 PM, Ben Pfaff <b...@nicira.com> wrote: > > > > > > > > > > > It sounds like you want to use ovs-ofctl from the same machine > > running > > > > > > ovs-vswitchd. There's already a unix socket for that. Just give > > the > > > > > > name of the bridge, e.g. "ovs-ofctl show br0". > > > > > > > > > > > > On Mon, Sep 12, 2011 at 03:37:19PM -0700, Aishwarya wrote: > > > > > > > Hi Ben, > > > > > > > > > > > > > > Passive tcp socket should be fine. I know the ptcp option lets > > you do > > > > > > this. > > > > > > > But I am not sure which command to use it with. For eg: I use the > > > > unix > > > > > > > socket option with ovsdb-server command so that vswitchd can > > connect > > > > to > > > > > > teh > > > > > > > database server. Now, ofctl needs to connect to the switch. So, > > which > > > > > > > command do I use the ptcp option with so that the switch is > > listening > > > > on > > > > > > a > > > > > > > tcp port that ofctl can connect to. Right now, when i do an ofctl > > > > show > > > > > > > tcp:127.0.0.1, i get a connection refused error. > > > > > > > > > > > > > > Thanks, > > > > > > > Aish > > > > > > > > > > > > > > On Mon, Sep 12, 2011 at 3:32 PM, Ben Pfaff <b...@nicira.com> > > wrote: > > > > > > > > > > > > > > > On Mon, Sep 12, 2011 at 03:29:38PM -0700, Aishwarya wrote: > > > > > > > > > The ovs-ofctl uses either a unix socket or tcp port to > > connect to > > > > the > > > > > > > > open > > > > > > > > > flow switch. When I start the openvswitch process, which > > command > > > > do i > > > > > > use > > > > > > > > to > > > > > > > > > set the switch in the listen mode so that ofctl can connect > > to > > > > it? > > > > > > > > > > > > > > > > Do you want to connect to ovs-ofctl over a unix socket or a tcp > > > > > > > > socket? > > > > > > > > > > > > > > > > > > > > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
