On Feb 10, 2008 2:23 AM, Carlo Marcelo Arenas Belon
<[EMAIL PROTECTED]> wrote:
> On Fri, Feb 08, 2008 at 06:24:05PM -0800, Ben Rockwood wrote:
> > I then found that I could use multicast in a non-multicast
> > environment on Solaris and just let it all become broadcast.  So now I
> > have gmond's on each subnet working together via broadcast, however I
> > need to "bridge" the gmond's together.
>
> you are abusing the application and the network to send a UDP packet to a
> broadcast IP, it will be better to fix the source of your environmental
> limitations instead of hacking around them.

Actually, there is some precedent for this (ab)use of
unicast->broadcast traffic, and it can be really useful on occasion,
and if use carefully.  I know that Samba, specifically, can can do
this *if* configured to do so.  Quoting from the smb.conf(5) man page:

      remote announce (G)
         This option allows you to setup nmbd(8)to periodically
announce itself to arbitrary IP
         addresses with an arbitrary workgroup name.
        [...]
         For example:

         remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
         [...]
         The  IP  addresses  you choose would normally be the
broadcast addresses of the remote
         networks, but can also be the IP addresses of known browse
masters  if  your  network
         config is that stable.

However, in this case it is probably best to just have gmond poll one
host in each subnet, instead of trying to send traffic between the
subnets.

-- 
Jesse Becker
GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0  2720 0083 0931 9A2B 06A2

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general

Reply via email to