I'm afraid I have to report that this did not work for me. I have spent several days trying to get multicast traffic to route between two interfaces and have had no success.
I have exactly the configuration you outline below-- I was unable to get A to see any ganglia traffic from b[1..n] or c[1..n]. A could only see B and C data if the gmond on those machines used the interface connecting to A. If B and C used the interfaces connecting to b[1..n] and c[1..n], then B could only see itself and b[1..n]. C could only see itself and c[1..n]. B and C never saw A in this mode either. I am running kernel 2.4.9 with multicast routing enabled in the kernel and did the echo thing shown below but got no joy. Chris On Friday (04/26/2002 at 11:44AM -0700), matt massie wrote: > > i THINK i might have a trick that can be helpful for some of your > configurations but i'm not sure. i'm explaining it here in case someone > out there wants to try this out. > > on linux, you can enable ip forwarding with a simple command > # echo "1" > /proc/sys/net/ipv4/ip_forward > > altering this value on your multi-homed frontend will cause it to forward > on ganglia multicast traffic to other interfaces. > > if your configuration is like this > > A > / \ > B C > b1 c1 > b2 c2 > .. .. > bn cn > > if you enable ip forwarding on B and C AND the private IP space on cluster > b and c are different, then it might be possible to monitoring everything > from A. > > if someone has the time to try this out, can you report on what you found? > > we also need to be sensitive the security ramifications of ip forwarding. > http://www.linuxsecurity.com/articles/network_security_article-4528.html > > hope it works. > > -matt > > > _______________________________________________ > Ganglia-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ganglia-general -- Chris Elmquist mailto:[EMAIL PROTECTED] Unlimited Scale, Inc. http://www.unlimitedscale.com St. Paul, MN
