Bandwidth Limit Youtube Videos

[gportillo]

Hi,

I'm trying to limit bandwidth when an user of my LAN network try to view a youtube video.

I already limit the bandwidth when an user enter on youtube. The problem is after they enter to the video, in that moment my pfsense lose the control of bandwidth and the video starts charging with all the available bandwidth of the network.

Could anyone help me to limit the bandwidth when in my LAN network an user trying to load a youtube video? I need that the video load slowly.

Regards!


[KOM]

Your problem is most likely that your classification is failing so the traffic is not being directed into your limiter.  I notice you are using an alias, youtube_com.  I'm guessing that your alias does not hold all of the IP space used by YouTube/Googlevideo.

[Harvy66]

Not to say you don't want traffic shaping, but the symptoms of having a bandwidth hog is not inherent in a network, it is a problem cause by bufferbloat. You can trivially fight bufferbloat by using Codel on your WAN and LAN and setting your bandwidth appropriately.

[chrcoluk]

youtube.com is just the portal.

video's come from googlvideo* hostnames.

the easiest way I have managed to classify youtube is to add google's ASN table to a alias via pfblockerng, but I do this to keep google higher priority than other stuff not lower.  Youtube shouldnt be causing bufferbloat as it is only a single tcp session to stream the video and also only bursts high at the start of the video.

[gportillo]

Thanks for replies,

Chrcoluk can you guide me or  show me how to add a google's ASN table to a alias via pfblockerng?

Thanks in advance!

[Harvy66]

@chrcoluk:

youtube.com is just the portal.

video's come from googlvideo* hostnames.

the easiest way I have managed to classify youtube is to add google's ASN table to a alias via pfblockerng, but I do this to keep google higher priority than other stuff not lower.  Youtube shouldnt be causing bufferbloat as it is only a single tcp session to stream the video and also only bursts high at the start of the video.

Prior to TCP BBR there was no packet pacing and even though there was a single TCP connection, going from idle to full meant that single connection would burst an entire transmission window at line rate before settling down to a sustained pace. Even a year ago, I was seeing 1Gb/s bursts from YouTube for each request as long as it was on an established connection that was idle. I am not sure if BBR is fully rolled out, but I know Google is at least in the process of.