On Fri, Apr 3, 2026 at 3:49 PM Ido Schimmel <[email protected]> wrote:
>
[...]
>
> Is there a reason to place them in bridge_vlan_mcast.sh given they are
> not specific to the per-VLAN multicast context? bridge_{igmp,mld}.sh
> looks like a better fit.
I could see the framework is ready to validate using
bridge_vlan_mcast.sh script. Just had to apply a new tc rule to
validate QEURY+MRC/QQIC fields. Something like this.
tc filter add dev $dev egress pref 10 prot 802.1Q \
flower vlan_id 10 vlan_ethtype ipv4 dst_ip
224.0.0.1 ip_proto 2 \
+ action continue
+ # AND Type 0x11 (Query) at offset 24 after IP
+ # IP (20 byte IP + 4 bytes Option)
+ tc filter add dev $dev egress pref 20 prot 802.1Q u32 \
+ match u8 0x11 0xff at 24 $intvl_match \
action pass
And writing a few lines will validate the test for IGMPv3 QQIC non
linear value of 160s.
+ RET=0
+ bridge vlan global set vid 10 dev br0 mcast_snooping 1
mcast_query_interval 16000
+ check_err $? "Could not set mcast_query_interval in vlan 10"
+ log_test "Vlan 10 mcast_query_interval option changed to 16000"
+ # 1 is sent immediately, IGMPv3 QQIC should match with non
linear value 160s
+ vlmc_check_query igmp 3 $swp1 1 1 160
+ check_err $? "Wrong QQIC in sent tagged IGMPv3 general queries"
+ log_test "Vlan 10 mcast_query_interval in IGMPv3 is 160"
>
[...]
> > Vlan 10 mcast_query_interval:
> > TEST: Number of tagged IGMPv2 general query [ OK ]
> > TEST: IGMPv3 QQIC linear value 60 [ OK ]
> > TEST: IGMPv3 QQIC non linear value 160 [ OK ]
> > TEST: MLDv2 QQIC linear value 60 [ OK ]
> > TEST: MLDv2 QQIC non linear value 160 [ OK ]
>
> I find the latter clearer.
I thought so, hence asked which would be a better version of log.
Thanks for clearing it.
