From: Neil Horman <nhorman@tuxdriver.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: andy@greyhouse.net, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: Question: igmp behavior on interface change
Date: Wed, 18 Mar 2009 22:34:52 -0400 [thread overview]
Message-ID: <20090319023452.GA27155@localhost.localdomain> (raw)
In-Reply-To: <OF69D34007.7F9590E4-ON8825757D.005914BF-8825757D.00592A56@us.ibm.com>
On Wed, Mar 18, 2009 at 09:13:55AM -0700, David Stevens wrote:
>
>
> Neil Horman <nhorman@tuxdriver.com> wrote on 03/18/2009 07:03:53 AM:
>
>
> > I was going to look into writing some notification code for igmp to
> > detect link state chagnes and issue the reports on link up, but I wanted
> to be
> > sure there were no counter arguments first. So any and all thoughts
> > appreciated.
>
> Isn't that ip_mc_up()? Are you not getting the reports?
>
> +-DLS
Thank you! I knew there was a some integration between igmp and interface state
changes, but couldn't find it! Nevertheless, yes, thats the report I'm getting,
not so much the lack of membership reports, but the lack of multicast reception
in perpituity after a link state change. I'm still gathering data on why, so
I'm not 100% sure on the lack of the membership report, but now that you've
shown me the path between state changes and igmp updates, I can figure out more
precisely whats going on.
Thanks!
Neil
prev parent reply other threads:[~2009-03-19 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 14:03 Question: igmp behavior on interface change Neil Horman
[not found] ` <OF69D34007.7F9590E4-ON8825757D.005914BF-8825757D.00592A56@us.ibm.com>
2009-03-19 2:34 ` Neil Horman [this message]
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=20090319023452.GA27155@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox