Struct etherparse::Ipv6FragmentHeaderSlice[−][src]

pub struct Ipv6FragmentHeaderSlice<'a> { /* fields omitted */ }

Expand description

Slice containing an IPv6 fragment header.

Implementations

[src]

impl<'a> Ipv6FragmentHeaderSlice<'a>

[src]

pub fn from_slice(
slice: &'a [u8 ]
) -> Result<Ipv6FragmentHeaderSlice<'a>, ReadError>

Creates a hop by hop header slice from a slice.

[src]

pub unsafe fn from_slice_unchecked(
slice: &'a [u8 ]
) -> Ipv6FragmentHeaderSlice<'a>

Creates a hop by hop header slice from a slice (assumes slice size & content was validated before).

Safety

This function assumes that the passed slice has at least the length of 8. If a slice with length less then 8 is passed to this function the behavior will be undefined.

[src]

pub fn slice(&self) -> &'a [u8 ]ⓘ
Notable traits for &'_ mut [u8 ]
`impl<'_> Write for &'_ mut [u8]impl<'_> Read for &'_ [u8]`

Returns the slice containing the ipv6 fragment header.

[src]

pub fn next_header(&self) -> u8

Returns the IP protocol number of the next header.

See IpNumber or ip_number for a definition of the known values.

[src]

pub fn fragment_offset(&self) -> u16

Fragment offset in 8 octets.

Note: In the header only 13 bits are used, so the allowed range of the value is between 0 and 0x1FFF (inclusive).

[src]

pub fn more_fragments(&self) -> bool

True if more fragment packets will follow. False if this is the last packet.

[src]

pub fn is_fragmenting_payload(&self) -> bool

Checks if the fragment header actually fragments the packet.

Returns false if the fragment offset is 0 and the more flag is not set. Otherwise returns true.

RFC8200 explicitly states that fragment headers that don’t fragment the packet payload are allowed. See the following quote from RFC8200 page 32:

Revised the text to handle the case of fragments that are whole datagrams (i.e., both the Fragment Offset field and the M flag are zero). If received, they should be processed as a reassembled packet. Any other fragments that match should be processed independently. The Fragment creation process was modified to not create whole datagram fragments (Fragment Offset field and the M flag are zero). See RFC6946 and RFC8021 for more information.“

use etherparse::Ipv6FragmentHeaderSlice;

{
    let slice = Ipv6FragmentHeaderSlice::from_slice(&[
        0, 0, 0, 0, // offset 0 & more_fragments not set
        1, 2, 3, 4,
    ]).unwrap();
    assert!(false == slice.is_fragmenting_payload());
}

{
    let slice = Ipv6FragmentHeaderSlice::from_slice(&[
        0, 0, 0, 0b1000_0000u8, // more_fragments set
        1, 2, 3, 4,
    ]).unwrap();
    assert!(slice.is_fragmenting_payload());
}

{
    let slice = Ipv6FragmentHeaderSlice::from_slice(&[
        0, 0, 1, 0, // non zero offset
        1, 2, 3, 4,
    ]).unwrap();
    assert!(slice.is_fragmenting_payload());
}