* Re: [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge [not found] ` <620d3cfbe58e3ae87ef1d5e7f2aa1588cac3e64a.camel@vyatta.att-mail.com> @ 2019-08-14 20:11 ` Linus Lüssing 2019-08-14 20:34 ` Nikolay Aleksandrov 0 siblings, 1 reply; 3+ messages in thread From: Linus Lüssing @ 2019-08-14 20:11 UTC (permalink / raw) To: Patrick Ruddy; +Cc: Nikolay Aleksandrov, Ido Schimmel, roopa, bridge, netdev On Wed, Aug 14, 2019 at 05:40:58PM +0100, Patrick Ruddy wrote: > The group is being joined by MLD at the L3 level but the packets are > not being passed up to the l3 interface becasue there is a MLD querier > on the network > > snippet from /proc/net/igmp6 > ... > 40 sw1 ff0200000000000000000001ff008700 1 00000004 0 > 40 sw1 ff020000000000000000000000000002 1 00000004 0 > 40 sw1 ff020000000000000000000000000001 1 0000000C 0 > 40 sw1 ff010000000000000000000000000001 1 00000008 0 > 41 lo1 ff020000000000000000000000000001 1 0000000C 0 > 41 lo1 ff010000000000000000000000000001 1 00000008 0 > 42 sw1.1 ff020000000000000000000000000006 1 00000004 0 > 42 sw1.1 ff020000000000000000000000000005 1 00000004 0 > 42 sw1.1 ff0200000000000000000001ff000000 2 00000004 0 > 42 sw1.1 ff0200000000000000000001ff008700 1 00000004 0 > 42 sw1.1 ff0200000000000000000001ff000099 1 00000004 0 > 42 sw1.1 ff020000000000000000000000000002 1 00000004 0 > 42 sw1.1 ff020000000000000000000000000001 1 0000000C 0 > 42 sw1.1 ff010000000000000000000000000001 1 00000008 0 > ... > > the bridge is sw1 and the l3 intervace is sw1.1 What kind of interface is sw1.1 exactly? Is it a VLAN or a VRF interface? Something else? Could you also post the output of bridge mdb show? Regards, Linus PS: Also please include the bridge mailinglist in the future. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge 2019-08-14 20:11 ` [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge Linus Lüssing @ 2019-08-14 20:34 ` Nikolay Aleksandrov 2019-08-15 13:36 ` Patrick Ruddy 0 siblings, 1 reply; 3+ messages in thread From: Nikolay Aleksandrov @ 2019-08-14 20:34 UTC (permalink / raw) To: Linus Lüssing, Patrick Ruddy; +Cc: Ido Schimmel, roopa, bridge, netdev On 8/14/19 11:11 PM, Linus Lüssing wrote: > On Wed, Aug 14, 2019 at 05:40:58PM +0100, Patrick Ruddy wrote: >> The group is being joined by MLD at the L3 level but the packets are >> not being passed up to the l3 interface becasue there is a MLD querier >> on the network >> >> snippet from /proc/net/igmp6 >> ... >> 40 sw1 ff0200000000000000000001ff008700 1 00000004 0 >> 40 sw1 ff020000000000000000000000000002 1 00000004 0 >> 40 sw1 ff020000000000000000000000000001 1 0000000C 0 >> 40 sw1 ff010000000000000000000000000001 1 00000008 0 >> 41 lo1 ff020000000000000000000000000001 1 0000000C 0 >> 41 lo1 ff010000000000000000000000000001 1 00000008 0 >> 42 sw1.1 ff020000000000000000000000000006 1 00000004 0 >> 42 sw1.1 ff020000000000000000000000000005 1 00000004 0 >> 42 sw1.1 ff0200000000000000000001ff000000 2 00000004 0 >> 42 sw1.1 ff0200000000000000000001ff008700 1 00000004 0 >> 42 sw1.1 ff0200000000000000000001ff000099 1 00000004 0 >> 42 sw1.1 ff020000000000000000000000000002 1 00000004 0 >> 42 sw1.1 ff020000000000000000000000000001 1 0000000C 0 >> 42 sw1.1 ff010000000000000000000000000001 1 00000008 0 >> ... >> >> the bridge is sw1 and the l3 intervace is sw1.1 > > What kind of interface is sw1.1 exactly? Is it a VLAN or a VRF > interface? Something else? > +1 > Could you also post the output of bridge mdb show? > > Regards, Linus > > > PS: Also please include the bridge mailinglist in the future. > Note that if you'd like to debug a host joined group currently bridge mdb show will not dump it and if the group is host-joined only it can even be empty. You can use my latest set (not applied yet): http://patchwork.ozlabs.org/project/netdev/list/?series=125169 Alternatively you could monitor the mdb events, it will show up there even today without any changes (bridge monitor mdb) and you can check if it's getting deleted. Cheers, Nik ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge 2019-08-14 20:34 ` Nikolay Aleksandrov @ 2019-08-15 13:36 ` Patrick Ruddy 0 siblings, 0 replies; 3+ messages in thread From: Patrick Ruddy @ 2019-08-15 13:36 UTC (permalink / raw) To: Nikolay Aleksandrov, Linus Lüssing Cc: Ido Schimmel, roopa, bridge, netdev On Wed, 2019-08-14 at 23:34 +0300, Nikolay Aleksandrov wrote: > On 8/14/19 11:11 PM, Linus Lüssing wrote: > > On Wed, Aug 14, 2019 at 05:40:58PM +0100, Patrick Ruddy wrote: > > > The group is being joined by MLD at the L3 level but the packets are > > > not being passed up to the l3 interface becasue there is a MLD querier > > > on the network > > > > > > snippet from /proc/net/igmp6 > > > ... > > > 40 sw1 ff0200000000000000000001ff008700 1 00000004 0 > > > 40 sw1 ff020000000000000000000000000002 1 00000004 0 > > > 40 sw1 ff020000000000000000000000000001 1 0000000C 0 > > > 40 sw1 ff010000000000000000000000000001 1 00000008 0 > > > 41 lo1 ff020000000000000000000000000001 1 0000000C 0 > > > 41 lo1 ff010000000000000000000000000001 1 00000008 0 > > > 42 sw1.1 ff020000000000000000000000000006 1 00000004 0 > > > 42 sw1.1 ff020000000000000000000000000005 1 00000004 0 > > > 42 sw1.1 ff0200000000000000000001ff000000 2 00000004 0 > > > 42 sw1.1 ff0200000000000000000001ff008700 1 00000004 0 > > > 42 sw1.1 ff0200000000000000000001ff000099 1 00000004 0 > > > 42 sw1.1 ff020000000000000000000000000002 1 00000004 0 > > > 42 sw1.1 ff020000000000000000000000000001 1 0000000C 0 > > > 42 sw1.1 ff010000000000000000000000000001 1 00000008 0 > > > ... > > > > > > the bridge is sw1 and the l3 intervace is sw1.1 > > > > What kind of interface is sw1.1 exactly? Is it a VLAN or a VRF > > interface? Something else? > > > +1 > > > Could you also post the output of bridge mdb show? > > > > Regards, Linus > > > > > > PS: Also please include the bridge mailinglist in the future. > > > > Note that if you'd like to debug a host joined group currently bridge mdb show > will not dump it and if the group is host-joined only it > can even be empty. You can use my latest set (not applied yet): > https://urldefense.proofpoint.com/v2/url?u=http-3A__patchwork.ozlabs.org_project_netdev_list_-3Fseries-3D125169&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=au3D9TlUU6OvFpWOU9cuIHeNeV2fw-AOF1ZqCRqsILc&m=KsdarH0MAMMoKZ4PuvHrEC57uEluTGK-XSL4uUxu9MY&s=jyoK6VVmFh1KpKZirrtUYwq9nLy8fz-GigFFLjaLsoE&e= > > Alternatively you could monitor the mdb events, it will show up there even > today without any changes (bridge monitor mdb) and you can check if it's > getting deleted. > > Cheers, > Nik The sw1.1 interface is a .1q vlan The output of "bridge monitor mdb" is empty I can see the incoming query and the outging report on tshark: 29002 72654.887739 fe80::4041:1ff:fe00:101 → ff02::1 ICMPv6 94 Multicast Listener Query 29003 72655.502035 fe80::eac5:7aff:fe00:8700 → ff02::16 ICMPv6 194 Multicast Listener Report Message v2 debugging shows that bridge code sees the incoming query but not the outgoing report. Thanks for all the pointers - I will pursue what is happening. -pr ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-08-15 13:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20190813141804.20515-1-pruddy@vyatta.att-mail.com>
[not found] ` <20190813195341.GA27005@splinter>
[not found] ` <43ed59db-9228-9132-b9a5-31c8d1e8e9e9@cumulusnetworks.com>
[not found] ` <620d3cfbe58e3ae87ef1d5e7f2aa1588cac3e64a.camel@vyatta.att-mail.com>
2019-08-14 20:11 ` [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge Linus Lüssing
2019-08-14 20:34 ` Nikolay Aleksandrov
2019-08-15 13:36 ` Patrick Ruddy
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox