netdev - Re: restoring IP multicast addresses when restarting the interface.

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 24 Apr 2012 19:19:34 -0300
From:	Flavio Leitner <fbl@...hat.com>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	David Miller <davem@...emloft.net>, herbert@...dor.hengli.com.au,
	netdev@...r.kernel.org
Subject: Re: restoring IP multicast addresses when restarting the interface.

On Tue, 24 Apr 2012 14:28:33 -0700
David Stevens <dlstevens@...ibm.com> wrote:

> netdev-owner@...r.kernel.org wrote on 04/24/2012 02:00:04 PM:
> 
> > From: David Miller <davem@...emloft.net>
> 
> > >> I don't see why they should disappear when the interface goes
> > >> down and then comes back up since these ultimately come from
> > >> application sockets which continue to exist after a down/up.
> > > 
> > > Yeah, but that's not how things used to work before, so my
> > > question is if the kernel should be responsible for keeping
> > > the subscription or the application.
> > > 
> > > If the admin puts down the interface and remove the module,
> > > for instance, then the multicast subscription is gone.
> > > Should the application monitor for that then?
> > > 
> > > David? Any thoughts?
> > 
> > David Stevens at IBM and Herbert at the current multicast
> > experts, so I will defer to them.
> 
> I think restoring the hardware multicast filter on device up
> is useful, desirable and not a bug. :-)

Alright, thanks everyone!
fbl
--
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