What is an IP Packet?

Computers are not only integral to today’s world but they have become a passion. Hotels, cafes and even townships have made Internet access available, answering the demand for connectivity. But how does information travel across cyberspace from one computer to another? Like Star Trek’s transporter, information is disassembled into small blocks of data, sent independently to the destination address, then reassembled at the receiving end. Each block of data is known as an IP packet.

Every time you connect to the Internet, your Internet service provider assigns your computer a unique numerical address. This unique address identifies your computer on the network so that you can request and receive information. The address is known as an Internet Protocol (IP) address. When you initiate a request, such as clicking on a link in your Web browser, the request travels across the Internet in the form of data packets stamped with your IP address. Hence the term, IP packets.

Due to the structure of networks, small IP packets work more efficiently than large packets. A single, large IP packet would not only take longer to transmit, but high traffic conditions would quickly clog the network. Sending smaller packets (up to about 1500 bytes) has the advantage of moving more traffic through available routes at a faster pace with less chance of creating bottlenecks. Consequently, each IP packet travels the Internet independently, guided by routers that read the destination address and forward the packet along the fastest available route. At the destination address the packets are reassembled.

The protocol responsible for orchestrating the movement of IP packets through cyberspace is the Transfer Control Protocol, better known as TCP. TCP is “layered” on top of the addressing protocol (IP) to break requests into small packets, monitor the arrival of each IP packet at the destination address, call for the re-transmission of missing packets, and reassemble the packets into the original form. This protocol suite is known as TCP/IP, a term likely familiar to anyone who has setup an Internet connection.

Each IP packet carries vital information that allows it to be properly manipulated by TCP. The “DNA” of an IP packet includes, among other things, the size of the IP packet, sender and destination addresses, and the payload itself, or the data being sent. Packet numbering, error reporting and fragmentation are also included, with an end-of-life stamp to prevent lost packets from bouncing endlessly in cyberspace as junk traffic. Packets that don’t make it to their destination in time are simply discarded.

A successful transmission is processed by a Web server that responds by sending the requested webpage, which itself is broken into IP packets for the return trip to your computer screen. These rushing data packets make up “The Information Superhighway.”

While TCP/IP might sound involved, it operates faster than Star Trek’s transporter under normal conditions. So what’s up with those occasional slow page loads? Assuming your computer is capable of quickly processing page content, a sluggish load can be caused by third party ad servers or a busy website that is processing more requests than its hardware can comfortably juggle.

Despite the robust nature of TCP/IP, there is a downside to the protocol. Anyone can “listen in” to what it being transmitted between your computer and the Internet without your knowledge. How is this possible?

A typical IP packet might pass though several routers and servers before reaching its destination. At any point along the way, specialized software or hardware can “trap” the data packet, taking a snapshot before forwarding it along. The interloper’s stolen copy can be analyzed and read at will, as IP packet payloads are sent as plain text, sometimes referred to as “in the clear.” Tools that trap IP packets are known as “packet sniffers.”

Network administrators legitimately use packet sniffers to troubleshoot local area networks (LANs) and to filter unwanted traffic coming in from the Internet. Law enforcement can plant packet sniffers on an Internet Service Provider to monitor some or all of its traffic, if the provider agrees or is compelled by law to comply. But packet sniffers can also be used by virtually anyone to simply eavesdrop, or worse, steal sensitive information like passwords and usernames sent over unencrypted channels.

With identity theft on the rise and concern for privacy at an all time high, the best way to protect yourself from packet sniffers is to use encryption for all transmissions that contain personal information. Encrypted packets are unreadable en route, and are only decrypted at the destination address.

Online retailers already provide secure, encrypted connections for passing data between your computer and the website. To check for encryption, look for https in the Web browser’s address field. That extra “s” stands for security, and indicates all traffic between your computer and the Web server is encrypted. Your computer will still generate IP packets, but the payload portion of the IP packet will be in unreadable cipher, protecting credit cards, bank accounts, and other highly sensitive information from prying eyes.

Since the IP packet is also used for email, file transfers, telnet, and other networking services, you might also choose to encrypt other transmissions. Pretty Good Privacy (PGP), a military grade encryption program, can automatically encrypt mail in several popular email programs. GNU Privacy Guard (GPG), based on the same source code but part of the Free Software Foundation, is another encryption program. GPG used with the Enigma plugin provides Mozilla™ Thunderbird™ with fully automated, easy to use encryption.

Web surfing can be encrypted through security services online, though it might slow surfing and is probably overkill for the average person. Surfing by using anonymous proxy servers that sit between your computer and the Internet is a more common alternative for those who wish to surf anonymously.

Additional protocols can be bundled with TCP/IP to form other “suites” that accommodate different types of networking environments and hardware. In special situations the User Datagram Protocol (UDP) is sometimes substituted for TCP, but provides no mechanism for IP packet loss, lacking TCPs ability to call for retransmissions. Network host computers might use several additional protocols for exchanging router information, such as Internet Control Message Protocol (ICMP), the Interior and Exterior Gateway Protocols (IGP/EGP), and the Border Gateway Protocol (BGP).

Using the Internet from the familiar settings of home or school causes many people, especially children, to feel a false sense of security and privacy. A basic understanding of the “vulnerability” of the IP packet and the ubiquitous availability of packet sniffers drives home the point that one should always check for a secure, encrypted connection (https) before sharing sensitive information online. The rule is, anything that travels unencrypted should be considered public and not private.