usenet@nlm-mcs.arpa (usenet news poster) (02/24/90)
Would someone please outline how to perform a directed broadcast-- that is, a broadcast to a net located one or more hops away? Are there severe limitations or restrictions on the use of directed broadcasts, such that directed broadcasts are impractical? e.g., are routers usually configured to block off-site broadcast packets? Any source code examples would be greatly appreciated. BTW: the reason for asking this question (aside from my naivety) is that I am investigating providing network services on machines whose network identities may change (although the subnet probably wouldn't); and I'd like to avoid having to update potentially thousands of distributed copies of client applications when these changes do occur. I'd be very interested if perhaps y'all have some better suggestions than directed broadcasts. Warren Gish National Center for Biotechnology Information National Library of Medicine gish@ncbi.nlm.nih.gov
mogul@decwrl.dec.com (Jeffrey Mogul) (02/28/90)
In article <11545@nlm-mcs.arpa> gish@host.UUCP () writes:
Would someone please outline how to perform a directed broadcast--
that is, a broadcast to a net located one or more hops away?
Are there severe limitations or restrictions on the use of directed
broadcasts, such that directed broadcasts are impractical? e.g.,
are routers usually configured to block off-site broadcast packets?
Well, you might look at RFC922:
Mogul, J.C. Broadcasting Internet datagrams in the presence of subnets.
1984 October; 12 p. (24832 bytes)
On the other hand, I think it is nearly universally agreed that if
broadcasting is evil, then directed broadcasting is evil compounded.
I.e., I wouldn't suggest using them (and as far as I know, few
routers implement directed broadcasting).
BTW: the reason for asking this question (aside from my naivety) is
that I am investigating providing network services on machines whose
network identities may change (although the subnet probably wouldn't);
and I'd like to avoid having to update potentially thousands of
distributed copies of client applications when these changes do occur.
I'd be very interested if perhaps y'all have some better suggestions
than directed broadcasts.
Sounds like you want to use multicasting (see RFC1112 and RFC1075).
But you might have to wait a while for that to be widely implemented.
Or maybe you should just use the Domain Name System (DNS) to provide some
late binding (i.e., assign a nickname to the host that is currently
providing the service, and require the clients to look up that nickname
whenever they want to use the service). You can do it today if your
software uses DNS (and if it doesn't, fix that first).
-Jeff