Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upExtend suite of ICMPv4 Messages #104
Open
Assignees
Labels
Comments
zeeshanlakhani
changed the title
|
Working on destination unreachable message |
|
Working on Redirect message |
|
Working on Source Quench message |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 almost1 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:
Others:
1 Not including Mobile IP extensions here.