| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090319023452.GA27155@localhost.localdomain> Date: Wed, 18 Mar 2009 22:34:52 -0400 From: Neil Horman <nhorman@...driver.com> To: David Stevens <dlstevens@...ibm.com> Cc: andy@...yhouse.net, davem@...emloft.net, netdev@...r.kernel.org Subject: Re: Question: igmp behavior on interface change On Wed, Mar 18, 2009 at 09:13:55AM -0700, David Stevens wrote: > > > Neil Horman <nhorman@...driver.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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists