<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.2.4">
</HEAD>
<BODY>
Robert,<BR>
The 10/100Mbit hubs are actually a marketing simplification in naming ;) What they actually are, are a 10Mbit segment, and a 100Mbit segment, with a switch in between them. When you plug in a device, the device determines which segment to connect you to. When a 10Mbit device talks to a 100Mbit device, it passes through the switch. I've also seen some of these "hubs" that are actually full fledged switches. <BR>
<BR>
Of course, this could be different, depending on the exact device you have, but regardless of the device, there is no IEEE 802.3 spec that allows Ethernet devices of different speeds to coexist on the same physical segment. You can logically connect them via a switch or bridge.<BR>
<BR>
--Matt<BR>
<BR>
<BR>
On Tue, 2005-01-18 at 19:18 -0600, Robert Denier wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Everyone probably knows this, but just in case they don't..</FONT>
<FONT COLOR="#000000">Anytime you see a wireless speed you can probably cut it in half for the </FONT>
<FONT COLOR="#000000">actual speed you get. Furthermore the more wireless clients you have on </FONT>
<FONT COLOR="#000000">a channel, even if they are not transmitting, the slower the network </FONT>
<FONT COLOR="#000000">operates, although its not a huge difference. At leasts thats my </FONT>
<FONT COLOR="#000000">experience with 802.11b networks and the orinoco driver series.</FONT>
<FONT COLOR="#000000">One small point. I've connected 10Mb devices to a cheap 10/100 hub and </FONT>
<FONT COLOR="#000000">everything works fine. I don't know what its actually doing internally </FONT>
<FONT COLOR="#000000">of course. Of course if your still using hubs and having bandwidth </FONT>
<FONT COLOR="#000000">issues, well switches were quite cheap last I looked.</FONT>
<FONT COLOR="#000000">As a final comment. If your doing anything beyond web browsing. (I.E. </FONT>
<FONT COLOR="#000000">mythtv or playing multimedia files over a network, then avoid 802.11b as </FONT>
<FONT COLOR="#000000">much as feasible. It simply isn't fast enough to keep everything </FONT>
<FONT COLOR="#000000">responsive. That doesn't mean you can't use it for those purposes where </FONT>
<FONT COLOR="#000000">you truly need it, but well sometimes the time you save not running a </FONT>
<FONT COLOR="#000000">cable, you lose later. 802.11g might solve those issues, but I've never </FONT>
<FONT COLOR="#000000">seriously tried to get it working under linux.) (Netgear MA311 pci </FONT>
<FONT COLOR="#000000">cards with the orinico and/or hostap driver series are my </FONT>
<FONT COLOR="#000000">recommendations for linux for 802.11b.)</FONT>
<FONT COLOR="#000000">Matt Mossholder wrote:</FONT>
<FONT COLOR="#000000">> Brad,</FONT>
<FONT COLOR="#000000">> Just to clear something up... a 10Mbit client connected to a </FONT>
<FONT COLOR="#000000">> 100Mbit network does NOT "10x the bandwidth it is using, because it is </FONT>
<FONT COLOR="#000000">> time that matters." The only way to connect a 10Mbit client to a </FONT>
<FONT COLOR="#000000">> 100Mbit network is via a switch or bridge, which does rate conversion </FONT>
<FONT COLOR="#000000">> on each frame. Hench, a 10Mbit client's traffic will be converted to </FONT>
<FONT COLOR="#000000">> 100Mbit when the frame is sent out by the switch. The time in between </FONT>
<FONT COLOR="#000000">> the frames to/from the 10Mbit client is free for use by other systems.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Now, if we are talking about something like 802.11, that's a </FONT>
<FONT COLOR="#000000">> different story.... 802.11b clients definitely have a negative impact </FONT>
<FONT COLOR="#000000">> on the 802.11g traffic, when the b and g clients are both on the same </FONT>
<FONT COLOR="#000000">> channel. This is because everything is a broadcast, and in this </FONT>
<FONT COLOR="#000000">> instance, it really is the time that matters. The 802.11g clients </FONT>
<FONT COLOR="#000000">> can't talk or be talked to while the 802.11b systems are...speaking... </FONT>
<FONT COLOR="#000000">> so...slowly....</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> I agree with everything else though :)</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> --Matt</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">mythtv-users mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</A></FONT>
<FONT COLOR="#000000"><A HREF="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Matt Mossholder <<A HREF="mailto:matt@mossholder.com">matt@mossholder.com</A>>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>