Multicast IP Addresses
List of known Multicast address assignments within WMF's networks
This list is definitely not exhaustive. We should make an effort to find other existing multicast IPs already in use and flesh out this table!
|220.127.116.11||HTCP for cache_text (e.g. Wikis and services)||UDP port 4827|
|18.104.22.168||HTCP for cache_upload||UDP port 4827|
|22.214.171.124||HTCP for cache_maps (vhtcpd on cache_upload subscribes to this address)||UDP port 4827|
|126.96.36.199||HTCP for cache_misc (vhtcpd on cache_text subscribes to this address)||UDP port 4827|
|188.8.131.52-255||multicast tftp on installserver(s)||whole range 0-255 in last octet|
Notes about address collisions
While it's obvious that we shouldn't re-use the same exact IP address for two different purposes, there are network performance reasons to go a bit further than that. At Layer 2 (Ethernet), multicast addressing for IPv4 only has 23 bits of address space. Those 23 bits are taken from the least-significant 23 bits of the IPv4 Multicast address. In pragmatic terms, this means the first octet is irrelevant at Layer 2 (224.x.x.x == 225.x.x.x == ... 239.x.x.x), as well as the first bit of the next octet (184.108.40.206 == 220.127.116.11, 18.104.22.168 == 22.214.171.124, etc...). The aliased traffic won't reach layer 3 and beyond, but will be sent to all ethernet interfaces subscribed to aliased addresses. Therefore we should try to avoid using aliased addresses above (they should all differ in the lower 23 bits).
The same basic things apply for IPv6 multicast, but IPv6 gets 32 bits of L2 address space, which map to the least-significant 32 bits of the IPv6 Multicast address.
In both cases, we should probably also watch out for aliasing with well-known multicast addresses used for standard network functions...
See also: Multicast Address