public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] multicast routing from satillite to lan
Date: Thu, 14 Sep 2006 16:34:54 +0200	[thread overview]
Message-ID: <20060914163454.b757a097.hilse@web.de> (raw)
In-Reply-To: <2418.196.36.109.159.1158238861.squirrel@webmail.tcsn.co.za>

Hi,

On Thu, 14 Sep 2006 15:01:01 +0200 (SAST) henti@geekware.co.za wrote:

> >> mrouted doens't work with 2.4 (according to docs)
> >
> > What docs? Well, I see it being written in the ebuild, but given
> > that mrouted-3.9-beta3 is existing since June 1999, I don't think
> > it is actually true. Did you try compiling and running it?
> 
> I can't compile it since it requires 2.6 kernel headers which I cannot
> have on my system.

There's no mention of it in the tarball itself, just in the ebuild, as
I mentioned. So go and check if the sources from the tarball build
(i.e. don't use the ebuild, don't use portage at all). If you happen to
have errors while building, quote them here.

2.6 is certainly not required by all means. Back in 1999, there was no
kernel 2.6, mrouted can run even on 2.2. It *may* be that you have to
patch /usr/incluse/linux/ip_mroute.h in order to include types.h.

> I have compiled it before on a different intallation but didn't get
> any results then either.

What do you mean with "any results"? What were you expecting and what
did actually happen?

> I think my knowledge of mutlicast and routing thereof is lacking ..
> or I just don't understand how the setup should look / work

I don't have much knowledge there, either. I just understood that you
want to get mrouted running. In fact, I don't think you need it to
route multicast from one interface onto another. In order to do that,
you're probably better off using bridging (and maybe ebtables to
suppress non-multicast traffic from being bridged). As far as I can
tell from reading mrouted's documentation, its primary focus is in fact
multicast _tunneling_. In order to use that, you should have mrouted
running in more than one LAN, interconnected by a non-multicast network
(e.g. the internet). You can then route multicast packages between the
LANs. You would have to configure mrouted on both ends in order to make
them know each other. But as I said, your usage scenario most likely
doesn't need it.

-hwh
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-09-14 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 12:30 [gentoo-user] multicast routing from satillite to lan henti
2006-09-14 12:50 ` Hans-Werner Hilse
2006-09-14 13:01   ` henti
2006-09-14 14:34     ` Hans-Werner Hilse [this message]

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=20060914163454.b757a097.hilse@web.de \
    --to=hilse@web.de \
    --cc=gentoo-user@lists.gentoo.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