[Xorp-users] IGMP Querier and VLAN Bug in Xorp 1.8.3?

[Patricio Latini]

I have found a weird issue in Xorp seems not to be sending the IGMP
membership query to 224.0.0.1 when the output interface is an 802.1q vlan
interface.

>From Xorp, the packet is shown in the dump however it never arrives to the
server connected on the other side. The curious thing is that membership
report packets(224.0.0.22) arrive without problems

XORP

root at xorp:~# tshark -i vlan30 -R"(igmp)"
Running as user "root" and group "root". This could be dangerous.
Capturing on vlan30
  0.000000   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general
  2.524879   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 10.000458   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general
 19.956889   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 20.000371   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general

Other server directly connected

root at videoserver:~# tshark -i vlan30 -R"(igmp)"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
  4.841084   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 22.272951   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources

On the other side packet going to 224.0.0.1 are passing ok, as sending a
ping from Xorp to 224.0.0.1 is received fine on the server

root at videoserver:~# tshark -i eth0 -R"(ip.addr==224.0.0.1)"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
 28.169015   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 29.177341   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 30.185335   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 31.193331   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 32.201317   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 33.209310   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request

Any idea of what might be happening.

Thanks

Patricio