public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.4.22 multicast address problem, pcap workaround
@ 2003-09-19  8:11 Dominic Robinson
  0 siblings, 0 replies; only message in thread
From: Dominic Robinson @ 2003-09-19  8:11 UTC (permalink / raw)
  To: linux-kernel

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-09-19  8:06 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-19  8:11 2.4.22 multicast address problem, pcap workaround Dominic Robinson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox