This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Wed May 22 01:58:35 2024 Received: from spaans.ds9a.nl (adsl-xs4all.ds9a.nl [213.84.159.51]) by kylie.puddingonline.com (8.11.6/8.11.6) with SMTP id g8IH1kX20892 for ; Wed, 18 Sep 2002 19:01:46 +0200 Received: (qmail 19784 invoked from network); 18 Sep 2002 07:22:29 -0000 Received: from unknown (HELO spaans.ds9a.nl) (3ffe:8280:10:360:202:44ff:fe2a:a1dd) by mayo.ipv6.ds9a.nl with SMTP; 18 Sep 2002 07:22:29 -0000 Received: (qmail 720 invoked by uid 1000); 17 Sep 2002 21:06:22 -0000 Received: (maildatabase); juh Received: (qmail 1578 invoked by alias); 9 Jan 2002 18:38:34 -0000 Received: (qmail 1575 invoked from network); 9 Jan 2002 18:38:34 -0000 Received: from unknown (HELO dipsaus.ds9a.tudelft.nl) (::ffff:10.0.0.202) by spaans.ds9a.nl with SMTP; 9 Jan 2002 18:38:34 -0000 Received: (qmail 20419 invoked from network); 9 Jan 2002 18:38:13 -0000 Received: from unknown (HELO vger.kernel.org) (::ffff:12.107.208.194) by adsl-xs4all.ds9a.nl with SMTP; 9 Jan 2002 18:38:13 -0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Jan 2002 13:35:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Jan 2002 13:35:06 -0500 Received: from adsl-63-192-223-74.dsl.snfc21.pacbell.net ([63.192.223.74]:15216 "EHLO gateway.berkeley.innomedia.com") by vger.kernel.org with ESMTP id ; Wed, 9 Jan 2002 13:34:56 -0500 Received: from berkeley.innomedia.com (IDENT:root@berkeley.innomedia.com [192.168.1.5]) by gateway.berkeley.innomedia.com (8.9.1/8.9.1) with ESMTP id KAA02371 for ; Wed, 9 Jan 2002 10:35:47 -0800 Received: from berkeley.innomedia.com (IDENT:cjames@pc20.berkeley.innomedia.com [192.168.1.20]) by berkeley.innomedia.com (8.11.0/8.9.3) with ESMTP id g09JJ7t12985 for ; Wed, 9 Jan 2002 11:19:07 -0800 Message-Id: <3C3C8D4D.621A4696@berkeley.innomedia.com> Date: Wed, 09 Jan 2002 10:34:53 -0800 From: Christopher James X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.0-test1-rtl i686) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Multicast fails when interface changed Content-Type: text/plain; charset=iso-8859-1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org X-Spam-Tag: 1 Lines: 33 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by kylie.puddingonline.com id g8IH1kX20892 We are running an application that uses multicasting on Linux kernel 2.2.19. The application is connected to two network interfaces for redundancy purposes - only one interface is active at a time. When the application starts up on the first interface, the application can send and receive multicast messages. We then use ifconfig to bring down the first interface, and use ifconfig to bring up the second interface. The application works with the exception that it cannot receive multicast packets (it can still send multicast packets). It appears that the multicast information is not propagated when switching from one interface to the other. After the switch, the information in /proc/dev/mcast is still set up to work with the first interface. Also, it looks like the device list of multicast information (checked by calling ip_check_mc()) is lost when switching from the first to second interface. Is there a fix or work around to keep multicasting working when switching from one interface to another? We looked at the 2.4 kernel and it appears that it will have the same problem. Also, if there is no fix or patch, we are considering whether we should come up with a kernel patch. If we submitted a kernel patch that propagates the multicast information when the interface is changed, would it be accepted into the kernel? I am not on the list so please CC with any answers/comments. Thanks. Christopher :.˛mkabzwmb˛mbz_^nrzh&zzޗ++zfh~iz_j:+v)ߣmSy杶ii