Re:Question about section 4.7 View OpenFlow Messages for Ping<http://archive.openflow.org/wk/index.php/OpenFlow_Tutorial#View_OpenFlow_Messages_for_Ping>in the open flow tutorial. I have a problam with this pat in the tutorial, from some reason the only kind of messages i see in the wireshark are "Hello" , and i don't see al the types written in the tutorial, thanks shimon
2014-04-09 4:49 GMT+02:00 <openflow-discuss-requ...@lists.stanford.edu>: > Send openflow-discuss mailing list submissions to > openflow-discuss@lists.stanford.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > or, via email, send a message with subject or body 'help' to > openflow-discuss-requ...@lists.stanford.edu > > You can reach the person managing the list at > openflow-discuss-ow...@lists.stanford.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openflow-discuss digest..." > > > Today's Topics: > > 1. Re: Quick experimenting with OVS on OpenWrt (Alison Chan) > 2. Re: Quick experimenting with OVS on OpenWrt (Nicholas Bastin) > 3. Re: Quick experimenting with OVS on OpenWrt (Ben Pfaff) > 4. Re: Release of libfluid: ONF Driver Competition Winner w/ > OpenFlow 1.0 and 1.3 (Christian Esteve Rothenberg) > 5. Re: Release of libfluid: ONF Driver Competition Winner w/ > OpenFlow 1.0 and 1.3 (Murphy McCauley) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 8 Apr 2014 17:29:20 -0400 > From: Alison Chan <chan7...@kettering.edu> > To: Ben Pfaff <b...@nicira.com> > Cc: d...@openvswitch.org, openflow-discuss > <openflow-discuss@lists.stanford.edu> > Subject: Re: [openflow-discuss] Quick experimenting with OVS on > OpenWrt > Message-ID: > < > cabcsdhdtuirso9sevvz6a6fxt4et-bpeahijvy1qv+woina...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Thanks Ben. I just subscribed to dev@ovs list. > > I was able to take the router back up to the lab (I had been testing > it with laptops in my office). With two gigabit ethernet hosts on the > data plane, throughput (tcp iperf) is 450~460 Mbit/s. I will test > things a bit more tomorrow (e.g. adding 802.11 clients) and if all > goes well then I will move all five of our TP-Links to OVS. > > I was not expecting throughput with OVS to be 11 times better than > Pantou throughput -- I had to double check things to make sure the > switch was still OpenFlow enabled and not just using hardware learning > switch! > > Cheers, > Alison > > 2014-04-08 13:15 GMT-04:00 Ben Pfaff <b...@nicira.com>: > > [adding ovs-dev since there might be interest there] > > > > On Tue, Apr 08, 2014 at 11:56:28AM -0400, Alison Chan wrote: > >> Hi everyone, > >> > >> I was able to get OpenVswitch running on one of our TL-WR1043ND > >> routers running OpenWrt Attitude Adjustment. I was expecting somewhat > >> better performance than Pantou, but not this much better: > >> > >> Pantou: 39.7 Mbit/s tcp iperf using static flows (in_port:1 output:2 > >> and in_port:2 output:1) > >> OVS: 94.1 Mbit/s testing the same way > >> > >> At this point, the limiting factor is one of my laptops' 10/100 > >> ethernet interface! I will try to find another computer with gigabit > >> ethernet and report back. > >> > >> Cheers, > >> -- > >> Alison ChanI > >> chan7...@kettering.edu > >> SMS: +1 909 278 7753 > >> Fax: +1 206 203 2793 > >> _______________________________________________ > >> openflow-discuss mailing list > >> openflow-discuss@lists.stanford.edu > >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > > > -- > Alison Chan > chan7...@kettering.edu > SMS: +1 909 278 7753 > Fax: +1 206 203 2793 > > > ------------------------------ > > Message: 2 > Date: Tue, 8 Apr 2014 17:51:14 -0500 > From: Nicholas Bastin <nick.bas...@gmail.com> > To: Alison Chan <chan7...@kettering.edu> > Cc: d...@openvswitch.org, openflow-discuss > <openflow-discuss@lists.stanford.edu> > Subject: Re: [openflow-discuss] Quick experimenting with OVS on > OpenWrt > Message-ID: > <CADmMkWdqjcDrPbsGE= > u8pwghbk_cc905fzxrk1ed_qpn-fc...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Tue, Apr 8, 2014 at 4:29 PM, Alison Chan <chan7...@kettering.edu> > wrote: > > > I was able to take the router back up to the lab (I had been testing > > it with laptops in my office). With two gigabit ethernet hosts on the > > data plane, throughput (tcp iperf) is 450~460 Mbit/s. I will test > > things a bit more tomorrow (e.g. adding 802.11 clients) and if all > > goes well then I will move all five of our TP-Links to OVS. > > > > There are two variants of this device - one with an AR9132 (boring white > case), and one with a QCA9558 (blue spaceship-looking thing). The AR9132 > version uses a separate switch ASIC (AR8316 - I have one of these), so your > max throughput through that device in any software forwarding (regardless > of CPU speed) will be a gigabit. The 400Mhz ARM in that box is going to > limit you even further, so 450Mbits seems a bit suspect. > > If you have the rev. 2 (blue) hardware, that is more of an unknown (I don't > have one of these to look at or tinker with) - the 9558 has a 720Mhz MIPS > core, so that's better, but I found images of a different AP that uses this > chip on the internet and it appears to use an AR8327 for the switching, so > likely there's no integrated ethernet switch on the SoC. This means your > max throughput is still probably a gigabit, and you might be able to > actually get 450Mbits through that CPU. The AR8327 actually has a 96-entry > ACL table and 64-entry VLAN translation table (as well as a bunch of more > specialized tables that would be more difficult to use well) that could be > used for hardware acceleration, but I doubt anyone has done the work to > program them. > > -- > Nick > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20140408/2957a37b/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Tue, 8 Apr 2014 16:00:23 -0700 > From: Ben Pfaff <b...@nicira.com> > To: Nicholas Bastin <nick.bas...@gmail.com> > Cc: "d...@openvswitch.org" <d...@openvswitch.org>, openflow-discuss > <openflow-discuss@lists.stanford.edu> > Subject: Re: [openflow-discuss] Quick experimenting with OVS on > OpenWrt > Message-ID: > < > cacjumbzxnbsa3-xcaurn3eujuheqjw3wttndgjw-qm-ngxm...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Apr 8, 2014 at 3:51 PM, Nicholas Bastin <nick.bas...@gmail.com> > wrote: > > If you have the rev. 2 (blue) hardware, that is more of an unknown (I > don't > > have one of these to look at or tinker with) - the 9558 has a 720Mhz MIPS > > core, so that's better, but I found images of a different AP that uses > this > > chip on the internet and it appears to use an AR8327 for the switching, > so > > likely there's no integrated ethernet switch on the SoC. This means your > > max throughput is still probably a gigabit, and you might be able to > > actually get 450Mbits through that CPU. The AR8327 actually has a > 96-entry > > ACL table and 64-entry VLAN translation table (as well as a bunch of more > > specialized tables that would be more difficult to use well) that could > be > > used for hardware acceleration, but I doubt anyone has done the work to > > program them. > > Wow, the AR8327 seems to have full public documentation: > https://lafibre.info/images/doc/201106_spec_AR8327.pdf > At a glance, it's not that general-purpose but certainly nice to > see a documented switching ASIC in a low-cost device. > > > ------------------------------ > > Message: 4 > Date: Tue, 8 Apr 2014 21:34:08 -0300 > From: Christian Esteve Rothenberg <chest...@dca.fee.unicamp.br> > To: Murphy McCauley <murphy.mccau...@gmail.com>, > "openflow-disc...@mailman.stanford.edu" > <openflow-disc...@mailman.stanford.edu> > Subject: Re: [openflow-discuss] Release of libfluid: ONF Driver > Competition Winner w/ OpenFlow 1.0 and 1.3 > Message-ID: > <CAEj5p9TOj8gTy8Pk-WOObY9Zw9ov-Q+ws5U=50w3oTk= > thg...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Thanks Murphy, > > one of my students working with POX wants to give a try and hopefullly > contribute to these efforts, can you share the pointers to that POX > branch. We can only say positive things about prototypiing with POX -- > giving it clean and effective OF1.3 support would be a neat upgrade > beneficial to all parties :) > > -Christian > > > > > > > On Mon, Mar 24, 2014 at 10:17 PM, Murphy McCauley < > murphy.mccau...@gmail.com> wrote: > >> > >> Congratulations. > >> > >> There's now POX branch that's been quickly hacked up to (sort of) use > libfluid's Python bindings. It also includes a minor patch for one of the > swig .i files. > >> > >> -- Murphy > >> > >> On Mar 22, 2014, at 5:08 AM, Christian Esteve Rothenberg < > chest...@dca.fee.unicamp.br> wrote: > >> > >> Dear OpenFlow fellows, > >> > >> in case you are not aware about the public release of the winner > implementation of the OpenFlow driver competition ( > https://www.opennetworking.org/competition) here is the pointer to the > github repository: > >> > >> http://opennetworkingfoundation.github.io/libfluid/ > >> > >> libluid may be interesting to developers of both OpenFlow switches and > controllers. It features support of OpenFlow 1.0 and 1.3, high performance, > bindings to Python and Java, easy port to different hardware architectures, > etc. > >> > >> We welcome users and developers interested in building an open > community to maintain libfluid as a useful, multi-purpose OpenFlow library > to develop switch agents and controller implementations. > >> > >> -Christian (on behalf of the libfluid team) > >> _______________________________________________ > >> openflow-discuss mailing list > >> openflow-discuss@lists.stanford.edu > >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >> > >> -- > >> Christian > > > > > -- > Christia > > > ------------------------------ > > Message: 5 > Date: Tue, 8 Apr 2014 19:49:23 -0700 > From: Murphy McCauley <murphy.mccau...@gmail.com> > To: Christian Esteve Rothenberg <chest...@dca.fee.unicamp.br> > Cc: "openflow-disc...@mailman.stanford.edu" > <openflow-disc...@mailman.stanford.edu> > Subject: Re: [openflow-discuss] Release of libfluid: ONF Driver > Competition Winner w/ OpenFlow 1.0 and 1.3 > Message-ID: <a69fefad-402b-41ec-a588-b38e3bdd2...@gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Sure, it's just the libfluid_experiment branch of the main fork: > http://noxrepo.org/git/pox/tree/libfluid_experiment > > It's definitely very much an experiment. ;) For starters, I was only > messing with 1.0 and while I used libfluid to read off the wire, the > responses are still generated with POX's OpenFlow library. I just thought > it was worth experimenting to get a sense of what would be involved. If > you guys are interested in doing much more work on this, we should talk! > > -- Murphy > > On Apr 8, 2014, at 5:34 PM, Christian Esteve Rothenberg < > chest...@dca.fee.unicamp.br> wrote: > > > Thanks Murphy, > > > > one of my students working with POX wants to give a try and hopefullly > > contribute to these efforts, can you share the pointers to that POX > > branch. We can only say positive things about prototypiing with POX -- > > giving it clean and effective OF1.3 support would be a neat upgrade > > beneficial to all parties :) > > > > -Christian > > > >> > >> > >> On Mon, Mar 24, 2014 at 10:17 PM, Murphy McCauley < > murphy.mccau...@gmail.com> wrote: > >>> > >>> Congratulations. > >>> > >>> There's now POX branch that's been quickly hacked up to (sort of) use > libfluid's Python bindings. It also includes a minor patch for one of the > swig .i files. > >>> > >>> -- Murphy > >>> > >>> On Mar 22, 2014, at 5:08 AM, Christian Esteve Rothenberg < > chest...@dca.fee.unicamp.br> wrote: > >>> > >>> Dear OpenFlow fellows, > >>> > >>> in case you are not aware about the public release of the winner > implementation of the OpenFlow driver competition ( > https://www.opennetworking.org/competition) here is the pointer to the > github repository: > >>> > >>> http://opennetworkingfoundation.github.io/libfluid/ > >>> > >>> libluid may be interesting to developers of both OpenFlow switches and > controllers. It features support of OpenFlow 1.0 and 1.3, high performance, > bindings to Python and Java, easy port to different hardware architectures, > etc. > >>> > >>> We welcome users and developers interested in building an open > community to maintain libfluid as a useful, multi-purpose OpenFlow library > to develop switch agents and controller implementations. > >>> > >>> -Christian (on behalf of the libfluid team) > >>> _______________________________________________ > >>> openflow-discuss mailing list > >>> openflow-discuss@lists.stanford.edu > >>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >>> > >>> -- > >>> Christian > > > > > > > > > > -- > > Christia > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20140408/01b051dc/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > > ------------------------------ > > End of openflow-discuss Digest, Vol 66, Issue 6 > *********************************************** >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
