linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: berthiaume_wayne@emc.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multicast Broadcast
Date: 26 Nov 2001 17:15:42 +0100	[thread overview]
Message-ID: <p73y9kth5jl.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D00241AB08@corpusmx1.us.dg.com.suse.lists.linux.kernel>
In-Reply-To: berthiaume_wayne@emc.com's message of "26 Nov 2001 16:51:37 +0100"

berthiaume_wayne@emc.com writes:

> 	One potential work-around is a patch to
> net/ipv4/igmp.c:ip_mc_join_group.
> For example:
> 
> #ifdef DUAL_MCAST_BIND
>    if(!imr->imr_ifindex) {
>       imr->ifindex=2;  /* eth0 */
>       err=ip_mc_join_group(sk, imr);
>       if (!err) {
>         imr->ifindex=3; /* eth1 */
>         err=ip_mc_join_group(sk, imr);
>       }
>       return err;
>    }
> #else
>    if(!imr->imr_ifindex)
>      in_dev = ip_mc_find_dev(imr);
> #endif
> 
> 	I'm hoping that there is another way.

It depends on what you want to do, but this "fix" is the same
equivalent to executing IP_ADD_MEMBERSHIP twice with 2 and 3 in the
imr_ifindex field (except that the later doesn't break any programs) 

-Andi

       reply	other threads:[~2001-11-26 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <93F527C91A6ED411AFE10050040665D00241AB08@corpusmx1.us.dg.com.suse.lists.linux.kernel>
2001-11-26 16:15 ` Andi Kleen [this message]
2001-11-30 21:12 Multicast Broadcast berthiaume_wayne
2001-12-01 16:19 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2001-11-29 21:29 berthiaume_wayne
2001-11-29 21:31 ` Andi Kleen
2001-11-26 16:33 berthiaume_wayne
2001-11-26 16:44 ` Andi Kleen
2001-11-26 15:47 berthiaume_wayne
2001-11-21 20:53 berthiaume_wayne
2001-11-21 21:07 ` Peter Svensson
2001-11-23 20:52 ` Jamie Lokier

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=p73y9kth5jl.fsf@amdsim2.suse.de \
    --to=ak@suse.de \
    --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).