On Tue, Apr 30, 2013 at 3:25 PM, Carlos Patricio Amigo Haering < cam...@udec.cl> wrote:
> Hi Yiannis, thank for your reply. > > I did the setup Openflow but using a normal AP, just with OpenWRT and > seems works good, the normal AP has communication with the controller and > also connect a wireless client with a wired client, but the wireless client > still doesn't receive the video successfully, barely the audio. Now I can > discard the option of the Linksys's CPU as a entire guilty. > > I don't understand what you are saying here. A normal, non-OpenFlow AP doesn't require a controller. Are you using openflow or not? > Until I see, the flows are correctly installed. The switch Openflow is a > big PC and the top command doesn't show a over CPU usage.] > When you check the case with openflow, run dpctl and see whether the statistics counters for your flows are updated. Alternatively, look whether you are receiving any packet-ins in your controller. > About the bandwidth I'm not sure how can I calculate it but I'm streaming > a HD video.mov rocorded by a Iphone 4. > > Thanks in advance. > Regards. > > El 2013-04-30 11:33, Yiannis Yiakoumis escribió: > >> Hi Carlos, >> >> - Yes, the linksys AP has a small cpu and in comparison with the >> userspace openflow implementation it might be the bottleneck. The >> TP-Link box performs much better. >> - What bandwidth do you try to stream? IIRC, the linksys could go up >> to ~10Mbps for a single flow. >> - Make sure that the flows are installed correctly and you don't get >> any misses that try to reach the controller (i.e. check that your >> stats are updated properly during the stream) >> - To roll-back to non-OF use you need to stop the openflow daemon, >> and change your /etc/config/network file so that the bridge between >> wired and wireless is properly setup (I believe the original network >> configuration that comes with openwrt should work) >> >> Let me know how this goes, >> Regards, >> Yiannis >> >> On Thu, Apr 25, 2013 at 1:28 PM, Carlos Patricio Amigo Haering >> <cam...@udec.cl [5]> wrote: >> >> Hello everybody, >>> >>> I'm doing some experiments and I have a weird behaviour(at least >>> for me) and I hope that you'll help me to figure out it. Let me >>> explain myself: >>> >>> Firstly, I did the following NON-Openflow setup: >>> http://imageshack.us/a/img21/**9611/nonof.png<http://imageshack.us/a/img21/9611/nonof.png>[1] >>> >>> >>> The video streaming server (wired host) streams a video from a >>> file using VLC and RTSP as transmission method. The client >>> >> connected >> >>> wirelessly to the access point receives the video using VLC as >>> >> well. >> >>> This setup allows the client to receive successfully the video. >>> Also, the ping has a RTT average of 4-5 ms. >>> >>> On the other hand, I did the Openflow version of the previous >>> setup: >>> http://imageshack.us/a/img835/**8893/36915524.png<http://imageshack.us/a/img835/8893/36915524.png>[2] >>> >>> >>> After add the respective flows and using the exactly same method >>> and video file to stream the video from the wired host to the >>> >> client >> >>> , I can't receive the video, barely I receive fragments of video's >>> audio and pings shows a RTT average around 12-13 ms. Why this is >>> happening? I tried too, using a HP Procurve 2500yl-24G instead of a >>> PC as a Openflow Switch getting the same results. Exists a big >>> difference between both performances. >>> >>> My main suspect is the Access point Openflow (Pantou), the AP now >>> is using Openflow, so, the packets go through the CPU and this >>> device has a tiny processor. Could be this the problem? So, in >>> this case, How o where the OpenWRT (without OF extension) process >>> the packets in the first setup? >>> >>> What do you think? >>> >>> I really appreciate some help. >>> >>> Regards. >>> >>> ______________________________**_________________ >>> openflow-discuss mailing list >>> openflow-discuss@lists.**stanford.edu<openflow-discuss@lists.stanford.edu>[3] >>> https://mailman.stanford.edu/**mailman/listinfo/openflow-**discuss<https://mailman.stanford.edu/mailman/listinfo/openflow-discuss>[4] >>> >> >> >> >> Links: >> ------ >> [1] >> http://imageshack.us/a/img21/**9611/nonof.png<http://imageshack.us/a/img21/9611/nonof.png> >> [2] >> http://imageshack.us/a/img835/**8893/36915524.png<http://imageshack.us/a/img835/8893/36915524.png> >> [3] >> mailto:openflow-discuss@lists.**stanford.edu<openflow-discuss@lists.stanford.edu> >> [4] >> https://mailman.stanford.edu/**mailman/listinfo/openflow-**discuss<https://mailman.stanford.edu/mailman/listinfo/openflow-discuss> >> [5] mailto:cam...@udec.cl >> > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
