-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IP options in IPv4 header #349
Conversation
Please update example by actually adding item in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor documentation comments. Rest looks good to me.
Please update the example to reflect the changes for adding custom option. Also need to actually add option to packet template I think as @rudranil-das had mentioned to make it a valid snippet. |
Updated code snippet. @rudranil-das @apratimmukherjee |
ReDocly link:
ReDoc Interactive Demo (redocly.github.io)
( New object at : set_config/flows/packet/ipv4/options )
IPv4 RFC: RFC791
Router Alert Option RFC: RFC2113
IPv4 Options parameters
Objective: IPv4 options are optional extensions for the IPv4 header that can be utilised to provide additional information about the IPv4 datagram. It is encoded as a series of type, length and value attributes. The IP header length MUST be increased to accommodate the extra bytes needed to encode the IP options.
Currently IP options supported are:
IPv4 Options is an array option objects.
To support RSVP control packet, router alert option is required in IP header.
Sample IPv4 Options (Router Alert and Custom):