You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was writing some unit tests that involved crafting ICMP6 packets with your library and comparing computed checksums of your library against my own implementation of checksum calcs.
What's strange is that if I create an ICMP6 payload in a byte array, create an instance of IcmpV6Packet from that byte array, then create an instance of IPv6Packet.RandomPacket(), then make the ICMP packet the payload packet of the IPv6Packet and calc checksums, I don't get expected values. Yet, if I take a pcap payload of the same thing and simply parse it all like this:
Everything is as expected. It looks like what is happening when crafting is that the first 32 bits of the payload are getting collapsed into the tail 32 bits of the ICMP header. I'm unsure if this is correct behaviour. To be honest I'm still not sure if this is a bug of mine or yours, I'm only leaning lightly in your direction because of the inconsistency between crafting with the API and parsing complete packets.
The text was updated successfully, but these errors were encountered:
Hi there,
I was writing some unit tests that involved crafting ICMP6 packets with your library and comparing computed checksums of your library against my own implementation of checksum calcs.
What's strange is that if I create an ICMP6 payload in a byte array, create an instance of
IcmpV6Packet
from that byte array, then create an instance ofIPv6Packet.RandomPacket()
, then make the ICMP packet the payload packet of theIPv6Packet
and calc checksums, I don't get expected values. Yet, if I take a pcap payload of the same thing and simply parse it all like this:Everything is as expected. It looks like what is happening when crafting is that the first 32 bits of the payload are getting collapsed into the tail 32 bits of the ICMP header. I'm unsure if this is correct behaviour. To be honest I'm still not sure if this is a bug of mine or yours, I'm only leaning lightly in your direction because of the inconsistency between crafting with the API and parsing complete packets.
The text was updated successfully, but these errors were encountered: