From: Peter Svensson <petersv@psv.nu>
To: <berthiaume_wayne@emc.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Multicast Broadcast
Date: Wed, 21 Nov 2001 22:07:57 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0111212206000.1086-100000@cheetah.psv.nu> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D00241AB03@corpusmx1.us.dg.com>
On Wed, 21 Nov 2001 berthiaume_wayne@emc.com wrote:
> I have a cluster that I wish to be able to perform a multicast
> broadcast over two backbones, primary and secondary, simultaneously. The two
> eth's are bound to the same VIP. When I perform the broadcast, it only goes
> out on eth0.
I think you need multicast routing for that to work the way you want it
to. Flooding multicast traffic between network segments is normally the
task for multicast routers since you need a routing protocol to prevent
loops etc. If you send the data on both packets a multicast router
connected to the two networks would forward a copy each way resulting in
two packets on both segments.
Peter
--
Peter Svensson ! Pgp key available by finger, fingerprint:
<petersv@psv.nu> ! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF
------------------------------------------------------------------------
Remember, Luke, your source will be with you... always...
next prev parent reply other threads:[~2001-11-21 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 20:53 Multicast Broadcast berthiaume_wayne
2001-11-21 21:07 ` Peter Svensson [this message]
2001-11-23 20:52 ` Jamie Lokier
2001-11-26 15:47 berthiaume_wayne
[not found] <93F527C91A6ED411AFE10050040665D00241AB08@corpusmx1.us.dg.com.suse.lists.linux.kernel>
2001-11-26 16:15 ` Andi Kleen
2001-11-26 16:33 berthiaume_wayne
2001-11-26 16:44 ` Andi Kleen
2001-11-29 21:29 berthiaume_wayne
2001-11-29 21:31 ` Andi Kleen
2001-11-30 21:12 berthiaume_wayne
2001-12-01 16:19 ` Andi Kleen
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=Pine.LNX.4.33.0111212206000.1086-100000@cheetah.psv.nu \
--to=petersv@psv.nu \
--cc=berthiaume_wayne@emc.com \
--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;
as well as URLs for NNTP newsgroup(s).