search for: igmpv3

The testsuite that checks for mcast_max_groups functionality will need to generate IGMP and MLD packets with configurable number of (S,G) addresses. To that end, further extend igmpv3_is_in_get() and mldv2_is_in_get() to allow a list of IP addresses instead of one address. Signed-off-by: Petr Machata <petrm at nvidia.com> --- tools/testing/selftests/net/forwarding/lib.sh | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/tools/testin...

..._mdb.sh b/tools/testing/selftests/net/forwarding/bridge_mdb.sh index 2fa5973c0c28..51f2b0d77067 100755 --- a/tools/testing/selftests/net/forwarding/bridge_mdb.sh +++ b/tools/testing/selftests/net/forwarding/bridge_mdb.sh @@ -1018,26 +1018,6 @@ fwd_test() ip -6 address del fe80::1/64 dev br0 } -igmpv3_is_in_get() -{ - local igmpv3 - - igmpv3=$(: - )"22:"$( : Type - Membership Report - )"00:"$( : Reserved - )"2a:f8:"$( : Checksum - )"00:00:"$( : Reserved - )"00:01:"$( : Number of Group Records - )"01:"$( : Record Type -...

...the receiving host across bridge br1 > > [root@clusterdev02 ~]# tshark -i br1 -f "igmp or host 239.11.12.13" > Running as user "root" and group "root". This could be dangerous. > Capturing on 'br1' >     1 0.000000000 192.168.0.120 → 224.0.0.22   IGMPv3 54 Membership > Report / Join group 239.11.12.13 for any sources >     2 0.902032534 192.168.0.120 → 224.0.0.22   IGMPv3 54 Membership > Report / Join group 239.11.12.13 for any sources >     3 41.448921858 192.168.0.110 → 239.11.12.13 UDP 60 5555 → 5555 Len=10 > > // 4. previou...

Hi Laine What you have suggested sounds eminently reasonable. Thanks for your advice. I'm going to give it a shot and report back. Richard On 11/27/19 1:38 PM, Laine Stump wrote: > On 11/26/19 11:07 PM, Richard Achmatowicz wrote: >> Hello >> >> I have a problem with attaching VMs to a VLAN interface. >> >> Here is my setup: I have several physical hosts

...0.251 // 3. tshark on the receiving host across bridge br1 [root@clusterdev02 ~]# tshark -i br1 -f "igmp or host 239.11.12.13" Running as user "root" and group "root". This could be dangerous. Capturing on 'br1'     1 0.000000000 192.168.0.120 → 224.0.0.22   IGMPv3 54 Membership Report / Join group 239.11.12.13 for any sources     2 0.902032534 192.168.0.120 → 224.0.0.22   IGMPv3 54 Membership Report / Join group 239.11.12.13 for any sources     3 41.448921858 192.168.0.110 → 239.11.12.13 UDP 60 5555 → 5555 Len=10 // 4. previously started multicast test...

Hello, Can anyone tell me why the maximum number of members in a multicast group is set at 20? Are there issues with increasing this number? Any information would be greatly appreciated. Thanks, Steve Clark -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a

...hanged, 50 insertions(+) diff --git a/tools/testing/selftests/net/forwarding/lib.sh b/tools/testing/selftests/net/forwarding/lib.sh index 9f180af2cd81..7b3e89a15ccb 100755 --- a/tools/testing/selftests/net/forwarding/lib.sh +++ b/tools/testing/selftests/net/forwarding/lib.sh @@ -1815,6 +1815,21 @@ igmpv3_is_in_get() payload_template_expand_checksum "$igmpv3" $checksum } +igmpv2_leave_get() +{ + local GRP=$1; shift + + local payload=$(: + )"17:"$( : Type - Leave Group + )"00:"$( : Max Resp Time - not meaningful + )"CHECKSUM:"$( : Checksum + )&qu...

How do the Multicast routers sniff IGMP/MLD messages from the network? I checked the XORP, pimd etc. Most of them just open a RAW socket with protocol set to IPPROTO_IGMP. But using this the router gets the packets addressed to 224.0.0.1 only. How does it receive IGMPv2 and IGMPv3 membership reports sent by other hosts? Thanks, Sachin