Pluk On Feb 14, 2014 5:23 PM, <[email protected]> wrote: >ljpli> Send discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://openvswitch.org/mailman/listinfo/discuss > or, via email, send a messaged with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of discuss digest..." > > > Today's Topics: > > 1. Re: Basic OVS connectivity (tyler derden) > 2. Re: Basic OVS connectivity (Justin Pettit) > 3. Re: Routing on Open V switch (Justin Pettit) > 4. OVS running inside esxi (Jose Augusto de Sousa) > 5. How to get the socket descriptor (vis reddy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Feb 2014 22:12:51 +0200 > From: tyler derden <[email protected]> > Subject: Re: [ovs-discuss] Basic OVS connectivity > To: Justin Pettit <[email protected]>, "[email protected]" > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Thx Justin for your prompt response!Actually, I connected them using crossover, but what do I need to assign as an IP address for the NIC that is in the desktop (running as OVS switch) when I am connecting that NIC to another desktop's NIC (running as a host). > Thanks. > > > Date: Fri, 14 Feb 2014 11:24:36 -0800 > > Subject: Re: [ovs-discuss] Basic OVS connectivity > > From: [email protected] > > To: [email protected]; [email protected] > > > > It depends on your NICs. Most modern NICs will automatically take care of > > the cross-over, so you don't need a special cable or switch/hub. > > > > --Justin > > > > > > On 2/14/14, 10:46 AM, "tyler derden" <[email protected]> wrote: > > > > >Hello,I just have a question about the basic connectivity of OVS. I > > >installed OVS on a an ubuntu desktop that has 3 NICs, I want to connect > > >one of the NICs to another desktop ( running as openflow Controller) and > > >the other 2 NICs to two desktops ( running as Hosts ). So I just connect > > >each NIC with the other NIC on the other desktop directly using a > > >cross-over cable or I need a switch/hub in between. > > > > > > > > >Thank you in advance! > > > > > >_______________________________________________ > > >discuss mailing list > > >[email protected] > > >http://openvswitch.org/mailman/listinfo/discuss > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < http://openvswitch.org/pipermail/discuss/attachments/20140214/10e413e4/attachment-0001.htm > > > ------------------------------ > > Message: 2 > Date: Fri, 14 Feb 2014 13:19:41 -0800 > From: Justin Pettit <[email protected]> > Subject: Re: [ovs-discuss] Basic OVS connectivity > To: tyler derden <[email protected]>, "[email protected]" > <[email protected]> > Message-ID: <cf23c828.20c28%[email protected]> > Content-Type: text/plain; charset="US-ASCII" > > I'm not sure that I understand the question; it's just standard IP > connectivity. If the two hosts' IP addresses are in the same subnet, then > they should be able to just communicate with each other. > > --Justin > > > On 2/14/14, 12:12 PM, "tyler derden" <[email protected]> wrote: > > >Thx Justin for your prompt response!Actually, I connected them using > >crossover, but what do I need to assign as an IP address for the NIC that > >is in the desktop (running as OVS switch) when I am connecting that NIC > >to another desktop's NIC (running as a host). > > > >Thanks. > > > >> Date: Fri, 14 Feb 2014 11:24:36 -0800 > >> Subject: Re: [ovs-discuss] Basic OVS connectivity > >> From: [email protected] > >> To: [email protected]; [email protected] > >> > >> It depends on your NICs. Most modern NICs will automatically take care > >>of > >> the cross-over, so you don't need a special cable or switch/hub. > >> > >> --Justin > >> > >> > >> On 2/14/14, 10:46 AM, "tyler derden" <[email protected]> wrote: > >> > >> >Hello,I just have a question about the basic connectivity of OVS. I > >> >installed OVS on a an ubuntu desktop that has 3 NICs, I want to connect > >> >one of the NICs to another desktop ( running as openflow Controller) > >>and > >> >the other 2 NICs to two desktops ( running as Hosts ). So I just > >>connect > >> >each NIC with the other NIC on the other desktop directly using a > >> >cross-over cable or I need a switch/hub in between. > >> > > >> > > >> >Thank you in advance! > >> > > >> >_______________________________________________ > >> >discuss mailing list > >> >[email protected] > >> >http://openvswitch.org/mailman/listinfo/discuss > >> > >> > > > > > > > > > > > ------------------------------ > > Message: 3 > Date: Fri, 14 Feb 2014 13:21:39 -0800 > From: Justin Pettit <[email protected]> > Subject: Re: [ovs-discuss] Routing on Open V switch > To: Ashwin Prabhu <[email protected]>, > "[email protected]" <[email protected]> > Message-ID: <cf23c8bd.20c2c%[email protected]> > Content-Type: text/plain; charset="US-ASCII" > > On 2/13/14, 12:57 PM, "Ashwin Prabhu" <[email protected]> wrote: > > >Is routing as a feature already been taken care of in open vswitch? > > > >Is it possible to implement routing capability in open v switch without > >the help of controller??? > > No, you need a controller to handle routing. > > > --Justin > > > > > > ------------------------------ > > Message: 4 > Date: Fri, 14 Feb 2014 19:56:39 -0200 > From: Jose Augusto de Sousa <[email protected]> > Subject: [ovs-discuss] OVS running inside esxi > To: [email protected] > Message-ID: > <CANvQ_MzQ5wHW49H6kSnosUButDwdivW2-iGctzN= [email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > did you know if this is possible today? > > Is it exactly i trying do > http://openvswitch.org/pipermail/discuss/2012-December/008626.html > > But doesn't work too.... > > i did 2 setup > > first one with native vlan linux > ovs-vsctl add-br br0 > ovs-vsctl add-port br0 eth1 > ovs-vsctl add-port br0 eth1.20 > ovs-vsctl add-port br0 eth2 > > > bfe59603-c7fd-4d2d-8c9c-675ae8796c7f > Bridge "br0" > Port "br0" > Interface "br0" > type: internal > Port "eth1" > Interface "eth1" > Port "eth1.20" > * Interface "eth1.20"* > Port "eth2" > Interface "eth2" > ovs_version: "2.1.90" > > This work well > > and a second with internal interface and vlan. > > ovs-vsctl add-br br0 > ovs-vsctl add-port br0 eth1 > ovs-vsctl add-port br0 eth2 > ovs-vsctl add-port br0 vlan20 tag=20 -- set interface vlan20 > type=internal > > > ovs-vsctl show > bfe59603-c7fd-4d2d-8c9c-675ae8796c7f > Bridge "br0" > Port "br0" > Interface "br0" > type: internal > Port "vlan20" > tag: 20 > * Interface "vlan20"* > * type: internal* > Port "eth1" > Interface "eth1" > Port "eth2" > Interface "eth2" > ovs_version: "2.1.90" > > > Both are connected in esxi portgroup vds with trunk configuration, if eth1 > and eth2 in common access, the vds are setup for promisc mode. > > > some one know if this work today? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < http://openvswitch.org/pipermail/discuss/attachments/20140214/316fc41e/attachment-0001.htm > > > ------------------------------ > > Message: 5 > Date: Fri, 14 Feb 2014 13:16:00 -0800 (PST) > From: vis reddy <[email protected]> > Subject: [ovs-discuss] How to get the socket descriptor > To: "[email protected]" <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hello All > I am porting the openvswitch as a library in a new process on a new hardware ?and had written ?netdev and ofproto providers that suits my hardware, ?i have my own select call on various file descriptor that are used to talk to different process in my hardware, problem is i am not able to get the file descriptor that openvswitch uses to communicate to the controller, went through the stream classes and not able to see any methods that will give the file descriptor that had been assigned for the socket, could you please mail if there is any method to get the file descriptor of the socket . I have ?access to ?connmgr and do not want to change ?openvswitch code to have an extern for the file descriptor at the place where the socket is created. > Thanks > Vishnu > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < http://openvswitch.org/pipermail/discuss/attachments/20140214/7d2dec22/attachment.htm > > > ------------------------------ > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > > > End of discuss Digest, Vol 56, Issue 38 > ***************************************
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
