Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Mastering Grub 2 The Easy Way

Shedding commercial attitudes towards documentation

Will secret copyright treaty restrict your digital rights?

Saving the "Best" for Last - Fedora 12 (Constantine)

LinuxCertified Announces its next Linux System and Network Administration BootCamp

The Problem With The Linux Community

Vim 101: A Beginner's Guide to Vim

Open Source Science: A Revolution From Within

openSUSE 11.2-- Incremental Updates, Plenty of Polish

Microsoft, other rivals slam Google Chrome OS




Technical Specialist II – PC – LAN (AZ)
Next Step Systems
US-AZ-Scottsdale

Justtechjobs.com Post A Job | Post A Resume
:Networking 101: Understanding the Data Link Layer
Networking 101: Understanding the Data Link Layer
Aug 20, 2008, 23 :04 UTC (5 Talkback[s]) (4184 reads)

(Other stories by Charlie Schluting)

"Ethernet switches, as they're called now, began life as a "bridge." Traditional bridges would read all Ethernet frames, and then forward them out every port, except the ones they came in on. They had the ability to allow redundancy via STP, and they also began learning which MAC addresses were on which port. At this point, a bridge then became a learning device, which means they would store a table of all MAC addresses seen on a port. When a frame needed to be sent, the bridge could look up the destination MAC address in the bridge table, and know which port is should be sent out."

Complete Story

Related Stories:
Linux to Windows and Back Again With Samba(Aug 15, 2008)
10 quick tips to make Linux networking easier(Aug 15, 2008)
Networking 101: Understanding Layers(Aug 13, 2008)
Networking 101: Subnets Realized (Including IPv6)(Aug 07, 2008)
Networking 101: Understanding Subnets and CIDR(Jul 31, 2008)
Networking 101: Understanding IP Addresses(Jul 25, 2008)


Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat  
  Talkback(s) Name  and Date
The posted link leads to the previous ar ...   Bad link   
Vance
Aug 21, 2008, 05:06:46
 
The provided link is for Understanding L ...   Wrong Link   
blackhole
Aug 21, 2008, 06:30:08
 
> The provided link is for Understanding ...   Re: Wrong Link   
Dale Pontius
Aug 21, 2008, 14:11:29
 
Link fixed-- ed.Thanks!  I'm looking ...   Re: Bad Link   
Vance
Aug 21, 2008, 16:55:58
 
> Link fixed-- ed.> >Thanks!  I'm lo ...   Re: Re: Bad Link   
Carla Schroder
Aug 21, 2008, 17:50:38
 
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs