Shaping/policing at the head end eliminates this problem, and clears up your backbone. On Jul 12, 2016 7:06 PM, "Ken Hohhof" <[email protected]> wrote:
> When this happens it basically wipes out that customer’s Internet except > for the CDN download, no matter where you do the rate limiting. Customer > of course assumes their ISP just sucks. With a lot of education, you can > convince most of them it is actually an aggressive application hogging > their entire pipe and pushing all the other applications aside. So I have > customers that whenever their VPN to work stops working, they yell upstairs > at their kid didn’t I tell you to do your Xbox downloads after I go to bed? > > One view is this isn’t a problem, customer uses bad application, feels > pain, learns not to do that. But everyone tells them it is always the > ISP’s fault. And people with fat pipes like 50 or 100 Mbps cable Internet > probably don’t experience this problem, which reinforces the idea that it’s > the ISP’s fault. > > > *From:* Darin Steffl <[email protected]> > *Sent:* Tuesday, July 12, 2016 5:42 PM > *To:* [email protected] > *Subject:* Re: [AFMUG] CDN overload > > > Why aren't you rate limiting at the core closer to your upstream? Keep the > traffic off your last mile and wireless backhaul network if you can help > it. > > Works much better to throttle at the core instead of CPE. > > Sent from my smartphone. Please excuse any typos. > On Jul 12, 2016 5:13 PM, "George Skorup" <[email protected]> wrote: > >> I have had it with these CDNs sending more traffic than the last mile can >> handle. Got a customer at 1.5Mbps on 900 FSK and they're sending to her at >> 15Mbps. Of course the AP reports RF downlink overloaded. >> >
