public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Bishop <abishop@datacast.com>
To: linux-media@vger.kernel.org
Subject: dvbnet - Multiple PIDs on Single Network Interface Attempt
Date: Mon, 2 Dec 2013 20:03:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20131202T202014-656@post.gmane.org> (raw)

Greetings,

I'm quite stuck and am hoping I can find some guidance.  I have N PIDs
carrying MPE multicast packets that have been exposed via dvb0_N interfaces.
 It does not appear that multiple PIDs can be assigned to a single DVB
network interface via V4L/DVB API.

My goal is to have all packets (in general, multicast or not) arrive on a
single interface (i.e. sat0).  That is, a tcpdump -i sat0 will show dvb0_1,
dvb0_2, ... , dvb0_N packets.

Statically routing (smcroute) does work but, the multicast group address
isn't generally known or joined via this process.  The other process is
pre-existing software that knowns nothing of dvb0_N interfaces too.

Bridging the dvb0_N interfaces doesn't show the multicast packets on the
bridge interface (i.e. br0 via bridge-utils).  I had thought this would be
the solution.

Routing all multicast packets via route/iptables didn't seem to work either.
 From what what I gather multicast packets can't be routed 'normally'.

I have attempted some with a dynamic multicast router such as mrouted
without success.  Chance this is my limited experience in this domain, I
don't fully grasp the necessities with IGMP and such.

So, I think the question is, what would be the method you'd choose to
combine packets received from dvb0_N interfaces into a single interface? 
Can this be done multicast agnostic?  Without static routing?

Cheers,
 Alex


                 reply	other threads:[~2013-12-02 20:10 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=loom.20131202T202014-656@post.gmane.org \
    --to=abishop@datacast.com \
    --cc=linux-media@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