Firewall.cx Forums

Community Forums

Facebook Fans

Show your support for Firewall.cx!

Social Media Channels

Facebook-icon LinkedIn-icon Twitter-icon

System Login



Login With Facebook

More Articles

Who's Online

We have 180 guests online

Statistics

Members : 5036
Content : 718
Content View Hits : 98815284

Top Website Visitors

41.4%United States United States
18.2%India India
8%United Kingdom United Kingdom
5.1%Australia Australia
4.3%Canada Canada
2.5%Germany Germany

Today: 1466
Yesterday: 6200
This Week: 20405
Last Week: 35290
This Month: 83110
Last Month: 141872
Total: 884548

Gold Cisco Lab Partners

logo-gfi



logo-datavision

Unicast PDF Print Email
(9 votes, average 4.56 out of 5)
Written by Administrator   
Sunday, 17 April 2011 17:38
AddThis Social Bookmark Button

Introduction

Compaired to broadcasts and Multicasts, a Unicast is very simple and one of the most common data transmissions in a network. This article  explains what unicats are and how they are used within the Local Area Network to allow hosts to communication with each other.

The Reason for Unicast


Well it's pretty obvious why they came up with Unicasts, imagine trying to send data between 2 computers on a network, using broadcasts ! All you would get would be a very slow transfer and possibly a conjested network with low bandwidth availability.

Data transfers are almost all of the times, unicasts. You have the sender e.g a webserver and the receiver e.g a workstation. Data is transfered between these two hosts only, where as a broadcast or a multicast is destined either everyone or just a group of computers.

unicast-1

In example above, my workstation sends a request to the Windows 2000 Server. The request is a simple Unicast because it's directed to one machine (the server) and nothing else. You just need to keep in mind that because we are talking about a Ethernet network, the traffic, hence the packets, are seen by all machines (in this case the Linux Server aswell) but they will not process them once they see that the destination MAC address in the packets do not match their own and are also not set to FF:FF:FF:FF:FF:FF which would indicate that the packet is a broadcast


Last Updated on Friday, 22 April 2011 00:48
 

SIMILAR TOPICS THAT MIGHT INTEREST