Extend suite of ICMPv4 Messages

[zeeshanlakhani]

Background

ICMP messages are used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address. Examples include errors indicating when a requested service is not available or when a host or router could not be reached. We've implemented a few ICMPv4 messages thus far in Capsule, but we'd like to include more.

Solution

Implement almost¹ all ICMPv4 message types in Capsule. For reference on how to handle these kinds of messages, please look at what's been implemented thus far @ https://github.com/capsule-rs/capsule/tree/master/core/src/packets/icmp/v4.

Format information for most messages can be found in RFC 792 and RFC 1256 (Sorry, no anchor links!).

Another helpful resource is available via IANA, including RFC 2780 for helpful considerations.

Message Types

Good First Issues from RFC 792:

• Echo Reply
• Destination Unreachable
• Source Quench
• Redirect
• Echo (Request)
• Time Exceeded
• Parameter Problem
• Timestamp
• Timestamp Reply
• Information Request
• Information Reply

Others:

• Router Advertisement ~ RFC 1256¹
• Router Solicitation ~ RFC 1256¹
• Extended Echo Request ~ RFC 8335
• Extended Echo Reply ~ RFC 8335

¹ Not including Mobile IP extensions here.

[scrollins]

Working on destination unreachable message

[ari23]

Working on Redirect message

[ari23]

Working on Source Quench message