How do I choose a multicast address for my application's use?

Question

Hi,

How should I choose an IPv4 multicast address for my application's use? I may need more than one (a whole range perhaps ultimately) but just want to avoid conflicts with other applications.

• Packets will be entirely contained within an administrative domain, probably a LAN
• If several independent instances of my application are in use on the same network, they could each use their own multicast address - but if they don't, they will be able to coexist anyway, they'll just have a small amount of overhead ignoring each others' packets.
• My packets already contain a "magic number" to avoid problems
• I will be checking the originator address (which I know can be spoofed of course), TTL and other things to try to prevent unexpected packets mucking things up.

Ideas please :)

Currently I've just allocated an arbitrary one from the "local use" space, 239.255.42.99

Answer 1

If it is just for internal use then why not just externalize the address range as configuration and continue to use internal use.

The Internet Assigned Numbers Authority is responsible for assigning IP addresses. They do not allocate to ISPs or individuals but on they have http://www.iana.org/numbers/">information where to get numbers allocated depending on your region.

Answer 2

As already suggested, allow the range to be configured. But taking that further, don't require configuration. You pick the range and allow configuration to override if necessary.

You should have some logic in your application to handle foreign packets, to alert the user, through logs, or some other mechanism, that your application has detected multicast packets from another app, with instructions on how to change the configuration.

If it turns out that there is a conflict, play those numbers in the lottery!

Answer 3

Have you seen this ?

MADCAP

Answer 4

It seems you've already found http://www.iana.org/assignments/multicast-addresses, so you've done the right thing by picking an address from the 239.255/16 range.

As those ranges are entirely for site-local use it's no ones else's business which particular address you pick, but you may need to coordinate with the network manager (assuming that's not you) to pick an alternate address pool.

As others have suggested, just make sure there's an easy way to change the address just in case it does conflict with another address on the local LAN.

If the multiple applications issue becomes a problem, provide a (locally) well-known multicast address which the applications can talk to which will issue unique local-scope IP addresses for clients' use.

Answer 5

ZMAAP is a zero-configuration alternative to MADCAP. I doubt there are any public source implementations of it. If you find one, then I'd like to know about it.