Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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

like image 798
MarkR Avatar asked Oct 25 '08 10:10

MarkR


People also ask

What multicast address can I use?

So, the full range of multicast addresses is from 224.0. 0.0 to 239.255. 255.255. Since multicast addresses represent a group of IP devices (sometimes called a host group) they can only be used as the destination of a datagram; never the source.

How are multicast addresses assigned?

The address range is divided into blocks each assigned a specific purpose or behavior. Addresses in the range of 224.0. 0.0 to 224.0. 0.255 are individually assigned by IANA and designated for multicasting on the local subnetwork only.

What is the default multicast address?

The multicast addresses are in the range 224.0. 0.0 through 239.255. 255.255.


2 Answers

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.

like image 126
Alnitak Avatar answered Nov 03 '22 22:11

Alnitak


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!

like image 35
Corey Trager Avatar answered Nov 03 '22 22:11

Corey Trager