-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
icmpv4 time exceeded message #102
Conversation
Also includes: - doc fixes for links to private fns
Codecov Report
@@ Coverage Diff @@
## master #102 +/- ##
==========================================
+ Coverage 67.00% 67.15% +0.14%
==========================================
Files 63 64 +1
Lines 5377 5459 +82
==========================================
+ Hits 3603 3666 +63
- Misses 1774 1793 +19
Continue to review full report at Codecov.
|
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.
👍 good.
core/src/packets/icmp/v6/mod.rs
Outdated
@@ -252,7 +252,7 @@ impl<E: Ipv6Packet> Packet for Icmpv6<E> { | |||
/// * [`checksum`] is computed based on the [`pseudo-header`] and the | |||
/// full packet. | |||
/// | |||
/// [`checksum`]: Icmpv6::checksum | |||
/// [`checksum`]: Icmpv6Packet::checksum |
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.
noticed that functions on Icmpv4
and Icmpv6
have inconsistent visibility scopes. msg_type
, code
, set_code
, checksum
, compute_checksum
should all be pub on Icmpv6. then don't need to fix these links anymore.
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.
good. I was going to do this, but wasn't sure why we had the inconsistency.
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.
yep not sure how I missed this, but they need to be public so extending Icmpv6
is possible from outside the crate.
Description
Time Exceeded Message defined in [IETF RFC 792] (for ICMPv4).
Also includes:
Type of change
Checklist