Slashdot Mirror
Thumb On the Scale? Study Finds 5 of 7 Broadband Meters Inaccurate
stox writes "For the 64 percent of Americans whose internet service provider imposes a broadband cap, and for those lucky enough to have a meter, I have some bad news. The president of the firm who audits many of the country's broadband meters says that he can't certify the measurements produced by five out of seven of his clients' meters because they don't count your bits correctly
Its all bout the money
DD-WRT has a meter I find it to be very accurate. I guess it could be used as evidence if things do not match.
When they were enforcing the 250 gig cap, they were within 1% of my dd-wrt tally. Now that they're not enforcing the cap, their reading is waaaaaay under my actual usage. I wonder if they're no longer counting traffic that stays in the Comcast network.
Perhaps we need a weights and measures type certification for ISPs?
In the US it's per County, so that will be interesting!
no other explanation is necessary. For the old folks here who used to have a landline phone service in the old days, do you remember all those mysterious little "charges" they tacked on your bill? Like $1.05 "User Service fee" and $0.87 "DCF Maintenance fee" or some crap like that? Well even the federal gov't realized they were just plain thieves and sued them, which they settled for a few dozen million dollars. And went right back to doing it again.
Also there was the dial-up modem scam the telcos used to pull... Dvorak's summary
So this means that they can't legally do 'metered billing,' as the meter is known and proven to be inaccurate, right?
right?
anybody?
An enigma, wrapped in a riddle, shrouded in bacon and cheese
DATA1=`grep eth0 /proc/net/dev | sed -e 's/ /:/g' -e 's/:\+/:/g' | cut -d: -f 3,11` /path/rrd/eth.rrd N:${DATA1}
rrdtool update
?
#
#\ @ ? Colonize Mars
#
Building an incorrect bandwidth meter is easy. Incorrect meters will calculate your bandwidth like ( 'MTU size' * 'number of packets' = usage), which will over estimate usage by a large margin (30% off is common), since a large number of packets are much smaller then MTU, DNS replies for example. It is 'somewhat' more accurate to take ('average packet size' * 'number of packets') per user, since different usage will come up with a different avg_pkt size. Counting each packets size and keeping track of it is the most accurate, but also the most resource intensive therefore the least likely to occur in bulk by the ISP.
Another place that can cause a significant skew in total bits is where bandwidth is monitored. Most ISPs count traffic before the restriction of your slow connection, therefore packet loss and re-transmits get counted against you (if the ISP uses no, or a bad queuing discipline this can end up being a significant amount of bandwidth). Monitoring how much was downloaded is best done on the CPE, such as the cable modem or dsl modem, but that would lead to firmware hacks and such to lie to the provider.
... and how much is ads?
Moving to a new client's site gave me a taste of using a browser without noscript and flashblock. I discovered a number of sites are displaying multiple ads that consist of flash movies.
To view a few paragraphs of text (a couple kilobytes or so) I USED to be downloading perhaps a quarter megabyte of graphic imagery. Now I'm downloading perhaps a minute of video for each of several self-starting video ads.
Not to mention popovers-on-mouseover - including some that that darken the whole page rather than just obscuring part of it - and if I want to kill them without "pushing a 'close' button" supplied by the popover ("Push me! Push me! I'll just close the window and not download malware! I promise!) I have to reload the page all over again. Listen to that meter whir!
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I don't know how many on slashdot know networking, but there are different ways of measuring bandwidth. Are we measuring layer 2, or layer 3? Further, layer 2 can often have multiple encapsulations before even taking layer 3 into consideration. Take for example DSL which frequently uses PPPoE, which means we have both PPP and Ethernet frames in addition to the IP data and everything encapsulated therein. And if you include DSL interleaving, then do we also include the packets that had a bad checksum and were therefore discarded? (in many cases there are a lot of these) That *is* data usage by all definitions. Do we also include ingress packets that were dropped due to bad checksums? Again, that is data usage.
In my opinion, the problem is that there aren't any standards defined for measuring bandwidth. Also in my opinion, that definition should be layer 3 traffic only and nothing else.
Careful with names containing L slashdot.org/~AiphaWolf_HK slashdot.org/~AlphaWoif_HK slashdot.org/~AiphaWoif_HK
I guess it really doesn't take any facts for the idiots to start clamoring about how all business' are evil.
Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.
I'm sure these meters make mistakes both ways right? Occasionally under counting.
From the article:
"They are wrong by missing numbers by one way or another - sometimes it's over reporting, but more frequently the error is under reporting," he said. Under reporting should be a relief to those facing overage charges or service termination for going over their meters, but if the meters aren't counting the data properly, it is still a problem.
They tell me to download from "localhost" where ever that is. Wow is that site fast! Everything I've ever used is hosted there too!
A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
Someone who thinks it should be at -1 even though it's not troll, offtopic, redundant, or flamebait?
For example, wrong information, or a superbly silly statement/question that still manages to apply to the topic. Not that this applies here, I'm just answering your question.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...