This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 14 and 16 (spanning 2 versions)
Revision 14 as of 2005-10-25 00:07:23
Size: 4382
Editor: GuyHarris
Comment: Edits.
Revision 16 as of 2006-08-24 08:28:21
Size: 4619
Editor: dslb-084-056-074-153
Comment: add capture filter for subnets
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
XXX - Add example traffic here (as plain text or Ethereal screenshot). XXX - Add example traffic here (as plain text or Wireshark screenshot).
Line 35: Line 35:
== Ethereal == == Wireshark ==
Line 37: Line 37:
IP dissector is fully functional. Ethereal provides some advanced features such as IP defragmentation. IP dissector is fully functional. Wireshark provides some advanced features such as IP defragmentation.
Line 45: Line 45:
XXX - Add a simple example capture file. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically. XXX - Add a simple example capture file. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
Line 48: Line 48:
A complete list of IP display filter fields can be found in the [http://www.ethereal.com/docs/dfref/i/ip.html display filter reference] A complete list of IP display filter fields can be found in the [http://www.wireshark.org/docs/dfref/i/ip.html display filter reference]
Line 70: Line 70:
 Capture only the IP-based traffic to or from the subnet 192.168.43.0/24 (The /24 is CIDR notation for a network address with a mask of 24 one bits, that is, a subnet mask of 255.255.255.0): {{{
 ip src net 192.168.43.0/24 }}}

Internet Protocol version 4 (IP)

The Internet Protocol provides the network layer (layer 3) transport functionality in the InternetProtocolFamily.

This page describes IP version 4, which is widely used. There's also an ["IPv6"] protocol page available.

The IP protocol is used to transfer packets from one ["IP-address"] to another. The user of this layer will give a packet and a remote IP address, and IP is responsible to transfer the packet to that host.

IP will (hopefully) guide the packet the right way to the remote host. The data transfer is independant of the underlying network hardware (e.g. ["ATM"], ["Ethernet"], or even a SerialLine). If the underlying hardware is not able to transfer the maximum length required (especially on SerialLine's or ["ATM"]), IP will split the data into several smaller IP fragments and reassemble it into a complete one at the receiving host.

When IP wants to send a packet on a LAN, it must first translate the ["IP-address"] given into the underlying hardware address (e.g. an ["Ethernet"] address). IP uses ["ARP"] for this translation, which is done dynamically. On a point-to-point line, this is obviously not necessary, as there's only one host to which a given machine can send a packet.

IP doesn't provide any mechanism to detect PacketLoss, DuplicatePackets and alike.

IP uses ["ICMP"] to transfer control messages to a remote host such as "Please don't send me more IP packets, I'm full". The famous ping tool also use ["ICMP"].

The typical protocols on top of IP are ["TCP"] and ["UDP"].

Version 4 of the IP protocol is widely used all over the world. As the available ["IP-address"] range is becoming short, version 6 with a much wider address range is becoming more and more popular these days.

History

The [http://www.ietf.org/rfc/rfc791.txt RFC791] "INTERNET PROTOCOL" was released in September 1981.

Protocol dependencies

  • ["Ethernet"]: IP can use ["Ethernet"] and many other protocols. The assigned Ethernet type for IP is 0x800.
  • ["ICMP"]: IP uses ["ICMP"] for control messages between hosts.

Example traffic

XXX - Add example traffic here (as plain text or Wireshark screenshot).

Wireshark

IP dissector is fully functional. Wireshark provides some advanced features such as IP defragmentation.

Preference Settings

(XXX add links to preference settings affecting how IP is dissected).

Example capture file

XXX - Add a simple example capture file. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of IP display filter fields can be found in the [http://www.wireshark.org/docs/dfref/i/ip.html display filter reference]

  • Show only IP-based traffic (beware: you won't see any ARP packets if you use this filter!):

     ip 

    Show only the IP-based traffic to or from host 192.168.0.10:

     ip.addr==192.168.0.10 

    Show only the IP-based traffic to or from the subnet 192.168.43.0/24 (The /24 is CIDR notation for a network address with a mask of 24 one bits, that is, a subnet mask of 255.255.255.0):

     ip.addr==192.168.43.0/24 

    Show only the IP based traffic not to or from host 192.168.0.10 (beware: this is not identical to ip.addr!=192.168.0.10):

     !(ip.addr==192.168.0.10) 

Capture Filter

  • Capture IP based traffic only:

     ip 

    Capture only the IP based traffic to or from host 192.168.0.10:

     host 192.168.0.10 

    Capture only the IP-based traffic to or from the subnet 192.168.43.0/24 (The /24 is CIDR notation for a network address with a mask of 24 one bits, that is, a subnet mask of 255.255.255.0):

     ip src net 192.168.43.0/24 

Discussion

Internet_Protocol (last edited 2018-10-09 12:21:34 by AlexHammer)