1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

QoS and Netflix

Discussion in 'Tomato Firmware' started by joedr, Jul 7, 2011.

  1. joedr

    joedr Networkin' Nut Member

    All,

    I am looking for ways of prioritize Netflix streaming traffic thru QoS.

    So far, the only information I got off different blogs and forums is to include the differnt IPs where Netflix use to serve the streaming content. Is there is any better way to do this?

    I do not like the idea of checking every time Netflix change IP sets due to expansion, changes, etc.

    Here is the list of IPs:

    Thanks!

    -Joed
     
  2. Always-wondering

    Always-wondering Networkin' Nut Member

    I feel your pain.... Take the IP's you have, use this link : http://whois.domaintools.com/ (for example) - get the full IP address range for of your addresses. The full range can go into the QoS rules as a single line (per range).
    Here's a list of my most recent video (class B) rules. (I wish the Lvl 7 rules worked!)

    To 91.0.0.0-91.255.255.255
    TCP/UDP B U-Tube video

    To 208.75.76.0-208.75.79.255
    TCP/UDP B NetFlix

    To 204.160.0.0-204.163.255.255
    TCP/UDP B LvL 3 (Netflix /HBO carrier)

    To 206.32.0.0-206.35.255.255
    TCP/UDP B LvL 3 video carrier

    To 209.244.0.0-209.247.255.255
    TCP/UDP B LvL 3 (Netflix carrier)

    To 8.0.0.0-8.255.255.255
    TCP/UDP B LvL.3 video carrier

    To 208.111.128.0-208.111.191.255
    TCP/UDP B Limelight Networks media carrier

    To 69.164.0.0-69.164.63.255
    TCP/UDP B Limelight

    To 68.142.64.0-68.142.127.255
    TCP/UDP B Limelight
    TCP/UDP
    Dst Port: 1935 B RTMP (real time media player)

    To 69.175.0.0-69.175.127.255
    TCP/UDP B Web75 - video
     
    CardinS2U likes this.
  3. Toastman

    Toastman Super Moderator Staff Member Member

    #2 , Try L7 HTTPvideo and L7 flash video, works with most youtube video clips and full movies. Most of the stuff I tried today wasn't covered by your range of 91.0.0.0-91.255.255.255 but the L7 filters work fine for almost everything. I can't test netflix though.
     
  4. Always-wondering

    Always-wondering Networkin' Nut Member

    What I have seen ('cause I watch our very public network patterns a lot), is that the L7 rules generally don't catch the longer video streams. So, as I eventually worked my self out of condition rule space (only have 50 avail.) - and since I try to keep categories open for VoIP, gen'l browsing, Apple / MS downloads, IM and others.... the only really sure fire approach is to get IP ranges. -This is of course somewhat 'reactive', rather than 'predictive' - but is effective........... right up until some major network server bank opens up another block of IP addresses.

    -What is really somewhat annoying (recently) is that I have come across some (transient thankfully) users that are UPLOADing video. -Talk about snubbing L7..... it didn't catch a video upload....... let alone previous 'indications' of video downloads. It was at that point, that I over-wrote the http:video L7 rule w/something more concrete... like another LvL 3 communications IP range set. (Google has a 'tool' available now that appears to behave much like a (one way) bit torrent). It blew through every condition I had set - hogging my port 80/443 outbound class - closing and opening ports and effectively avoiding all my P2P rules. - But I digress. -I think it was you Toastman that had posted a while ago that the L7 project had unfortunately stopped some time ago??

    In the end- if you have the rule space, go ahead, use the L7's - they are easy - but if it doesn't appear to work reliably, then I think the only way to go is to become an "IP" detective....:ninja:
     
  5. CardinS2U

    CardinS2U LI Guru Member

    did u update yoru settings at all for netflix? can I get those too?

     

Share This Page