public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Pesce <pescej@sprl.db.erau.edu>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>,
	linux-kernel@vger.kernel.org
Subject: Re: How to make Linux route multicast traffic bi-directionly between multible subnets
Date: 19 Apr 2004 17:34:01 -0400	[thread overview]
Message-ID: <1082410441.1971.27.camel@inferno> (raw)
In-Reply-To: <40843363.4070903@backtobasicsmgmt.com>


On Mon, 2004-04-19 at 16:15, Kevin P. Fleming wrote:
> Jose Luis Domingo Lopez wrote:
> 
> > So, to summarize, your best bet is to get "mrouted" or something like
> > that, and have a look at the documentation bundled. You are quite right,
> > multicast routing documentation for Linux seems to be quite old, rather
> > short, and maybe out of date.
> 
> That it is, but if you use the mrouted source and patches from the 
> Debian distribution it's fairly easy to get a basic network working. It 
> took me a few days to get it all set up, but I now have a router that 
> routes multicast between local devices and two remotes over OpenVPN 
> tunnels. Setting up mrouted was actually pretty easy, once I figured out 
> that's what I needed and got the Debian patches so it would compile.

Currently we are running Redhat 9.0 and Suse 9.0 boxes with plans to
possibly move to Suse 9.1 boxes when the Suse 9.1 comes out with 2.6
kernel support.

I've seen several sites claiming to provide the elusive "mrouted".

Can you point me to a specific location for "the" mrouted demon you are
referring to ;)

Have you played with xorp.org? It claims to be a multicast capable
router?

Thanks. 


  reply	other threads:[~2004-04-19 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 15:37 How to make Linux route multicast traffic bi-directionly between multible subnets John Pesce
2004-04-19 20:07 ` Jose Luis Domingo Lopez
2004-04-19 20:15   ` Kevin P. Fleming
2004-04-19 21:34     ` John Pesce [this message]
2004-04-19 22:16       ` Jose Luis Domingo Lopez

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=1082410441.1971.27.camel@inferno \
    --to=pescej@sprl.db.erau.edu \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@24x7linux.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