From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next] net: bridge: add support for IGMP/MLD stats and export them via netlink
Date: Tue, 28 Jun 2016 14:02:07 +0200 [thread overview]
Message-ID: <5772673F.8010808@cumulusnetworks.com> (raw)
In-Reply-To: <20160628110321.GA3221@otheros>
On 28/06/16 13:03, Linus Lüssing wrote:
> On Mon, Jun 27, 2016 at 08:10:48PM +0200, Nikolay Aleksandrov via Bridge wrote:
>> These are invaluable when monitoring or debugging complex multicast setups
>> with bridges.
>
> Indeed! Great patch :). Especially if people are unable to provide
> pcap files for debugging (due to whatever reason). Hopefully that
> will help with bugzilla ticket #99081, too...
>
> I know it might not quite fit into your current patch, which simply
> stores the ICMPv6 and IGMP type in the bridge private skb->cb, but
> do you think you could count and export the following two more
> things, too:
>
> * MLDv1 vs. MLDv2 querier (and IGMP accordingly)
> * Number of (potential) MLD/IGMP parse errors
> (e.g. beginning of br_multicast_ipv{4,6}_rcv():
> http://lxr.free-electrons.com/source/net/bridge/br_multicast.c?v=4.5#L1588 and
> http://lxr.free-electrons.com/source/net/bridge/br_multicast.c?v=4.5#L1634)
>
> The former would help to know how the network is expected to
> behave (for instance whether you should see MLDv2 reports at all or
> whether / how much report suppression to expect).
>
> The latter would help to spot either potential IGMP/MLD parsing bugs in
> the bridge or malformed IGMP/MLD messages send by someone else.
>
>
> Ideally, there would be per port counters again for the overall
> IPv4/IPv6 multicast traffic. That would help for multicast streams
> for instance, to easily see whether multicast counters increase
> rapidly on the ports you would expect them to. And whether snooping
> is working in general for such streames, without needing to check
> each port individually via tcpdump, for instance.
>
>
> Just some thoughts, would love to hear what you think about them.
>
> Regards, Linus
>
Hi Linus,
I think these are all reasonable and helpful things to export in addition. I will
definitely look into extending the stats with them. If this patch is accepted as-is
I'll just do it as a follow-up.
Thanks for the good suggestions!
Cheers,
Nik
WARNING: multiple messages have this Message-ID (diff)
From: Nikolay Aleksandrov via Bridge <bridge@lists.linux-foundation.org>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, davem@davemloft.net
Subject: Re: [PATCH net-next] net: bridge: add support for IGMP/MLD stats and export them via netlink
Date: Tue, 28 Jun 2016 14:02:07 +0200 [thread overview]
Message-ID: <5772673F.8010808@cumulusnetworks.com> (raw)
In-Reply-To: <20160628110321.GA3221@otheros>
On 28/06/16 13:03, Linus Lüssing wrote:
> On Mon, Jun 27, 2016 at 08:10:48PM +0200, Nikolay Aleksandrov via Bridge wrote:
>> These are invaluable when monitoring or debugging complex multicast setups
>> with bridges.
>
> Indeed! Great patch :). Especially if people are unable to provide
> pcap files for debugging (due to whatever reason). Hopefully that
> will help with bugzilla ticket #99081, too...
>
> I know it might not quite fit into your current patch, which simply
> stores the ICMPv6 and IGMP type in the bridge private skb->cb, but
> do you think you could count and export the following two more
> things, too:
>
> * MLDv1 vs. MLDv2 querier (and IGMP accordingly)
> * Number of (potential) MLD/IGMP parse errors
> (e.g. beginning of br_multicast_ipv{4,6}_rcv():
> http://lxr.free-electrons.com/source/net/bridge/br_multicast.c?v=4.5#L1588 and
> http://lxr.free-electrons.com/source/net/bridge/br_multicast.c?v=4.5#L1634)
>
> The former would help to know how the network is expected to
> behave (for instance whether you should see MLDv2 reports at all or
> whether / how much report suppression to expect).
>
> The latter would help to spot either potential IGMP/MLD parsing bugs in
> the bridge or malformed IGMP/MLD messages send by someone else.
>
>
> Ideally, there would be per port counters again for the overall
> IPv4/IPv6 multicast traffic. That would help for multicast streams
> for instance, to easily see whether multicast counters increase
> rapidly on the ports you would expect them to. And whether snooping
> is working in general for such streames, without needing to check
> each port individually via tcpdump, for instance.
>
>
> Just some thoughts, would love to hear what you think about them.
>
> Regards, Linus
>
Hi Linus,
I think these are all reasonable and helpful things to export in addition. I will
definitely look into extending the stats with them. If this patch is accepted as-is
I'll just do it as a follow-up.
Thanks for the good suggestions!
Cheers,
Nik
next prev parent reply other threads:[~2016-06-28 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 18:10 [Bridge] [PATCH net-next] net: bridge: add support for IGMP/MLD stats and export them via netlink Nikolay Aleksandrov
2016-06-27 18:10 ` Nikolay Aleksandrov
2016-06-28 11:03 ` [Bridge] " Linus Lüssing
2016-06-28 12:02 ` Nikolay Aleksandrov [this message]
2016-06-28 12:02 ` Nikolay Aleksandrov via Bridge
2016-06-28 12:48 ` [Bridge] " Nikolay Aleksandrov
2016-06-28 12:48 ` Nikolay Aleksandrov via Bridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5772673F.8010808@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.