Raw socket

From Wikipedia, the free encyclopedia

In computer networking, a raw socket is an internet socket that allows direct sending and receiving of Internet Protocol packets without any protocol-specific transport layer formatting.

Raw sockets vs standard sockets

In standard sockets, the payload to be transmitted is encapsulated according to the chosen transport layer protocol (e.g. TCP, UDP). In contrast, raw sockets usually receive raw packets including the header. When transmitting packets, the automatic addition of a header may be a configurable option of the socket.

Uses

One possible use case for raw sockets is the implementation of new transport-layer protocols in user space.[1]

Raw sockets are typically available in network equipment, and used for routing protocols such as the Internet Group Management Protocol (IGMP) and Open Shortest Path First (OSPF), and in the Internet Control Message Protocol (ICMP, best known for the ping suboperation).[2]

Support by socket APIs

Most socket application programming interfaces (APIs), especially those based on Berkeley sockets, support raw sockets.

Windows XP

When Microsoft released Windows XP in 2001 with raw socket support implemented in the Winsock interface, the media criticized Microsoft[3] asserting that raw sockets are only of use to hackers to perform TCP reset attacks. Three years after the Windows XP release, Microsoft silently limited Winsock's raw socket support in a non-removable hotfix and offered no further support or workarounds for applications that used them.[4]

See also

References

  1. ↑ Linux man page raw(7)
  2. ↑ Raw IP Networking FAQ
  3. ↑ http://www.informit.com/articles/article.aspx?p=27289
  4. ↑ Microsoft Tightens the Noose on Raw Sockets

External links

This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.