Ask Slashdot: How Can I Prove My ISP Slows Certain Traffic?
Long-time Slashdot reader GerryGilmore is "a basically pretty knowledgeable Linux guy totally comfortable with the command line." But unfortunately, he lives in north Georgia, "where we have a monopoly ISP provider...whose service overall could charitably be described as iffy."
Sometimes, I have noticed that certain services like Netflix and/or HBONow will be ridiculously slow, but -- when I run an internet speed test from my Linux laptop -- the basic throughput is what it's supposed to be for my DSL service. That is, about 3Mbps due to my distance from the nearest CO. Other basic web browsing seems to be fine... I don't know enough about network tracing to be able to identify where/why such severe slowdowns in certain circumstances are occurring.
Slashdot reader darkharlequin has also noticed a speed decrease on Comcast "that magickally resolves when I run internet speed tests." But if the original submitter's ultimate goal is delivering evidence to his local legislators so they can pressure on his ISP -- what evidence is there? Leave your best answers in the comments. How can he prove his ISP is slowing certain traffic?
Slashdot reader darkharlequin has also noticed a speed decrease on Comcast "that magickally resolves when I run internet speed tests." But if the original submitter's ultimate goal is delivering evidence to his local legislators so they can pressure on his ISP -- what evidence is there? Leave your best answers in the comments. How can he prove his ISP is slowing certain traffic?
They might not be slowing down specific traffic but instead just have a poor connection to those popular services and it gets saturated.
The Official Site of 1337 Pwnage
Traffic slowed by your ISP, and traffic slowed further down the chain - for instance by poor peering - are indistinguishable. With some help from hops further along like Netflix (or within the ISP) you may be able to pinpoint the exact problem. However, given that so many providers are capable of routing Netflix at acceptable speeds it also doesn't matter, it's obviously your ISP's responsibility.
Until the government ensures a quality service on ISPs to make them similar to land-line phones (common-carrier), it doesn't really matter if you complain about small things you find. I have had VOIP blocked by the ISP due to their competing service, and have had speed issues that looked better with the speed test, but it really can't get resolved until the government cares about the Internet as critical infrastructure which can easily damage the economy.
wireline might be a problem. Before the ISP side of the network.
Streaming services will often consider a users connection and change their streaming service to what they think will offer the best experience.
Long term support any innovative new community broadband network and see how the different networks do networking?
Freedom of choice.
Support a better new network.
Domestic spying is now "Benign Information Gathering"
Find a free vpn service, like vpngate, and run your connection over to a site (other than netflix, due to geoblocking) that normally runs slow for you. If your speed sees an increase, then yes they are throttling traffic to certain websites. If your speed is the same or less then no your connection to the outside world is just shitty. That is the #1 benefit to vpns for the consumer imho. Unless it is a specific service they are degrading they can't tell who your vpn connects to, and either they throttle all vpns, which commercial users would frown upon, or they throttle none of them beyond regular bandwidth limits and you can find out if that is where the problem lies.
https://fast.com
This site uses the same servers as the Netflix streaming service so it should be a clear indicator. You should note though that 3Mbps isnâ(TM)t very fast when it comes to playing streaming video. An HD stream from Netflix can easily hit 7 or 8 Mbps.
1. Get job working for ISP
2. Slow certain traffic
3. Film yourself
4. Post video to youtube
Profit
Many ISPs large and small explicitly add rules prioritizing speed test servers over normal traffic. To this day it baffles me why ISPs are getting away not only with blatant violation of NN by prioritizing specific destinations over others but with what is essentially intentionally misleading their customers with bogus results as a consequence of prioritizing speed tests. The trick to obtain meaningful results is in finding much less known speed test servers or just downloading large files from a sampling of random sites. This will win you a better baseline to reason about the speeds you are actually getting.
It's otherwise really hard to tell on an individual destination basis for sure WTF is going on ... where the bottleneck really lies. You can trace paths and grab routes from looking glasses and shit yet as an end user this shit is rarely worth doing or conclusive. Smaller ISPs ... especially WISPs have bandwidth management boxes some of the layer 7 variety that execute all manner of wizardry the end user has little to no hope of deciphering.
I'm on several industry mailing lists where ISPs often bitch about what is a very common luser complaint about how ISP is preventing them from access something or is responsible for slowing down their access to something. To be fair MOST of the time a user arriving at such conclusions is in fact both clueless and WRONG yet when ISPs pull shit like this it's really hard to sympathize with the ISP.
The marketing of speeds is especially is difficult because they don't guarantee any particular speed to any particular destination, they often don't disclose details about bandwidth management or the fact they are prioritizing speed test servers. Often times the concept that speeds are not guaranteed for every site is not communicated in any marketing materials and is hard for end users especially ones who have no technical knowledge of the workings of Internets.
its not that hard
but you have to have at least two connections to compare the traffic
a study that was funded by a USA national science award does exactly this :
simply download a app and run it
http://bit.ly/2IAdbmD
you can thank me on twitter if you like http://twitter.com/johnjonesname
Video is very susceptible to jitter
No it isn't.
Streaming is a complex game and it can get disrupted in many ways. Packet loss, jitter, reordering, buffer-bloat, brief interruptions on traffic spikes, etc. all things that are no so bad with TCP can really, really mess up streaming. My guess would be that the streaming services all use a very similar set of parameters for their protocols that in general work reasonably, but with your connection does not work well at all. The solution to that would ordinarily be to just download the files and then play locally.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Netflix has servers in strategic positions within most ISPs, or in some cases just outside. Please see:
https://media.netflix.com/en/c...
In addition, Netflix automatically adjusts the video resolution depending upon the bandwidth of the connection.
Depends entirely on what is used for flow-control and how much buffering is done. Jitter can have minimal effect on that or it can shoot things to hell.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Many devices allow you to check your connection speed within the Netflix app. (I would presume HBONow offers a similar utility.) The Netflix Page explaining how to do this is here: https://help.netflix.com/en/no.... On the same Netflix page are their internet download speed recommendations for playing TV shows and movies: 0.5 Megabits per second - Required broadband connection speed 1.5 Megabits per second - Recommended broadband connection speed 3.0 Megabits per second - Recommended for SD quality 5.0 Megabits per second - Recommended for HD quality 25 Megabits per second - Recommended for Ultra HD quality Remember that these figures are per stream, so concurrent streaming to multiple devices is bandwidth additive.
I'm not an expert on these things, but maybe do it from the outside? Set up an internet facing server on your network and then push and pull data using a known honest provider.
https://tech.slashdot.org/stor...
[($)]
Has darkharlequin done something to displease the editors?
A good way to find where a connection is being slowed is to use MTR, or on Windows WinMTR. It's a combination of ping and traceroute that can show where the network becomes slow, or error rates become high between you are the server you are using.
For many years I've tested my connection on comcast.
If it's a popular or well publicized test site, comcast gives back great numbers.
On the other hand, if you use any of the various ways to obfuscate the address, or just use one comcast doesn't have on it's script yet, then you'll see MUCH lower speeds.
Yes, there are ways to verify that the obfuscation isn't causing the slowdown.
Short version, comcast slows you down unless they know they're being tested, then they give you a higher bandwidth. I've tested them for close to 10 years now, and it's always the same.
where the people live and breath this stuff 24/7/365. http://www.dslreports.com/forums/
This will sound odd, but try a VPN over the same connection.
I found my ISP was slowing down all traffic, apart from to speedtest.net and other speed testing sites.
However, they were not slowing down VPN traffic.
After running all my traffic for a month over a VPN, my speeds were 10x faster and not slowing down at peak times.
Then I received a call from my ISP kindly asking me to leave. I'm now with a decent ISP.
If you're a Windows user, sometimes the system will switch back to the default ISP's DNS for certain programs (Edge browser *cough cough*) and not just p2p/torrent stuff because, and like we Linux users keep trying to say, they are evil, assuming that all the ads and tracking doesn't give you away or if Micro$oft itself made a deal to throttle on behalf of the ad related conpitition. How else can Cortana give Micro$oft their untainted data fix if your lying to her or get you to use Bing instead of Google? Skype instead of literally anything else? Payed subscriptions instead of free and open source cross platform tools? I even have people telling me their Windows system is warning them that Firefox is an insecure web browser because they clearly want them to use IE or Edge. Classic web browser war bs, but they go much further than that now and you don't get a much of a choice these days. I guess I'm saying it could actually be your Windows 10 system being a dick instead of the ISP. Linux users will not wave it in your face like you think if you switched unless you picked pure Ubuntu (they're partners of sorts). Using WSL isn't going to help. Also, using ping isn't going to help either because it only rates the response time and not the amount of data transferred which is what the ISP is going to look at. It might not hurt to check anyway because maybe it's the just servers acting up.
It tests using Netflix so you can compare to other speed testers.
https://fast.com/
If you have an Android or iOS device, then download the Wehe app and run it while you're connected to your home WiFi. It was developed by university researchers to detect slowdowns of certain streaming services.
My ISPs dirty little secret is that it routes all http(s) traffic through a proxy cache server, so most popular websites run load great but everything else is often slow.
You are welcome.
Your math is wrong. All you have to do to prove it is to run Wireshark or a switch with a promiscuous port and log how much data has passed through your connection. Or download the same title for offline viewing in full HD quality. Those bandwidth numbers match up with a number of HD torrents of high quality and carefully tuned encoding.
He says he get a standard 3 Mpbs from his ISP. This is about the speed required for a non-buffering stream from Netflix. So any small dip in speed or the use of a second application at the same time as Netflix would result in buffering. Doesn't mean the ISP is not throttling but it could just be that the standard speed is not up to the job.
"He took a duck in the face at 250 knots." -- William Gibson, Pattern Recognition
I can't use SFTP to access my Godaddy account over Roger's infrastructure in Canada. I have ISP accounts with Carrytel and Tecksavvy both using Rogers cable infrastructure and my traffic is blocked. However when I use Bell everything works fine. Godaddy support was good, Tecksavvy is always amazing but we couldn't resolve it and rogers was completely unhelpful.
Has anyone else experienced this and been able to resolve it?
The company lies about its internet speeds but all of my customers know that and still subscribe to them.
The company lies about its internet speeds but all of my customers know that and unfortunately have no choice but to subscribe anyway.
FTFY
Cheap storage VM.
Last night netflix movies would simply get to 20% (of the way to starting the movie) and stop, meaning the movie never actually started. In every case it got to 15% or up to 23% and...no further. I tried several times on each of several movies.
Switched to amazon prime and no delay, fast response, worked fine right away.
I was asking myself how I could check on comcast (the only ISP available here).
It's a TV, so no obvious way to run a speed test on it.
Please note, the OP asks for the ways that can be accepted as a legal means. I would set up some host on the internet with public IP, and set the pack of speedtests (for instance using iperf) using different TCP/UDP ports. If the tests will show some significant differences on the ports used by P2P, than for ports 80/443 for example, this could be accepted as a proof, I suppose.
If Ayn Rand had had to deal with Comcast, she probably would have embraced Marxism.
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
Depends entirely on what is used for flow-control and how much buffering is done. Jitter can have minimal effect on that or it can shoot things to hell.
No it doesn't. The streaming services use TCP. Jitter and even packet loss are often concealed by the receive window depending on where event occurs. It's a statistical game where to win you need only a buffer big enough to account for transient conditions and of course channel capacity larger than consumption rate.
Massive jitter or packet loss at tail can indeed stall a stream and even result in visually affecting output yet TCP protocol is reasonably well designed and capable of efficient bulk transmission which is all that is necessary for video streaming services.
Remember parents comment was "Video is very susceptible to jitter" which is simply false despite ones ability to concoct ridiculous scenario where jitter becomes service affecting.
1. Use pchar to establish the bandwidth and packet loss ICMP sees between endpoints.
2. Craft packets that contain magic numbers or magic strings, I'm pretty sure that's hping, and see if there are behaviours that only occur with given sequences regardless of endpoints.
3. Traverse the same segment of net using an encrypted tunnel, as encryption is slow. If this causes a massive acceleration, then it cannot be explained by a change in path, only by a change in visibility.
4. Use a proxy that is on the other side, so you traverse the same path but alter the visible destination endpoint. This will detect the most common form of hostile traffic shaping.
If you detect an obvious, reproducible, pattern then you have shown hostile traffic shaping and the form it has taken.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
https://ooni.torproject.org/
HTH
"When information is power, privacy is freedom" - Jah-Wren Ryel
I've read most of the threads; some good knowledge out there. As said dozens of times, very difficult to pinpoint troubles. I mean, consider the architectures: Last Mile terminates inside a carrier's pop. From there on out, its kind of a crap-shoot. Even peering links get saturated (drops occur), even go down, in which case re-routes come into play. The internet's advertised functionality is a survivable cloud, where re-routes fix saturated or downed links. In principle. Working for tw telecom for a few years in their noc as a repair tech, outages and the like impact traffic in crazy ways. Without direct knowledge of what links are running at capacity, or what outages are going on it is just so hard to really maintain path integrity. And that's for enterprise customers, who pay through the nose for SLA. Residential broadband is at the bottom of the priority list, virtually always Best Effort. Which means exactly what it says. Factor in the corollary effects of *cough* net neutrality --it is my hope Ajit Pai can never take a cup of coffee in public again without risk of a beating-- we are indeed in a brave new world of throughputs and L2/L3traffic classifications. It is easy to rail at the ISP, but unless as a user you contract for SLA, and in specific SLA to that which is important to you, the Interweb will ALWAYS be a crap-shoot. The miracle is that it works as well as it does.
--I do what I can, I work in the dark.
I would love to see a standalone application that runs through enough encryption that the ISP can't selectively speed-up or slow down, that uniformly randomly tracks speed to at least one main (not advertiser/spam) site from my computer through my ISP and makes the results public. I would love to see a non-profit make this happen.
Every single customer of every single ISP would want this software. It would allow hundreds of millions of people to keep someone who has a monopoly over them honest. It would "the next killer windows program".
I think there are hundreds of millions of customers in the US who would like to see this. I think it would put teeth and a few hundred million customers behind "net neutrality" support, and make it happen. It might lead to internet access as a public utility, instead of toll roads and monopolies on driveway - which is what we have now.
Netflix is Amazon, which is insanely huge architecture and throughput. I can't imagine Netflix being the slow one. I can't not imagine your ISP being the slow one. They do this crap all the time. It is crap like this that drives cord-cutting. If AT&T/Verizon/Sprint weren't so miserly in their approach to cell phones, they could stunningly vastly improve their income by making an equivalent service to compete in the land of monopolies. If half of all ISP's are effectively a monopoly, and if the telecom just went "same price for same alleged service" then majority of all ISP customers would move, because ISP's don't make their on-paper commits in real life and lots of people are angry about it. Telecoms can't find the will to do that. Truth, however, would be transformative. If the ISP was measured/shown to be the ass every time they cheat, and they can't not cheat, then you would see what happens.
Your ISP probably doesn't slow down anything. It's just that they didn't partner with the content delivery networks of some popular services. There are often disagreements on who is going to pay... As a result, all Netflix or whatever traffic goes through small pipes that are not designed to handle such heavy loads.
If you notice that speeds vary during the day, with prime time being the slowest, than that's must be what happens. The mitigation is to force the data to take a different path, one that is not saturated. The obvious way is to use a well connected VPN, but sometimes, just using DNS tricks in order to use a different server than the "closest" one can do the trick.
Neither of these statements is particularly precise, but the first is general enough that your response starting with "no" is less correct. TCP is very sensitive to loss. These are my favorite links on this subject:
Jitter is not the same thing as packet loss (PL). My response is about Jitter not packet loss.
When I said "Jitter and even packet loss are often concealed by the receive window depending on where event occurs" this means TCP has machinery capable of dealing with out of order receipt and sequence gaps in most cases without stalling the stream for round trip or worse RTO. Mentioning PL was intended only to highlight this capability.
It sure as heck does not mean TCP congestion algorithms should ignore congestion indications in the form of PL. Even a small percent PL to borrow a phrase from Joe is "a big fucking deal" shit had better slow down dramatically in that case. I only mention PL at all to illustrate a point about designed capability of TCP.
Real time communications systems generally have a "jitter buffer" reserving some delay up front in order to allocate time to reorder packets if necessary. This simply doesn't exist in any practical way with streaming of static content.
My favorite is when my allegedly >100MB line is so slow loading web content (not streaming, just web content) that when I go to SpeedTest.net it immediately says "dude you're great at more than 100MB!" but the test results come back before the logo for the page downloads... Essentially I am getting canned results before a 64k graphic can download. Should be called SpeedFraud.net.
Every ISP I've used for the past twenty years have been doing this kind of game. Just like how the airlines oversell capacity. Totally unethical? Absolutely. Illegal? Not really.
Net neutrality is all we got to keep these companies honest, and even that isn't enough anymore.
"The mind is a terrible thing to, um, uh, oh bollocks." -- Me
of course I don't know what the mod was. But I don't think the rpi can go that fast. After all the ethernet connects to the cpu over USB2 and the wireless isn't that fast. Maybe they sandwiched a special interface card to the top, but if they can do that they can probably do without the pi.
Nullius in verba
....let me say that I very much appreciate the feedback from the /. community. As usual, a varied mix of great input, doom-mongering and nonsense. What I love about /. !!
Having worked in the industry in Australia, I've got a fair idea what the cause is.
I know Australia and the US are a little different, but the general theory remains the same - what you're probably looking at is QoS. They're not slowing the netflix traffic per se, they're just prioritising other traffic such as the speed tests.
Most streaming suppliers will have a big juicy link from their datacentres to prominent peering points. You can pretty much guarantee that it's your ISP and their choice of backhaul or their choice of backhaul supplier who are at fault if you're seeing traffic prioritisation affect your streaming.
Comcast deliberately and specifically used to slow down Netflix traffic. Prior to Netflix paying them for peering.
I had Comcast's 25mbps speed package, but couldn't stream Super or 3D content. Bandwith was too slow. Dropped my service down to 3mbps. Netflix and Comcast signed peering agreement. Suddenly, the very next day my 3mbps connection was fast enough to stream 3D content from Netflix.
Ya....don't give me the congestion BS. The telcos very knowingly throttle certain content.
Greedy bastitches.
Comcast deliberately and specifically used to slow down Netflix traffic. Prior to Netflix paying them for peering.
I had Comcast's 25mbps speed package, but couldn't stream Super or 3D content. Bandwith was too slow. Dropped my service down to 3mbps. Netflix and Comcast signed peering agreement. Suddenly, the very next day my 3mbps connection was fast enough to stream 3D content from Netflix.
The telcos very knowingly throttle certain content.
https://www.measurementlab.net... has some good tests. Sadly, some of old Net Neutrality tests have died there - but some of their stuff remains and is good. Back when this fight started, Google backed some groups working to make speed tests that detect if specific slowing was going on - all those tests are at this site - even though the public servers behind them are offline now. Cheers.
Comcast has more lobbyists and lawyers than you. You'll never win. Ever.
Unless you just want to prove the point for argument's sake.
Then I bid you godspeed, sir.
Scruting the inscrutable for over 50 years.