- Joined
- Sep 26, 2002
- Location
- Indianapolis, IN
hub
a hub is a repeater, which is a osi model device, the simplest possible. a hub takes the data that comes into a port and sends it out all the other ports in the hub. it doesn't perform any filtering or redirection of data. although it's actually a little more complicated, you can think of a hub like a piece of wire. a better analogy might be that of an internet chat room. everything that everyone who joins a particular chat is seen by everyone else. if there are too many people trying to chat, things get bogged down. more info on hubs can be found here.
bridge
bridges (sometimes called "transparent bridges") work at osi model layer 2. this means they don't know anything about protocols, but just forward data depending on the destination address in the data packet. this address is not the ip address, but the mac (media access control) address that is unique to each network adapter card.
with a bridge, all your computers are in the same network subnet, so you don't have to worry about not being able to communicate between computers or share an internet connection. dhcp servers will work fine across bridges, or if you assign your own ip addresses, you'll use the same first 3 "octets" of the ip address (example: 192.168.0.x).
however, the only data that is allowed to cross the bridge is data that is being sent to a valid address on the other side of the bridge. no valid address, no data across the bridge. bridges don't require programming. they learn the addresses of the computers connected to them by listening to the data flowing through them.
bridges are very useful for joining networks made of different media types together into larger networks, and keeping network segments free of data that doesn't belong in a particular segment.
switches
switches are the same thing as bridges, but usually have multiple ports with the same "flavor" connection (example: 10/100baset).
switches can be used in heavily loaded networks to isolate data flow and improve performance. in a switch, data between two lightly used computers will be isolated from data intended for a heavily used server, for example. or in the opposite case, in "auto sensing" switches that allow mixing of 10 and 100mbps connections, the slower 10mbps transfer won't slow down the faster 100mbps flow.
although switch prices are dropping so that there is very little difference from hub prices, most home users get very little, if any, advantage from switches, even when sharing "broadband" internet connections. "broadband" connections for most users are in the 1-2mbps range, far below even 10mbps speeds. since you share that bandwidth, you can see that your speedy 100baset connection isn't even breaking a sweat when you're using the internet.
router
routers forward data packets from one place to another, too! however routers are osi model layer 3 devices, and forward data depending on the network address, not the hardware (mac) address. for tcp/ip networks, this means the ip address of the network interface.
routers isolate each lan into a separate subnet, so each network adapter's ip address will have a different third "octet" (example: 192.168.1.1 and 192.168.2.1 are in different subnets.). they are necessary in large networks because the tcp/ip addressing scheme allows only 254 addresses per (class c) network segment.
routers, like bridges, provide bandwidth control by keeping data out of subnets where it doesn't belong. however, routers need to be set up before they can get going, although once set up, they can communicate with other routers and learn the way to parts of a network that are added after a router is initially configured.
routers are also the only one of these four devices that will allow you to share a single ip address among multiple network clients.
----------------------------
thanks to thomas maufer for additional information
a hub is a repeater, which is a osi model device, the simplest possible. a hub takes the data that comes into a port and sends it out all the other ports in the hub. it doesn't perform any filtering or redirection of data. although it's actually a little more complicated, you can think of a hub like a piece of wire. a better analogy might be that of an internet chat room. everything that everyone who joins a particular chat is seen by everyone else. if there are too many people trying to chat, things get bogged down. more info on hubs can be found here.
bridge
bridges (sometimes called "transparent bridges") work at osi model layer 2. this means they don't know anything about protocols, but just forward data depending on the destination address in the data packet. this address is not the ip address, but the mac (media access control) address that is unique to each network adapter card.
with a bridge, all your computers are in the same network subnet, so you don't have to worry about not being able to communicate between computers or share an internet connection. dhcp servers will work fine across bridges, or if you assign your own ip addresses, you'll use the same first 3 "octets" of the ip address (example: 192.168.0.x).
however, the only data that is allowed to cross the bridge is data that is being sent to a valid address on the other side of the bridge. no valid address, no data across the bridge. bridges don't require programming. they learn the addresses of the computers connected to them by listening to the data flowing through them.
bridges are very useful for joining networks made of different media types together into larger networks, and keeping network segments free of data that doesn't belong in a particular segment.
switches
switches are the same thing as bridges, but usually have multiple ports with the same "flavor" connection (example: 10/100baset).
switches can be used in heavily loaded networks to isolate data flow and improve performance. in a switch, data between two lightly used computers will be isolated from data intended for a heavily used server, for example. or in the opposite case, in "auto sensing" switches that allow mixing of 10 and 100mbps connections, the slower 10mbps transfer won't slow down the faster 100mbps flow.
although switch prices are dropping so that there is very little difference from hub prices, most home users get very little, if any, advantage from switches, even when sharing "broadband" internet connections. "broadband" connections for most users are in the 1-2mbps range, far below even 10mbps speeds. since you share that bandwidth, you can see that your speedy 100baset connection isn't even breaking a sweat when you're using the internet.
router
routers forward data packets from one place to another, too! however routers are osi model layer 3 devices, and forward data depending on the network address, not the hardware (mac) address. for tcp/ip networks, this means the ip address of the network interface.
routers isolate each lan into a separate subnet, so each network adapter's ip address will have a different third "octet" (example: 192.168.1.1 and 192.168.2.1 are in different subnets.). they are necessary in large networks because the tcp/ip addressing scheme allows only 254 addresses per (class c) network segment.
routers, like bridges, provide bandwidth control by keeping data out of subnets where it doesn't belong. however, routers need to be set up before they can get going, although once set up, they can communicate with other routers and learn the way to parts of a network that are added after a router is initially configured.
routers are also the only one of these four devices that will allow you to share a single ip address among multiple network clients.
----------------------------
thanks to thomas maufer for additional information
since i don't have much studying to do for finals, i figured that i would get my research hat on and dig up some info about the differences... i know that i wish i just had this info laying around because i really didn't know a whole lot. 
