Couldn't find a way to add key words. So, this was found as IGMP and if you want to get to the real discussion about IGMPv3, see the following link. https://sourceforge.net/p/packetnet/discussion/1045280/thread/d364ae9e90/#2035
I don't see any support for IGMPv3 in the latest version (1.2.0). I only see support for IGMPv2. In this version you can see that there is a Type of MembershipReportIGMPv3, but no IGMPv3 packet object. This protocol (IGMPv3) has been around for many years. Am I missing something? Also, related, there should be a Type (in the IGMPv2 packet object) for PimV1. This is a legitimate type. All of this can be found in RFC 3376 (Oct 2002 - yes, that long ago!).
Decode IPV6-ICMPV6 protocol crash. PacketDotNet don't support the decoding IPV6 ...
Problems when capture length is different of actual packet length
IGMPv2PacketTest: Switch from IpAddress.Address...
Add 'F' to indicate a field in <see cref> to si...
Clean up some xml documentation to match the st...
InformationElementTest: Remove unused 'infoElem...
Fix several warnings about malformed documentat...
InformationElement.ErpInformation2, add stub do...
[Serializable] Attribute added to the protocol ...
[Serializable] Attribute added to the protocol ...
[Serializable] Attribute added to the protocol ...
Hello. I'm the author of packet.net and sharppcap. Have you looked to see if any...
Not able to set Time Stamps in TCp Hedaer Package.
When there are packets with different capture length and actual length the wrong...
No longer try to parse IP fragments to avoid pa...
Add capture file and unit tests to verify corre...
I opened this as a bug on SharpPcap before realizing it belonged in Packet.Net, and...
Attempting to set a negative length of -4