|
|
|
|
|
Posted by FreedomFireCom on August 30, 2006, 6:41 pm
If you were Registered and logged in, you could reply and use other advanced thread options
I wrote the subject article awhile back and am sharing it here for any
members working with Telecom/IT issues for their organizations.
Here's a snippet:
"By design, we have a basic way of dealing with bandwidth hogs both on
the local area network and in the wide area network. This goes all the
way back to the earliest days of IP, back before the Internet was a
common resource. The performance issues are still the same, and in most
cases bandwidth is not the culprit thanks to that original work."
http://ezinearticles.com/?Ethernet,-IP,-And-Caching....A-Bit-Of-History,-Background,-And-Insights&id=282410
God Bless,
Michael Lemm
FreedomFire Communications
http://DS3-Bandwidth.com
http://www.linkedin.com/in/freedomfirecom
|
 
| |
Posted by Albert Manfredi on August 31, 2006, 11:58 am
If you were Registered and logged in, you could reply and use other advanced thread options
> Here's a snippet:
>
> "By design, we have a basic way of dealing with bandwidth hogs both on
> the local area network and in the wide area network. This goes all the
> way back to the earliest days of IP, back before the Internet was a
> common resource. The performance issues are still the same, and in
> most
> cases bandwidth is not the culprit thanks to that original work."
>
>
http://ezinearticles.com/?Ethernet,-IP,-And-Caching....A-Bit-Of-History,-Background,-And-Insights&id=282410
Not sure about the emphasis placed on priority queueing. Early Ethernet
and IP used best effort queueing almost exclusively -- same priority for
every frame or packet. Ethernet "priority" wasn't even available until
quite a bit later, more like the 1990s, with IEEE 802.1p, eventually
folded into 802.1Q.
If there was any mechanism to prevent hogging of bandwidth, my thinking
is that it was simply the fact that no single machine was typically fast
enough to grab the entire L2 link. As machines became faster, so did the
L2 network. I really don't know what intrinsic mechanism existed at L2,
especially, to prevent bandwidth hogging.
Matter of fact, before the time of L2 "switches," it was possible to hog
the bandwidth, by violating the backoff requirements of the CSMA/CD
protocol ("Ethernet capture," it was called). And there was another
shared Ethernet protocol proposed, the name escapes me, to solve this
Ethernet capture vulnerability. But of course, switched Ethernet
appeared on the scene and all these worries were obsoleted.
All I'm saying is that I think we all "muddled through" a lot of this. I
don't think it had all been figured out ahead of time with uncanny
forethought.
Bert
|
|
Posted by Robert Redelmeier on August 31, 2006, 2:57 pm
If you were Registered and logged in, you could reply and use other advanced thread options
>> "By design, we have a basic way of dealing with bandwidth hogs both on
>> the local area network and in the wide area network. This goes all the
>
> Not sure about the emphasis placed on priority queueing.
There wasn't. IMHO, the OP was trolling for hit to his article
advertising caching proxies (instead just look up `squid`).
Unfortunately, this does nothing for bandwidth hogs (but does
help tame stampeding herds of students, etc).
Solving bandwidth hogs (individual abusers) is a more difficult
problem, perhaps addressible by delaying ACK packets and
allowing the senders TCP throttling to do the work. Of course
this won't work for UDP, but most firewalls drop inbound UDP,
and probably should outbound.
-- Robert
|
| Similar Threads | Posted | | USB Ethernet controllers that use the ASIX AX88772 or AX88172 USB-Ethernet bridge devices | August 19, 2005, 4:04 pm |
| Difference between Ethernet 2 and 802.3 Frame per the Ethernet FAQ | July 28, 2006, 9:02 am |
| ethernet hub | April 27, 2006, 2:44 am |
| WAN Ethernet | May 2, 2006, 4:20 pm |
| Ethernet TAP | July 30, 2007, 12:28 am |
| Do I have an Ethernet card? | February 20, 2005, 10:48 am |
| Ethernet Repeaters | March 9, 2005, 8:10 am |
| Need Ethernet Hub - NOT Switch | March 15, 2005, 7:15 pm |
| Ethernet to OC-3 Extender | April 11, 2005, 9:35 am |
| Ethernet over single UTP | April 19, 2005, 1:32 pm |
|
|
Home Cabling Guide
Finally, an instantly downloadable book that saves you thousands in home improvement dollars!
Enjoy living in 21st century technology-advanced home while increasing its selling value and competitive advantage
on the real estate market. Whether your cabling is for home office or high-tech
leisure, you can wire your home yourself or learn "wirish" to speak with your cabling contractors in their language!
Learn More
|
NewsGroups 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map