From: Chris Wright <chris@wirex.com>
To: Christopher James <cjames@berkeley.innomedia.com>
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: Multicast fails when interface changed
Date: Mon, 14 Jan 2002 19:28:40 -0800 [thread overview]
Message-ID: <20020114192840.A23120@figure1.int.wirex.com> (raw)
In-Reply-To: <200201142016.XAA10180@ms2.inr.ac.ru> <3C4374BA.F8E26684@berkeley.innomedia.com>
In-Reply-To: <3C4374BA.F8E26684@berkeley.innomedia.com>; from cjames@berkeley.innomedia.com on Mon, Jan 14, 2002 at 04:15:54PM -0800
* Christopher James (cjames@berkeley.innomedia.com) wrote:
> It was our expectation that the switch from the first to second
> interface should work without any involvement from the application
> because the second interface is configured exactly the same as the
> first interface. After the switch, everything seems to work with the
> exception of multicasting: the multicast membership information is not
> propagated to the second interface, it stays with the first interface.
i don't think this is a valid expectation. joining a multicast group
is a device specific action. when you join, you either specify an
interface to join on (imr_interface=dev_ip_addr) or let the kernel choose
(imr_interface=INADDR_ANY). in either case, you are telling some hardware
to adjust its multicast filter and identifying that hardware by a unique
device index. as alexey mentioned, it sounds like your app has never told
the second interface that is should even care about multicast packets.
did you try joining on both interfaces? (you may find using a unique
service ip addr on each interface, and failing over an application ip
addr using aliases will help)
cheers,
-chris
next prev parent reply other threads:[~2002-01-15 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 18:34 Multicast fails when interface changed Christopher James
2002-01-09 21:10 ` Chris Wright
2002-01-11 1:06 ` Christopher James
2002-01-14 20:16 ` kuznet
2002-01-15 0:15 ` Christopher James
2002-01-15 3:28 ` Chris Wright [this message]
2002-01-15 17:41 ` kuznet
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=20020114192840.A23120@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=cjames@berkeley.innomedia.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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