A simple demonstration of the difference between an Ethernet hub and an Ethernet switch, and how this can get you into (temporary) trouble if you're not aware of how a switch works.
Absolutely stellar video. I very rarely see such clear and concise tutorial videos for networking features. And the fact that it used a PLC and an HMI, as opposed to just a router and a PC like most videos on this make it excellent.
Bravo! I was asked this exact question last week by my boss at work and I didn't know. Funny how it's little understandings like this that stump even the best of us.
10 years later and this helped me with my cyber security course I am currently taking for a certification! Never heard of a hub before and didn't even realize this feature of switches I've been using forever! I've always viewed switches the way I now know hubs work, thank you sir!
BTCInstrumentation Your video was succinct, clear and very helpful to a person who likes to tinker with literally, a room full of acquired stuff. I happened to see your thumbnail while actually looking for something else. This is now one of my bookmarks/favorites. Thank you much.
The way you just explained this, made sooo much better sense. i currently own a hub off of a router. i was looking for a reason to get a switch. thanks for the tutorial.
Nice job on this video. I'm using it for our tech support people so they can get the impact of the data switch's behavior on troubleshooting matters. Really glad I found this one.
This is a great video. I was having trouble with a LAN party playing the game Halo on the Xbox 360. This video provided a good explanation on why some of my problems occurred.
The only reason for the delay when switching the PLC to a new port is the fact that it almost never transmits on its own (possibly once every 5 minutes). If it was reconfigured to transmit a frame every few seconds, this wouldn't be an issue. (For example, if you had two full-fledged computers connected to the switch, those networking stacks are going to talk so frequently that there would be almost no delay when changing ports under pretty much any circumstances)
Wow. nicely explained. This little piece of info will serve me well ;-) I just watched a video by Eli the Computer Guy, where he mentioned a bad point about a Buffalo Switch's loop detection. When the loop detection is switched on it had to be power cycled before the feature worked. He didn't mention why that would be the case. After watching this video I'm guessing it has something to do with what you just explained...detection of specific MAC address to specific port...nice
Okay, this be an old schooling video from 2013 but exactly this is all correct! Thanks for make it. Anno 2016 no one use more an extra hub now, only for diagnostic service we like. This "calling in the room" of a hub is it what we service technicans love to use. But many modern managed switches do you can use as hub for the ports how you likes.
Ethernet originated as a "bus" architecture, multiple nodes on a single shared cable. Over time it evolved to use hubs, repeaters, and bridges to expand and extend the maximum distances between nodes. It later became more of a star configuration, as we have today, where you almost invariably have an active network device interconnecting things, acting as a sort of traffic cop for the data packets. I worked with Ethernet back in the early days, even fixed a major throughput problem by understanding the difference between Ethernet 2.0 and IEEE 802.3 standards ("heartbeat" vs. SQE). We've come a long way, but understanding how things work at the lower levels, as this video shows, can really help when fighting problems or preventing them in the first place.
My first Ethernet experience was in the mid 80s, with DECnet over 10base5 Thicknet. In 1989, I hand wired a couple of Ethernet controllers on prototyping boards for Data General Eclipse computers. I also had some experience along the way with 10base2 Thinnet. In spring 1997, I was working on a job to convert some Ontario government offices from 10base2 to 10baseT, so they could move to switches. These days, my home LAN is 1 Gb and with my Internet connection around 920 Mb down, it may soon be time to upgrade my network.
***** No. the hub will actually cause you to get IP conflicts on your network. The hub will work fine as long as only one device on it is operating at a time. But because it does not assign IP addresses to each device with DHCP, if you turn on two devices connected to a hub at the same time, they will start trying to use the same IP address and you will get IP conflict error messages. Go ahead, use a switch. They're cheap and you'll never even know it's there. Everything will just work.
+Steve Warren That's completely wrong. A hub (or switch) has NOTHING to do with assigning IP addresses - if you get you get duplicate IP addresses, there's something else wrong in you network.
+Steve Warren Hubs are more common then you think, alot of what is marketed as a switch today are really just hubs. a hub operates on layer 1, a switch operates on layer 2 of the OSI model. a hub passes date to every port attached, a real switch only sends the packet to the port that is leads to the destination of said packet.
Informative... Curious about this before but never enough to follow up and get informed. came across your vid so watched it. Thank you! and btw... I duno who you sound like, and this prob makes me sound weird, but you have a very pleasant speaking (or at least teaching) voice! So Good Job on that as well! lol
Wonderful Explanation! I figure that unless a *Ethernet* *Switch* is way faster than a *Ethernet* *Hub,* I'll go with a Hub. A Hub definetly sounds like it's a _"set & forget it"_ situation.
Can you even buy a hub these days? Most hubs were 10 Mb, though there were some at 100 Mb. Switches are often 1 Gb or more these days. You're also likely slowing down your Internet connection, unless you have a really slow one. I have 1 Gb switches here and I get 920 Mb down on my Internet connection.
Thank you this is a wonderful video. HUB\SWITCH I'll be damned! I was about to loose my S*%$ so bad until I found this video. I just wanted to try a SRX200 HUB and made it more complicated by bridging two Ethernet cards.
Unfortunately this does not work. If you move the master (HMI) cable to another port, the problem remains. Ethernet frames sent to the PLC still get sent to the old PLC port, until the timer times out or the switch is reset.
There should be dead-timers within the switch CAM table to flush old MAC Address entries. But you'll have to wait. Otherwise, you can always power cycle switch to clear CAM table. Nice video.
great video thank you so much for clearing up my question. i had a question i have a cable modem with 4 outlets one for the cable and 3 for your use. now i have 5 computers all wired not wifi. i also have vonage internet phone that needs connected too. i have have twc fastest internet connection they offer for the home. it is 50 Mbps down and 10 Mbps up. so i could get a gigabit switch plug everything into it then one cable from the switch to the cable modem, correct? right now i have 2 computers and phone wired and 3 computers on wifi but i want all wired. so will the switch help me with connection and speed over using just the modem only? the switch i am looking at is TRENDnet TEGS16DG Gigabit GREENnet Switch. is this a good switch to buy? or what do you suggest? again thanks for your help.
Just love the so called experts (X being an unknown quantity and spert being a drip under pressure ) who just want to can this excellent demonstration on the differences between a switch and a hub. Ipreams is a good example of a know it all.
Thanks. but now that you explained the difference. it made a world of a difference. because I could NOT figure out why my brand new Linksys 8 port switch was all of a sudden slower than my older switch. as they in New England. "if you don't like the weather. wait 5 min " thanks
