From: Niels den Otter <otter@surfnet.nl>
To: Brian Litzinger <brian@top.worldcontrol.com>,
linux-kernel@vger.kernel.org
Subject: Re: Booting 2.5.63 vs 2.4.20 I can read multicast data
Date: Wed, 5 Mar 2003 09:25:20 +0100 [thread overview]
Message-ID: <20030305082519.GA920@pangsit> (raw)
In-Reply-To: <20030305061102.GA8473@top.worldcontrol.com>
Brian,
On Tuesday, 4 March 2003, brian@worldcontrol.com wrote:
> The apps I have vlc, and mpeg2dec (with mods) cannot read multicast
> data under 2.5.63, but both work under 2.4.20.
>
> I also have some PERL tools which do multicasting stuff and they don't
> work any longer either.
>
> However, I added 'eth0' to the IO::Socket::Multicast::mcast_add()
> call and now the data is showing up.
>
> I believe this means back in the C/C++ paradigm you can't rely on
> INADDR_ANY to do the right thing. So you may have to set the specific
> IP of the interface you want your multicast data to come from in
> imr_interface.s_addr of the struct ip_mreq you pass in via setsockopt(
> sock, IPPROTO_IP, IP_ADD_MEMBERSHIP, ...
>
> I'll give this a try and let you know what I find.
But lot of multicast applications use INADDR_ANY and most don't provide
an option to choose a specific interface. So I really think that the
kernel should bind the application to an ethernet interface and not to
the loopback interface to make them work.
Can you please check if it tries to bind to the loopback interface when
using INADDR_ANY by checking 'netstat -n -g' output?
-- Niels
next prev parent reply other threads:[~2003-03-05 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 7:39 Booting 2.5.63 vs 2.4.20 I can't read multicast data brian
2003-03-04 22:39 ` Niels den Otter
2003-03-05 6:11 ` Booting 2.5.63 vs 2.4.20 I can " brian
2003-03-05 8:25 ` Niels den Otter [this message]
2003-03-06 9:49 ` brian
2003-03-06 5:06 ` [PATCH] Re: Booting 2.5.63 vs 2.4.20 I can't " James Morris
2003-03-06 4:51 ` David S. Miller
2003-03-06 9:48 ` Niels den Otter
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=20030305082519.GA920@pangsit \
--to=otter@surfnet.nl \
--cc=brian@top.worldcontrol.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