Menu
▾
▴
Re: [Devil-Linux-discuss] Antw: Multicast Routing does not work - newstatus
|
From: <br...@ba...> - 2006-07-13 09:10:34
|
hello Alexander. There is no working mcast_forwarding support in neither kernel 2.4 nor = 2.6. If you would like to do that you have to use things like mrouted or = an IGMP Proxy. After starting mrouted the value of = /proc/sys/net/ipv4/conf/eth0/mc_forwarding will change to "1" (cheked = this on a Debian, since DL does not contain mrouted) It's not a hardware = problem. If you really need to use multicast-routing you could try to = customize your DL (see documentation on = http://www.devil-linux.org/documentation/1.2.x/ = <http://www.devil-linux.org/documentation/1.2.x/> for that). =20 Greetings, Bj=F6rn =20 =20 ________________________________ Von: dev...@li... im Auftrag von = Alexander Roos Gesendet: Do 13.07.2006 10:25 An: dev...@li... Betreff: [Devil-Linux-discuss] Antw: Multicast Routing does not work - = newstatus hello everybody! after searching the net the whole day yesterday I know a bit more about = devil-linux and multicasting. so the kernel supports multicast routing = by having the flags CONFIG_IP_MULTICAST and CONFIG_IP_MROUTE set. And I = played around with the quagga zebra demon, butt this didn't help me. I found out that the file "/proc/sys/net/ipv4/conf/eth0/mc_forwarding" = is set to "0", but I can't change this value to "1", because this file = is "r--r--r--". Trying to change the value with sysctl doesn't work = either, even not on a reboot with the wanted changes written in = "/etc/sysctl.conf". Could this be a hardware problem (wrong NICs)? so, any suggestions from your side? Greetings, Alexander Roos >>> Von: ar...@ar... An: <dev...@li...> Datum: 11.07.2006 21:57 Betreff: [Devil-Linux-discuss] Multicast Routing does not work Hello everybody! I installed a Devil-Linux router (V. 1.2.9) in our Network an need multicast-routing to run for our Novell-Clients. I googled the net for solutions and found a hint to add a static route for the multicast-net on the interface on which the novell-server resides. (http://www.informatikserver.at/index.php?option=3Dcom_content&task=3Dvie= w&id=3D10074&Itemid=3D99999999). But this did not work. On the router I can ping the multicast address 239.255.255.253 to reach the Novell Servers, on a client that resides in another ip-segment than the server I can't ping. Tcpdump shows nothing on the serverside interface. I'm wondering if the DL kernel supports multicast routing and if not how I can compile a new kernel with multicast routing support. Additionally I found that for the Service Location Protocol (SLP) which is used by the Novell client to look up the Novell servers "pim" is needed. There's something like pimd for linux, is it included in DL? If not, how can I include it? Or is obsolete, if the kernel supports multicast routing? Thanks in advance, Alexander Roos -------------------------------------------------------------------------= Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job = easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss -------------------------------------------------------------------------= Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job = easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss _________________________________________________________________________= ___ Der Inhalt dieser E-Mail ist vertraulich und ausschlie=DFlich f=FCr den = bezeichneten Adressaten (dev...@li...) = bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen = Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, = Ver=F6ffentlichung,=20 Vervielf=E4ltigung oder Wiedergabe des Inhalts dieser E-Mail = unzul=E4ssig ist. Bitte setzen Sie sich in diesem Fall mit dem Absender der E-Mail in = Verbindung (br...@ba...). |
