Hi,xinming.Have you build the click and OVS on the same machine?Recently I am trying to do this.I want to build the OVS and Click together on OpenWRT,but I have some problems:The OVS worked fine on attitude_adjustment but failed on backfire,while the click worked fine on backfire but failed on attitude_adjustment.Have you encounter this problem? Or which machine you put the OVS and click?
2014-09-29 8:11 GMT+08:00 <[email protected]>: > 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 message 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. OVS co-exist with Click router? (Xinming Chen) > 2. Re: OVS co-exist with Click router? (Justin Pettit) > 3. Re: OVS co-exist with Click router? (Xinming Chen) > 4. Re: how can 2 ports in different bridge communicate? (Ben Pfaff) > 5. Re: OVS co-exist with Click router? (Justin Pettit) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 28 Sep 2014 17:34:56 -0400 > From: Xinming Chen <[email protected]> > To: [email protected] > Subject: [ovs-discuss] OVS co-exist with Click router? > Message-ID: > <CAFACWXd9dbvXrBHAVZSAFP= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi All, > For some reason we want to put OVS and Click modular router on the same > machine, setting up the OVS as an OpenFlow switch to route IPv4 traffic, > and Click to route IPv6 traffic. > But we haven't find a way to have both of them working. Both Click and OVS > uses kernel modules to intercept packets. And to my understanding, if a > packet goes into OVS, it will be controlled by OVS until it is sent out of > a port. The same applies to Click. > Is there a way that can classify the packets and make OVS only intercept > the IPv4 packets? or is there a way that OVS can hand the packet to Click > once it recognice an IPv6 packet? > > Thanks! > > -- > Xinming Chen > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://openvswitch.org/pipermail/discuss/attachments/20140928/c6a9993a/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Sun, 28 Sep 2014 15:25:12 -0700 > From: Justin Pettit <[email protected]> > To: Xinming Chen <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [ovs-discuss] OVS co-exist with Click router? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Can you connect OVS and Click with something like veths? > > --Justin > > > > On Sep 28, 2014, at 2:34 PM, Xinming Chen <[email protected]> > wrote: > > > > Hi All, > > For some reason we want to put OVS and Click modular router on the same > machine, setting up the OVS as an OpenFlow switch to route IPv4 traffic, > and Click to route IPv6 traffic. > > But we haven't find a way to have both of them working. Both Click and > OVS uses kernel modules to intercept packets. And to my understanding, if a > packet goes into OVS, it will be controlled by OVS until it is sent out of > a port. The same applies to Click. > > Is there a way that can classify the packets and make OVS only intercept > the IPv4 packets? or is there a way that OVS can hand the packet to Click > once it recognice an IPv6 packet? > > > > Thanks! > > > > -- > > Xinming Chen > > _______________________________________________ > > 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/20140928/52b8d9fd/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Sun, 28 Sep 2014 19:18:21 -0400 > From: Xinming Chen <[email protected]> > To: "[email protected]" <[email protected]> > Subject: Re: [ovs-discuss] OVS co-exist with Click router? > Message-ID: > <CAFACWXcidMWPissZUJ+ywiyovvj1ef0-4=FNyTydtH5= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > Do you mean IP alias like eth1:0, eth1:1? I've tried that but OVS can't see > any packet on alias interfaces. > If this is not what you mean, can you give me a link of veths? I'd be glad > to try them out. > > Thanks, > Xinming > > 2014-09-28 18:25 GMT-04:00 Justin Pettit <[email protected]>: > > > Can you connect OVS and Click with something like veths? > > > > --Justin > > > > > > On Sep 28, 2014, at 2:34 PM, Xinming Chen <[email protected]> > wrote: > > > > Hi All, > > For some reason we want to put OVS and Click modular router on the same > > machine, setting up the OVS as an OpenFlow switch to route IPv4 traffic, > > and Click to route IPv6 traffic. > > But we haven't find a way to have both of them working. Both Click and > OVS > > uses kernel modules to intercept packets. And to my understanding, if a > > packet goes into OVS, it will be controlled by OVS until it is sent out > of > > a port. The same applies to Click. > > Is there a way that can classify the packets and make OVS only intercept > > the IPv4 packets? or is there a way that OVS can hand the packet to Click > > once it recognice an IPv6 packet? > > > > Thanks! > > > > -- > > Xinming Chen > > > > _______________________________________________ > > 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/20140928/e7a95125/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Sun, 28 Sep 2014 16:53:01 -0700 > From: Ben Pfaff <[email protected]> > To: ychen <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [ovs-discuss] how can 2 ports in different bridge > communicate? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Sun, Sep 28, 2014 at 01:45:51PM +0800, ychen wrote: > > I am confused about the usage of multi bridge in openvswitch. > > 1. under which environment will we use multi bridge? > > 2. how can 2 ports in different bridge communicate? exp: > > Q: How do I connect two bridges? > > A: First, why do you want to do this? Two connected bridges are not > much different from a single bridge, so you might as well just have > a single bridge with all your ports on it. > > If you still want to connect two bridges, you can use a pair of > patch ports. The following example creates bridges br0 and br1, > adds eth0 and tap0 to br0, adds tap1 to br1, and then connects br0 > and br1 with a pair of patch ports. > > ovs-vsctl add-br br0 > ovs-vsctl add-port br0 eth0 > ovs-vsctl add-port br0 tap0 > ovs-vsctl add-br br1 > ovs-vsctl add-port br1 tap1 > ovs-vsctl \ > -- add-port br0 patch0 \ > -- set interface patch0 type=patch options:peer=patch1 \ > -- add-port br1 patch1 \ > -- set interface patch1 type=patch options:peer=patch0 > > Bridges connected with patch ports are much like a single bridge. > For instance, if the example above also added eth1 to br1, and both > eth0 and eth1 happened to be connected to the same next-hop switch, > then you could loop your network just as you would if you added > eth0 and eth1 to the same bridge (see the "Configuration Problems" > section below for more information). > > If you are using Open vSwitch 1.9 or an earlier version, then you > need to be using the kernel module bundled with Open vSwitch rather > than the one that is integrated into Linux 3.3 and later, because > Open vSwitch 1.9 and earlier versions need kernel support for patch > ports. This also means that in Open vSwitch 1.9 and earlier, patch > ports will not work with the userspace datapath, only with the > kernel module. > > > ------------------------------ > > Message: 5 > Date: Sun, 28 Sep 2014 17:11:38 -0700 > From: Justin Pettit <[email protected]> > To: "=?utf-8?Q?discuss=40openvswitch.org?=" <[email protected]>, > Xinming Chen <[email protected]> > Subject: Re: [ovs-discuss] OVS co-exist with Click router? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Those are aliases. ?Here's some documentation on veths: > > http://backreference.org/2013/06/20/some-notes-on-veth-interfaces/ > > --Justin > > > On September 28, 2014 at 4:19:03 PM, Xinming Chen ([email protected]) > wrote: > > Do you mean IP alias like eth1:0, eth1:1? I've tried that but OVS can't > see > > any packet on alias interfaces. > > If this is not what you mean, can you give me a link of veths? I'd be > glad > > to try them out. > > > > Thanks, > > Xinming > > > > 2014-09-28 18:25 GMT-04:00 Justin Pettit : > > > > > Can you connect OVS and Click with something like veths? > > > > > > --Justin > > > > > > > > > On Sep 28, 2014, at 2:34 PM, Xinming Chen wrote: > > > > > > Hi All, > > > For some reason we want to put OVS and Click modular router on the same > > > machine, setting up the OVS as an OpenFlow switch to route IPv4 > traffic, > > > and Click to route IPv6 traffic. > > > But we haven't find a way to have both of them working. Both Click and > OVS > > > uses kernel modules to intercept packets. And to my understanding, if a > > > packet goes into OVS, it will be controlled by OVS until it is sent > out of > > > a port. The same applies to Click. > > > Is there a way that can classify the packets and make OVS only > intercept > > > the IPv4 packets? or is there a way that OVS can hand the packet to > Click > > > once it recognice an IPv6 packet? > > > > > > Thanks! > > > > > > -- > > > Xinming Chen > > > > > > _______________________________________________ > > > discuss mailing list > > > [email protected] > > > http://openvswitch.org/mailman/listinfo/discuss > > > > > > > > _______________________________________________ > > discuss mailing list > > [email protected] > > http://openvswitch.org/mailman/listinfo/discuss > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > > > ------------------------------ > > End of discuss Digest, Vol 63, Issue 58 > *************************************** >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
