linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niels den Otter <otter@surfnet.nl>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IGMP problem with 2.5 kernels
Date: Mon, 3 Mar 2003 15:39:37 +0100	[thread overview]
Message-ID: <20030303143936.GA3068@pangsit> (raw)
In-Reply-To: <Pine.LNX.3.95.1030303090132.22417A-100000@chaos>

Richard,

On Monday,  3 March 2003, Richard B. Johnson wrote:
> Did you try to use bind() to bind your socket to a specific interface?
> Using `route` to obtain side-effects is not the correct way. The
> application needs to bind the socket to a specific interface if the
> applications requires a specific interface (which you seem to
> require). Otherwise, the first interface found will be used as the
> default. If you can't rebuild the programs, you might work- around the
> problem by modifying start-up so that your ethernet interfaces are
> started before loop-back.
> 
> You can expriment without rebooting...
> 
> Remove all routing entries first.
> route del -default xxx
> route del -net xxx, etc.
> 
> `ifconfig eth0 down`
> `ifconfig lo down`
> 
> Completely reconfigure eth0 first....
> Then configure lo.
> 
> If you don't remove all the routing entries first, you don't really
> end up with a new configuration. Something 'remembers' and the order
> of entries doesn't get changed.

I have tried both your method and also booting Linux without any
interfaces enabled, then enable eth0 and after that also lo.

When only eth0 was enabled, I got the following error from sdr:
 pangsit:~> sdr
 setsockopt - IP_ADD_MEMBERSHIP: No such device
 setsockopt - IP_ADD_MEMBERSHIP: No such device
 sd_listen: setsockopt IP_ADD_MEMBRSHIP err, addr: 224.2.127.254

I can send strace if this helps.

This is the same problem I see with other multicast applications. It
really doesn't want to bind to the ethernet interface.
  pangsit:~> ifconfig eth0
  eth0      Link encap:Ethernet  HWaddr 00:08:74:22:48:CF  
            inet addr:192.87.109.130  Bcast:192.87.109.255 Mask:255.255.255.0
            inet6 addr: 2001:610:508:109:208:74ff:fe22:48cf/64 Scope:Global
            inet6 addr: fe80::208:74ff:fe22:48cf/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:32863 errors:0 dropped:0 overruns:1 frame:0
            TX packets:150 errors:0 dropped:0 overruns:0 carrier:1
            collisions:0 txqueuelen:100 
            RX bytes:16213097 (15.4 MiB)  TX bytes:16428 (16.0 KiB)
            Interrupt:11 Base address:0xec80 

After bringing up the loopback interface again the applications binds to
this interface.


-- Niels

      reply	other threads:[~2003-03-04  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 11:32 IGMP problem with 2.5 kernels Niels den Otter
     [not found] ` <20030212215757.GA1393@pangsit>
2003-03-03 13:49   ` Niels den Otter
2003-03-03 14:13     ` Richard B. Johnson
2003-03-03 14:39       ` Niels den Otter [this message]

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=20030303143936.GA3068@pangsit \
    --to=otter@surfnet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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).