Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 11-27-2008, 12:55 AM   #1
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Rep: Reputation: 36
Question difference between Packets, Frames, Datagrams and Cells

what exactly is the difference between Packets, Frames, Datagrams and Cells ? to what extent the description given here

is correct ?

# Packet: This term is considered by many to most correctly refer to a message sent by protocols operating at the network layer of the OSI Reference Model. So, you will commonly see people refer to “IP packets”. However, this term is commonly also used to refer generically to any type of message, as I mentioned at the start of this topic.

# Datagram: This term is basically synonymous with “packet” and is also used to refer to network layer technologies. It is also often used to refer to a message that is sent at a higher level of the OSI Reference Model (more often than “packet” is).

# Frame: This term is most commonly associated with messages that travel at low levels of the OSI Reference Model. In particular, it is most commonly seen used in reference to data link layer messages. It is occasionally also used to refer to physical layer messages, when message formatting is performed by a layer one technology. A frame gets its name from the fact that it is created by taking higher-level packets or datagrams and “framing” them with additional header information needed at the lower level.

# Cell: Frames and packets, in general, can be of variable length, depending on their contents; in contrast, a cell is most often a message that is fixed in size. For example, the fixed-length, 53-byte messages sent in Asynchronous Transfer Mode (ATM) are called cells. Like frames, cells usually are used by technologies operating at the lower layers of the OSI model.
Old 11-27-2008, 11:05 AM   #2
Senior Member
Registered: Dec 2000
Location: Gothenburg, SWEDEN
Distribution: OpenSUSE 10.3
Posts: 1,028

Rep: Reputation: 45
I must agree that all the terms and word used in networking is a bit confusing and sometimes intimidating.
As you might already know the network communication is structured in layers, each layer responsible for certain tasks.
Each layer referes to the incoming information units by a different name.

Data is divided into segments, which are then "put inside" datagrams by the next level, these are then "put inside" frames.
Each layer add extra information relevant for the transmission.
Old 12-02-2008, 02:10 PM   #3
Registered: Jan 2003
Location: Cambridgeshire, UK
Distribution: Mint (Desktop), Debian (Server)
Posts: 880

Rep: Reputation: 184Reputation: 184
The tcp guide is correct. The first four layers deal with data in "chunks" the reason we use different terms is to make it clear what layer we are referring to. If you refer to everything as a packet it causes all sorts of confusion.
Old 12-02-2008, 03:55 PM   #4
Registered: Aug 2006
Posts: 74

Rep: Reputation: 15
Originally Posted by sulekha View Post
# Datagram: This term is basically synonymous with “packet” and is also used to refer to network layer technologies. It is also often used to refer to a message that is sent at a higher level of the OSI Reference Model (more often than “packet” is).
Datagram packets are a type of packet which is not usually ACKed. They are spewed out without expecting a response, a la UDP(user _datagram_ protocol). This makes UDP inherently stateless.

Add TCP to IP and you get TCP/IP packets (which are delivery guaranteed). TCP and UDP are layer 4 protocols, IP is layer 3, and is used by both UDP and TCP.

The description of datagrams doesn't mention lack of delivery guarantee or frame receipt order guarantee, which is a distinction between datagram and other types of packets. With TCP/IP if the sending host doesn't recieve an ACK within the timeout window, it resends the packet. UDP applications don't wait for acks. It's fire and forget networking.

Frames happen at Layer 2, and carry TCP/IP packets, UDP datagrams etc from the host to switch, switch to router, etc. They don't care what the upper layers are doing with guarantees as frames are logically separated from the packets they contain. The frame headers of ethernet contain a CRC for error checking. The difference between layer 4 and 2 is that layer 4 guarantees delivery (when applicable) which makes the internet possible, and at layer 2 the integrity of the packet is tested though this can be done in the applications as well.

Frames are an abstraction for what's happening at layer 1, which is clock synchronized transmission of bits. Layer 1 transmits the frame in the form of clock regulated electrical pulses or light pulses.

Hope this helps...


Last edited by rg.viza; 12-02-2008 at 06:28 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
how to get source physical address of received udp datagrams? lyeoh Linux - Networking 0 05-31-2006 05:35 AM
oocalc drop down cells zippo85 Linux - Software 1 10-13-2005 12:53 AM
Possible to create a frames effect in an HTML page without using frames? furfurdemon666 General 10 12-12-2004 06:52 AM
how to broadcast UDP datagrams sokar Programming 2 02-14-2004 05:37 PM
RFC1149 - Std. for Transmission of IP Datagrams on Avian Carriers Can O' Beans General 2 02-25-2003 05:52 AM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:11 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration