approval from:
fAcEtIOUs 
| 10GE NOT ENOUGH “So, invest in more Internet gateway capacity, 10Gbps interconnect ports, and peering agreements."
First off .. 10GE is not nearly enough. It just goes to show how litte these "Torrent Freaks" understand large scale networking. And calling them interconnect ports is hilarious and just shows the lack of technical understanding. Second, have they seen what it cost per MB to fire up OC-48 and 10GE connections to "Internet gateways"? Who's going to eat that cost? I'll tell you ..the customer. Why should ISPs have to raise rates and invest hundreds of millions (yes, hundreds of millions) when simply throttling the traffic, especially during peak times, is a quick easy fix? Then they can build out their networks at a more steady pace. I wish all these BT freaks could really see what % of the Internet's traffic is BT. It would blow thier mind. |
|
| Actually bitorrent is 35% of internet traffic.
»en.wikipedia.org/wiki/BitTorrent···k_impact
Care to try again?
The question you should have asked is "I wish all these heavy bitorrent users could see what % of ISP customers use bitorrent."
You criticize the understanding of others, but fail to address the real issue of bitorrent, which isn't bandwidth, but the ridiculous number of connections that need to be maid to achieve such bandwidth. Cisco equipement ain't cheap. |
|
 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2
 ·Clear Wireless
| said by grandpinaple:You criticize the understanding of others, but fail to address the real issue of bitorrent, which isn't bandwidth, but the ridiculous number of connections that need to be maid to achieve such bandwidth. Cisco equipement ain't cheap. The number of connections is irrelevant on routers. Packets are packets: they read the destination IP and forward it out the appropriate interface. Whether the router is passing 6million packets per second across 10 TCP sessions or 10,000,000 TCP sessions the workload is the same. |
|
1 edit | Routing takes a lot more processing power than simply passing packets. Also most routers have a limited amount of connections that they can handle, that alone should show that routing is the issue here.
The old WRT linksys routers used to lock up from having too many connections made even if the download was only a few Mbps as opposed to direct connect which could download at 2-4 times the speed with no lock up.
If bandwidth were the issue then ISPs would be throttling NNTP. They would also simply throttle the speeds at which someone can torrent instead of outright blocking it. |
|
|
|
espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2 Reviews:
·Clear Wireless
1 edit | You're trying to compare SOHO router/NAT widgets to backbone routers used by ISPs, and these devices are only common in that they both move packets. The reason you have connection limits on widgets like the home Linksys / Netgear / Dlink routers is that they have to do stateful connection tracking to be able to re-write all of the packets to match source IPs on your local LAN. Those devices are also built to meet $100 or lower price points, so memory and processing limitations are on the low-end of the engineering scale. In any case once that device has performed the translation from RFC1918 addressing into public IPv4 addressing no other router in path needs to perform a similar translation operation.
Real backbone routers like those used by ISPs are only doing FIB lookups to a prefix:interface mapping. This is a hardware operating using ASICs that read from very fast TCAM tables that allow them to forward packets at full interface line rate. On the Internet backbone processing stops at layer3, with the slight exception of some layer4 data being used to gain more variability in traffic hashing when multiple links are available for a given destination prefix. |
|
patcat88
join:2002-04-05
Jamaica, NY
kudos:1 | reply to grandpinaple
Internet routers are stateless, each packet stands on its own, and only its own, it has no relationship to any other packet. Creating a concept of a connection is for higher level protocols that internet routers don't see. A home "Router", really a firewall, is a statefull device, since it must change IP addresses and do 1 to many conversion because of NAT.
You really fell off the boat to make that mistake. |
|
yabos
join:2003-02-16
London, ON | reply to grandpinaple
There's a huge difference between a real router and your home NAT router. NAT has to maintain a table entry for each outbound connection and this causes it to run out of memory. A real router does nothing of the sort unless it's using NAT but in most cases it isn't. |
|
| reply to ISP_Owner
There are so many problems in your post, the readers can be sure that you don't own an ISP... My favorite, "cost per MB". |
|
