Hi, On Thu, 14 Sep 2006 15:01:01 +0200 (SAST) [EMAIL PROTECTED] 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
