Sending IGMP v3 Join

[haydenryan]

Hi all, I'm having an issue sending an IGMP v3 packet. I doubt it's an issue with nemesis itself, but rather my knowledge of it - I am hoping someone here is able to assist.

I modified the example in the docs for an IGMP v2 join, to:

sudo nemesis igmp -v -p 0x22 -S 192.168.69.62 -g 224.0.1.116 -D 224.0.0.2

However, watching with Wireshark shows an IGMPv3 Membership Report, but it indicates that it is a malformed packet. I found 0x22 as an option under nemesis igmp help. I attempted to craft a payload, but with my limited knowledge it did not go too well!

If anyone is able to provide any suggestions, it would be much appreciated. And if it is possible to send a v3 join packet, this may be useful in the docs.

Thank you

[troglobit]

Yeah, this could really need some usability improvement. An IGMPv3 membership report can contain up to 183 group join/leave messages (an IGMPv2 membership report is join/leave for a single group). So having some simple (*,G), and (S,G) text file or similar to read this data from to generate a report would be really useful.

I've actually had the same need myself, but we ended up using scapy instead.