From: Dominic Robinson <d.robinson@videonetworks.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22 multicast address problem, pcap workaround
Date: Fri, 19 Sep 2003 09:11:54 +0100 [thread overview]
Message-ID: <3F6ABA4A.64DF0652@videonetworks.com> (raw)
Please cc to d.robinson@videonetworks.com
My source machine sends multicast packets on all the following
addresses: 230.1.1.1, 230.1.1.2 through to 230.1.1.64
My target machine (on local network, or with cross-over cable)
joins all these multicast groups, and receives packets on all
of these addresses EXCEPT 230.1.1.18 and 230.1.1.32.
However, if I run tcpdump at the same time as my program, I
find my program suddenly starts receiving on 230.1.1.[18,32]
If I kill tcpdump, my program stops receiving. It's the
"pcap_open_live()" function in tcpdump which causes this,
and as a workaround I just call it direct in my receiver.
Could this be a bug in the multicast kernel code?
NOTES:
(1) 230.1.1.1 to 230.1.64.1 and 230.1.1.1 to 230.64.1.1
has the same problem.
(2) 230.1.1.1 to 230.1.1.63 works
(3) 230.1.1.1 to 230.1.1.128 fails with slightly different
behaviour
(4) It makes no difference if I run a single program
listening on all addresses, or 64 individual programs
each listening on a single address.
Thanks and regards,
Dominic
reply other threads:[~2003-09-19 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F6ABA4A.64DF0652@videonetworks.com \
--to=d.robinson@videonetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.