Bell Canada Throttles Wholesalers Without Notice 239
knorthern knight writes "The Canadian family-run ISP Teksavvy (which is popular among Canadian P2P users precisely because it does not throttle P2P) has started noticing that Bell Canada is throttling traffic before it reaches wholesale partners. According to Teksavvy CEO Rocky Gaudrault, Bell has implemented 'load balancing' to 'manage bandwidth demand' during peak congestion times — but apparently didn't feel the need to inform partner ISPs or customers. The result is a bevy of annoyed customers and carriers across the great white north."
Just before everyone gets excited.... (Score:2, Insightful)
This isn't specifically throttling p2p traffic. It's using a proxy load balancing system to spread the load during peak hours which may lead to congestion. ISP's all over the world do it, in Australia the 2nd and 3rd biggest ISP's - Optus and TPG both implement transparent proxies for load balancing.
Obviously doing it before the traffic reaches wholesalers is a tad unethical, and I'm not condoning it, but the issue shouldn't be confused with specifically targeting p2p traffic.
Re: (Score:2)
Re:Just before everyone gets excited.... (Score:5, Funny)
Re: (Score:2)
Re:Really? (Score:5, Insightful)
- $15 a month for economy service (~50 gigs limit)
- $30 a month for standard service (~200 gigs limit)
- $45 a month for premium service (~500 gigs limit)
- $100 a month for unlimited
That's a similar structure to how electricity, water, and phone utilities are priced for consumers (albeit with differing dollar amounts). And yes I think that's entirely fair. The more you download, the more you should pay, because you are hogging more bandwidth than I am.
And the internet utility can take the extra dollars and use them to buy new servers and lay additional cable to support their high-demand customers, rather than block access to P2P or Itunes.com.
Re:Really? (Score:5, Interesting)
Or better yet how about time of day service like electricity. If I download in off peak hours my rates per gig would be lower than when downloading during peak hours. If you don't download at all you just pay the base amount for keeping service.
Re:Really? (Score:5, Informative)
http://teksavvy.com/en/resdsl.asp?ID=7&mID=1 [teksavvy.com]
Though I don't know if the graduated pricing is shared with the wholesaler.
Re:Really? (Score:5, Interesting)
They who do not learn from history are doomed to repeat it. We used to have tiered service. Consumers rejected it soundly as soon as services started selling unlimited service.
And it's not "fair" as you put it. We already pay for tiered service. Downloaders usually want faster speed, so they pay more money. We pay different amounts of money for different connection speeds. Adding bandwidth tiers on top of that will turn ISP billing into a horrible mess that is almost impossible for consumers to understand. When that happens, expect the ISPs to start finding ways to screw the consumer by tacking on extra fees for this and that until we end up with something as horrible as cell phone billing is now....
Besides, your plans have lots of problems:
Metered billing for ISPs is a terrible idea. Period. It causes more problems than it solves. ISPs are simply going to have to stop lying to their customers and actually be honest about how much bandwidth they are really providing for the money. As I said yesterday on this same topic, the only acceptable tier system is one that gives people lower priority for bulk downloads so that those transfer don't interfere with casual web surfers' usage, but does so on a continuously-updated basis and does not cut the bulk downloads any more than is absolutely necessary. Description here [slashdot.org].
Re: (Score:2)
False. Consumers did not reject "per gigabyte" tiers because no such animal has ever existed within the U.S. Some of the ISPs had time limits, but never gigabyte limits (you could download as much as you wanted).
Also, tiers based upon speed have proved themselves to be inoperative, because the professional liars.... er, salespeople exaggerate. They sell 10 megabit and then backwards-kludge it to 1 megabit through limits.
Therefore
Re: (Score:2)
Yes.
Oh well. (shrug) If downloading movies requires a $100 a month "unlimited gigabytes" connection, thus making DVDs a cheaper option for customers, so be it. That's the free market in action, where one type of product (downloading) competes with another type of product (dvd) for consumer dollar
Re: (Score:3, Informative)
-You can pay for a fast speed, but just 5 gigs per month (if all you do is email and surf the web a little, but want it fast).
-You can pay for a slow speed and say 1 gig per month if you are a grandmother type (just emailing the kids/grandkids, etc)
-You can pay for a slow speed and 100 gigs per month if you're a bulk.... "sharer" and just care about it getting down, now when it gets down
-You can pay for fast and 235892389432 gigs per
Re:Really? (Score:4, Informative)
TekSavvy charges $30/mth for 5mbit down 800kbit up DSL, with 200GB cap, $0.25 per GB over (averaged over two months), or $10 for 100GB. There is also an unmetered cogent-only service for $40/mth.
Pretty much everybody has caps/overage charges these days. Clearly the fact that ISPs are still throttling despite the incredibly low caps indicates that the throttling is about profit, not congestion.
Re: (Score:2)
When a core ISP buys fibre, whether or not the bandwidth is used on the fibre it still costs them the same (yes they can choose to make huge profits, but bear with me).
Electricity and water come from somewhere, if they aren't used it doesn't cost the suppliers the same.
Voice calls are typically priced by time and not by data transferred.
So why not:
1) When there is contention "premium priority" traffic always takes precedence over "normal pr
Re: (Score:3, Interesting)
Not for anyone else. Even then most of them don't use the proxies for their "business" plans.
And they don't implement them for "load balencing", they get that (well, as close as you can) for free with BGP. They implement them because it saves money.
This is not about transparent proxies, they only affect unencrypted HTTP traffic. It's about low level QoS (Which should be OK if well implemented) or something more along the lines of the recent Comcas
You are soooo wrong. (Score:5, Informative)
1. Bell is throttling P2P traffic between 4:30PM and 2AM. This affects BitTorrent and all other forms of P2P
2. All other traffic is full speed
3. All P2P is capped at about 30kbps between said hours
In fact this is exactly what they do to their own Sympatico users but now applied to all 3rd party resellers.
Re: (Score:2)
Re:Just before everyone gets excited.... (Score:5, Informative)
All blacklisted (or non-whitelisted, we're not sure yet) traffic is throttled to 60KB/s from 4PM to 5PM, and from 30KB per second from 5PM until 2AM.
There are two problems with your load-balancing allegation:
1) Load balancing would imply that provisioning of available bandwidth would be balanced, rather than limited to very specific thresholds
2) Users reported that speeds were perfectly fine before throttling; the network was able to handle all load without throttling or balancing. In order for load balancing to make sense as an explanation, there would have to have been congestion.
Further problems are that when blacklisted traffic is detected (P2P, for example), the users' entire connection is throttled (killing off VoIP service even with QoS). If the user is using a whitelisted service (HTTP), no throttling is performed. This IS protocol-specific.
Re:Just before everyone gets excited.... (Score:5, Interesting)
In late 2007 Bell/Sympatico started throttling p2p to 30KB/s between 5pm and 1am (when you're paying for a line capable of >400KB/s).
IMMEDIATELY all the technically savy customers (like me) **dumped** them and switched to TekSavvy and other competitors. It was only a matter of time before all of us managed to tell all of our friends and family, and bit by bit Bell's customer base was going to be EATEN ALIVE.
I DOUBT LIKE HELL there is actual congestion on Bell's common-infrastructure WAN links inside city limits, before they reach the point where it splits into the Bell-internal network and all the reseller's internal systems.
I GUARANTEE that Bell is just being cheap-asses with bandwidth to the net, and suddenly they discovered that their cheap-assness was NOT flying in the competitive market. So they've invented this reason to throttle everyone (since they control the common infrastructure - the "to the door" bits - that the CRTC *forces* them to re-sell at set rates to competitors).
Here:
Customer----(fat ass pipe)----PeeringPointForResellers------Sympatico-----(cheapass tiny pipe)-----Net
Customer----(fat ass pipe)----PeeringPointForResellers------Competitor-----(fat ass pipe)----------Net
BellSympaticoThink: "oh jeeze, we're getting raped by our competitors, maybe if we claim we're having congestion problems with the "fat ass pipe" that we're being forced to share with our competitors, then we'll have a level playing field? Yeah, fuck-em."
Now:
Customer----(fat ass pipe with packet shaping to make it suck as much as Sympatico)----PeeringPointForResellers------Competitor-----(fat ass pipe)----------Net
"there, now we won't loose any more customers".
FUCK SYMPATICO. I was being lazy about switching away from them, but now I'll do it just to save the $10 a month that the cheaper competition would save me.
PPS: I've been with BellSympatico 8 years, on their most expensive plan, and now I hate their guts and can't stand to pay them money. This is enough to make me want to drop my land line and go with VOIP, even if the latter is shitty quality and service.
Re: (Score:2)
The only good thing I can say, is at least bell admits they're doing this. I mean it'd be pretty hard to deny it, but some companies try anyway.
Re: (Score:3, Interesting)
Re: (Score:2)
Share the road (Score:3, Funny)
What is the result of the throttling? Is it lost connections, or is it just a slowdown of service? If it is just slowdown, I don't think these bandwidth hoggers have a claim. OTOH, if they are losing connection midstream, they too have a right to the road, even if they need to obey a slower speedlimit.
Re:Share the road (Score:5, Funny)
However in this case... (Score:5, Insightful)
However in this case, the road doesn't terminate at B, it goes on to C (and so forth). The wholesaler also controls the flow of traffic from B to C (even if the distance is arbitrary or non-existant). Thus the wholesaler in this case is forcing the retailers two roadways to merge in one single lane during peak times.
This isn't about the end users clogging up the highways. This is about the unscrupulous merge sign put up during 'peak' times. The idea is the retailer leased two roadways, and they damn well want to use them. If there are too many cars creating a traffic jam, its up to the retailer to decide who gets to use the carpool lane etc.
Re:However in this case... (Score:4, Funny)
Let me try to break it down to something simpler.
Imagine there were an infinite number of Supermen. Where would they fit? How super could he be if there are an infinite number of him taking up all the space in the universe?
There wouldn't be any space left for Lois Lane or even the planet Krypton. You sometimes need to remove a few "super" users to make room for the normal people.
Re:However in this case... (Score:5, Funny)
Re: (Score:3, Insightful)
Re: (Score:2)
Re: (Score:3, Interesting)
What seems to have happened from my point of view, is that the wholesaler used to put the resellers before its own retail clients before, and now put everyone at the same level. I expect the wholesaler to be called be
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Some wholesalers actually do own A to B. The problem is that in order to do that, you need to colocate your own DSLAMs in the COs, which limits your coverage and reach. It does have the advantage of letting you pick your own profiles/technology (ADSL, ADSL2+, VDSL, etc) since the wholesaler has access to the raw copper wire, and have zero interference since you're providing your own backhaul connection from the CO.
Re: (Score:3, Informative)
If you
Re: (Score:2)
They are usually VERY clear that you are paying for up to a certain number of tubes, and they will arbitrarily take away your maximum number of tubes if they decide you use them too much.
I'm not saying it's right, just that it is a little dis-ingenuous to pretend you didn't sign something that says I'll bend over and beg you for more.
If you really want your tube (and it is only one ma
Re:Share the road (Score:4, Interesting)
Throttling all http connections while I'm using a bittorrent client is the problem. I have no empirical evidence at hand to show that even the bittorrent traffic is throttled. As soon as I make a bittorrent connection, all other protocols are throttled to zero throughput. When I close the bittorrent client all returns to normal. It's that simple. If my http download rate can hit the 3.5Mbps as advertised but bittorrent cannot, and while using bittorrent total bandwidth allowed seems to drop to some 56kbps... well, that is not protecting anyone, it is forcibly throttling my traffic. I can download ISOs using http connections ALL FUCKING DAY LONG... start one P2P connection and I get roughly 56kbps total. What is happening is NOT about managing bandwidth usage, it's about mangling P2P usage.
I would be just fine and happy if all I could get was 3.5Mbps all day long with any protocol. I'd happily share that among my vonage, internet radio, several computers etc. When I open the bittorrent client, all bandwidth is dropped to near nothing and http traffic and smtp traffic (as far as I can tell) are cut off.
So, what you think is merely bandwidth management is actually p2p mangling, pure and simple. This was not always the case, it is something new that TimeWarner has started recently. No, I do not download movies and music illegally, so it is me, the honest user who is inconvenienced by all these anti-file sharing methods. I am penalized by the dimwitted people who think they know how to stop the **AA from dying. It takes a great deal of effort not to take out large WSJ ads telling the **AA to fuck off and die right along with timewarner et al.
Sure, you can say that I signed the contract etc. but god damnit people, I signed up for 3.5Mbps without regard to protocol used. Thanks to my good fortune, in the nice area where I live it's Time Warner or satellite. I don't have a choice of three or four ISP's.
So what is a cable company supposed to do? So many customers, so big is the Internet. How are they to balance the traffic and needs? Well, I can tell you this, it's not nearly as difficult as they would like congress and the fcc to believe. If you promise 3.5Mbps, deliver it or discount the price! period!
If you bought a 1st class ticket to the Orient, and half way through the stewardess tells you that you have the share your seat with someone else and there will be no discount or rebate... well, you have every right to be pissed off. I'm paying for 3.5Mbps worth of room in the tube and I EXPECT to get that much. I don't want half a lane for my car, or a bike path, I want the full passenger vehicle lane width. If my family is in the damn car I don't want to be forced to use the back roads. It really is THAT simple.
If they want to throttle traffic and shape it, then fucking discount the price of the service. period. If you take your car to be worked on and pay for guaranteed workmanship, you don't want to find out later that the work was faulty, that oh, that doesn't apply to YOUR type of vehicle, whether it was in the fine print of the last page of the contract or not.
Re: (Score:3, Interesting)
Re: (Score:2)
Re: (Score:2)
In short, users are already paying per-gig for what they use. Calling them a "bandwidth hog" despite the fact that they're paying Bell 50x cost for that bandwidth is incorrect.
The same is true when it comes to wholesalers; they pay Bell per-megabit for back
Bernoulli and the boiling point of data... (Score:2)
Throttle Bell Canada! (Score:4, Interesting)
Re: (Score:3, Informative)
Re: (Score:2)
drop the cap level that you are allowed to download and start charging for anything over the cap.
I think ISP's in Australia are a bit harsh in cropping speeds to 64kbps once the monthly limit is reached, as this is annoyingly slow. Instead they should cap to around 128kbps which allows for fairly useful day-to-day browsing and emails and VOIP calls whilst making P2P too annoyingly slow to contemplate. But in fairness, most ISP's here don't charge for excess traffic once it's shaped. You basically get what you pay for here, by and large, and you don't have to pay for what you don't need.
Re: (Score:2)
Re: (Score:2)
Right now, I am mulling at going with them but according to the tech I would only get
between 1 and 2M while now I am at 5.5M. However over the weekend random tests would show I was getting about 1.5M but this morning it peaked to 4.5M. However I gather you would be using Bell infrastructure which is why I may wait to see what the fallout of this article is befor
Re: (Score:2, Informative)
Re: (Score:2)
Re: (Score:2)
I may end up just sucking i
Re: (Score:2)
Already moved (Score:3, Interesting)
Min
Re: (Score:2)
Re: (Score:2)
It's not necessarily that easy (Score:5, Interesting)
E.g., there was at some point an article about what Comcast does. They're not targetting the P2P ports or anything. They just look at which client opens a burst of connections at the same time and has a lot of connections going at the same time.
You'd get throttled just the same if you connected a large extended family or lan party via the same proxy/router to the 'net, and everyone tried to download 5 porn movies at the same time, and repeatedly reload Slashdot while they download. You know, all via the browser, plain old HTTP, on port 80.
Basically it's not as much targeting P2P, as just targeting everyone who doesn't behave like one user with a browser.
Because they're not as much hating P2P, as trying to keep the majority of moms and pops sending emails to their kids happy. Those guys don't open 20 connections at the same time, so they don't notice it.
The problem is, basically: The ISPs oversold the bandwidth _massively_, and I'm certainly not trying to defend that, but it would sorta work if everyone didn't use all that. Or if they all had the same number of connections, so they're all inconvenienced equally. P2P programs don't act like that. They keep opening bursts of connections until they saturate the pipe, everyone else be damned.
Think of the following example, basically. Let's say I'm lucky enough to have an 100 mbit/s Ethernet connection to my best buddy's ISP, and decide to share it with the whole neighbourhood. Essentially, I'd be a mini-ISP there. Now I don't want one guy saturating it all, so let's say I connect everyone to my hub via only 10 mbit/s Ethernet. I'd have enough bandwidth for 10 of them. But I figure most of them are old people and don't surf much, so I let 40 people connect there.
It's already oversold, but let's hope it works out.
Now if everyone used a browser and, say, 1 connection at a time, worst that can happen is that all 40 download a movie at the same time, and they all see 100/40 = 2.5 mbit/s bandwidth. That's only at peak times, so probably most will understand it, and some probably won't even do the maths there in the first place.
But then come some people with P2P clients. Those don't play that nice. If they don't get the whole 10mbit/s, everyone else be damned, they'll open more connections until they do. So now as little as a quarter of my users can saturate my whole backbone connection. The other 75% will suck air through a straw. Their 1 connection vs the two dozen connections of the P2P guys means they'll be happy if they see 100 kbit/s on their downloads. They can probably go brew a cup of coffee even while a simple site like Slashdot loads.
Now they _will_ complain.
That's the ISP's problem in a nutshell: P2P makes the traditional oversell no longer work. A minority of users running P2P stuff full time, can stuff everyone else's pipe, and massively amplify the effects of oversell for everyone else.
Not because it's P2P, but because it opens that burst of connections.
What can you do there?
1. Stop overselling. That costs money, so I don't think the ISPs will do that any time soon. Especially since they dug themselves into a nasty hole where they advertised more and more bandwidth and lower and lower prices, and they can't afford to actually deliver that to everyone. The only way to do that is to raise prices.
2. Start charging per MB, and let free market economics solve who gets how much bandwidth. The moms and pops just reading their emails would probably pay cents, while if someone wants to download the whole internet, well, if they can afford it, why not? Downside, it would be extremely unpopular, and again it's a hole that their own marketing dug them in.
3. Target anyone who opens ridiculous numbers of connections, to stop them from squeezing everyone else out. Downside, it's easy to overdo it, and now P2P users will suck air through a straw and see analog modem speeds.
4. Implement some kind of smart scheduling, so
Re: (Score:3, Interesting)
Actually, this is the only thing that they should be doing as "overselling" can, and should, be treated as what it is: a rampant case of criminal business fraud. I am quite dismayed tha
Re: (Score:2)
If I have 100 customers who each have 5mbit connections, with average usage of 50mbit/s and peak usage of 75mbit/s, why should I (as an ISP) pay for 500mbit/s?
Overselling only becomes bad when you don't have enough bandwidth to handle peak loads. The internet and ISPs cannot function without overselling, and that includes TekSavvy.
Re: (Score:2)
I think you've missed the mark on why bittorrent at least is so revolutionary. Yes it can eat a lot of bandwidth, but for a large cable operator a large number of people are going to be on your own backbone not using any of your upstream bandwidth or at least using a lot less of it.
So from your perspective you have your 100meg connection with 100 million 10meg connections coming off of it, if they are copying from one to another then your 100meg feed is irrelevant and they will not be degrading the perfor
Re: (Score:2)
Doesn't work that way. For cable Internet the bottleneck is the upstream link from the subscriber's cable modem to the cable head-end. That upstream link's got only a fraction of the bandwidth the downstream link does, and's easy to saturate. And that's exactly the link that'd be hit when a subscriber downloads a file from another subscriber, because the download for the recipient is an upload for the machine hosting the file. And that upstream isn't per-customer, it's shared among all subscribers on a give
Re: (Score:2)
I'm sorry, but your family sounds scary.
Re: (Score:3, Interesting)
What's so dishonest about #4? As a DSL customer (not an ISP) that approach seems perfectly reasonable to me, so long as the ISP is upfront about the average bandwidth th
Re: (Score:2)
Unfortunately, as you said, it would probably be rather unpopular at first, even though it's likely to be less expensive for most users than unmetered bandwidth.
I don't know what ISPs are like in your experience, but 'round here I can't imagine any of them switching to a pricing structure which sees the majority of their customers giving them less money every month.
If and when pay-per-MB broadband comes, expect the most basic package to cost at least as much as the current standard package costs right now.
Re: (Score:2)
Connections and bandwith are not necessarily interconnected like you assume. Any moderately smart network appliance (e.g. Tomato for home routers) can measure bandwidth per source irrespective of the number of connections. So saying that the "big bad hacker" who opens 100 connections clogs the pipes for everyone is just spin doctoring the issue.
The other problem with your argument is that it is not only P2P programs that open flurries of connect
Re:It's not necessarily that easy (Score:5, Insightful)
1) Teksavvy supplies it's own bandwidth, and only leases the 'last-mile' connection from Bell Canada.
2) Teksavvy does oversell, but currently keeps up with it's traffic even at peak times.
3) Bell is throttling P2P on Teksavvy's last-mile, even though it has little impact on their ability to provide service to it's own customers.
4) The type of throttling they are doing is interfearing with QoS systems in routers that ensure VoIP works. It is causing reduced quality in VoIP services.
5) Selectively throttling specific protocols is a slippery slope. What's to say that they don't decide that VoIP is the next service that gets eliminated because it competes with their local phone service?
This is a blatant attempt by Bell to remove a competitive advantage from competing ISPs.
Re: (Score:2)
At any rate, to finally get back on topic, just randomizing ports and encrypting connections won't do much. As long as you still open two dozen connections, you can still be throttled just as well. The only way to be really stealthy there is if you make it all go to a centralized server, tunneled over a single connecti
Re: (Score:2)
I'd rather see something like the way OpenVPN can be setup to tunnel an encrypted connection over UDP packets as the transport mechanism. Hide all the TCP level details completely. I'd probably go even further and use a protocol like SCTP encrypted and tunneled over UDP.
At least this would stop the Comcast forged RST problem, but there's not much you could do if they just dropped these packets instead.
Re: (Score:2)
But what about the CBC? (Score:5, Interesting)
We hope you enjoyed tonight's show! As announced, CBC is happy to present Canada's Next Great Prime Minister to you as a DRM-free bittorrent file [www.cbc.ca] which you can download, share & enjoy. First, pick which file you want to download:
Xvid AVI at 720x486
or
264 MPEG-4 at 320x240
Maybe marketplace should do a story about Bell and Rogers regarding this throttling...
Re: (Score:2)
The answer is always the same (Score:5, Insightful)
Contact your ISP (Score:3, Insightful)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Then they just throttle unrecognized packets... (Score:2)
Re: (Score:2)
Re: (Score:2)
They already have 200Gb of online storage and are setting up "online desktops" which are RDP connections to a fedora VM with a 16Mb connection as free services -so I wouldn't put it past them setting up free VPN connections for everyone.
Can't Escape Bell (Score:5, Interesting)
I was actually considering dropping my Bell telephone number to move completely to voip at Teksavvy after I found Bell adding things to my phone bill that I never asked for. Now to go to voip would require me to get dry DSL service from Teksavvy and probably end up paying more per month than I could for a basic phone bill but I'm seriously considering it just to avoid having to talk to Bell any more.
I know that the back end is still run by Bell and that the money I pay for dry DSL would probably mostly get passed on to that company anyway but at least I could trust that nobody could decide to add a long distance plan to my account without consulting me first.
My big concern with moving to voip-only is that Bell will abuse their position to degrade VoIP calls.
Re: (Score:3, Interesting)
I was actually considering dropping my Bell telephone number to move completely to voip at Teksavvy after I found Bell adding things to my phone bill that I never asked for. Now to go to voip would require me to get dry DSL service from Teksavvy and probably end up paying more per month than I could for a basic phone bill but I'm seriously considering it just to avoid having to talk to Bell any more.
I'm also a very happy teksavvy customer, who moved to dry dsl + voip after bell pissed me off one too many times (By unilaterally, without notice adding an extra year of contract to my cell phone plan. Don't get me started...).
Since the service and support from teksavvy is so great (not that I often need support), I immediately asked them about their voip plans, and the teksavvy rep actually recommended against using their own voip service, saying it wasn't yet reliable enough (this was about 2 years ago,
Re: (Score:2)
The voip service I use right now is from Les.net (another very helpful small Canadian company) and I think I would end up moving to just using that full-time. I already have one local number from
How to Escape Bell in 4 steps (Score:5, Informative)
I got to keep my phone number, but it cost me some $$: to be sure that the number is not reassigned before it is transfered, I followed these steps:
1- sign up with Babytel
2- send a "number portability" form, signed, by fax to Babytel
3- wait 30 days for the move to be done
4- profit! Bell cuts off my phone line automatically when the number is gone.
Total cost: 1 month's fees due to the overlap (25$ Bell line + 12$ for the Babytel line).
Total hassle: fill and fax 1 form, email twice to Babytel to know the procedure and confirm.
Total time spent with Bell: no phone, no mail, just the final bill for the amount of 0$.
Re: (Score:2)
Total time spent with Bell: no phone, no mail, just the final bill for the amount of 0$.
I like the sound of that. The rates at Babytel look higher than what I get from Les.net but Babytel looks like a full-service outfit instead of just the basic access that I want. I wonder if Les.net does the same number porting thing. I'm going to look into that - especially if it means I don't have to call Bell myself.
Of course you have to know that since your DSL is supplied over Bell's lines you're really still at their mercy in the end.
One day maybe we can hope that someone will see the sense in
Re: (Score:2)
Re: (Score:2)
That was a few years ago. The last time I called
Re: (Score:2)
Bell and Teksavvy (Score:2)
In my case, after the initial (dry-loop) connection is made, *I* have to pay for any future Bell calls. Further to that, I have a straight run t
Re: (Score:3, Interesting)
I get that you're probably joking but QoS can make a huge difference from what I understand. And there are cases where providers have decided not to honour the QoS flags on voip protocols. Coincidentally these providers also have a voip offering of their own where they don't have a problem meeting QoS needs.
It's not throttling... (Score:4, Funny)
Which is how they learned to spell Canada, by the way. C, eh! N, eh! D, eh!
/Dives behind desk before the RCMP polites me to death, because I've been waiting for a proper Canadian thread to use that joke and couldn't hold back anymore. With credit - I think - to Bob and Doug.
Re: (Score:2)
Ah, that's a good one me 'bye. I haven't heard 'dat one since before Reagan was in 'de White 'Ouse.
:-P
Really my old trout, you need some newer jokes.
Watch out me son, the RCMP have been known to taser people to death [www.cbc.ca] as well; we could arrange for a demonstration if you like.
Re: (Score:2)
Re: (Score:2)
The number of people in Canada who use "eh" in their sentences is probably about the same number of people in the US who are in the habit of saying "y'all". I've lived half my life on each side of the border, and I probably couldn't use up my fingers counting the numbers I've personally known belonging to either category.
In much the same way that most folks in the US feel no ongoing need to distinguish themselves from their Southern, Ap
Re: (Score:2)
BTW, the plural of "y'all" is "all y'all". Trust me, Southerners REALLY understand the difference.
The problem is overselling (Score:4, Insightful)
Good day & welcome to the great white north re (Score:2)
The Censorship Tag (Score:4, Insightful)
Re: (Score:3, Insightful)
Alternatively, the ISP may buy bandwidth from their upstream wholesaler, and manage their own DSLAM's, authentication, etc.
As you say, too many unanswered questions to form an informed opinion. That doesn't
Re: (Score:2)
I always though that ISP's bought bandwidth based on the capacity of the interconnect such as a 100Mbs 100BaseT in the datacenter or an OC48 or whatever and by the total traffic transfered per time period. If the ISP went over in the total transfer, they were charged a permium rate for the excess. If an ISP can't get these classical terms from a tier 1 provider, it looks like we are all screwed.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
REAL quick and dirty explanation:
Bell installs the DSLAMs. The DSLAMs connect to the Bell network. Various ISPs connect their backhauls to the Bell network, and their DSL customer's PPPoE sessions hit the Bell DSLAM, then are popped over to the appropriate ISP's backhaul, and thence to their network.
What Bell is doing, more or less, is throttling at the DSLAM, rather than throttling at their own edge.
Re: (Score:3, Insightful)
Re:Bell Canada Monopoly/CRTC - Avenues of Recourse (Score:2, Insightful)