From the blog.

Managing Digital Racket
The more I tune out, the less I miss it. But that has presented me with some complex choices for a nuanced approach to curb
Complexity – My Friend, My Enemy
Over my years of network engineering, I've learned that the fewer features you can implement while still achieving a business goal, the better. Why? Fewer

OECG – Chapter 19

576 Words. Plan about 3 minute(s) to read this.

Remember that a multicast SOURCE address will be the unicast address of the sender. A multicast DESTINATION address is a representation of a multicast group. Receivers that wish to receive traffic for a specific multicast group will all have the same multicast destination address.

Components of a Multicast IP Address

  • The first 4 bits of the first octet are always 1110.
  • That translates to a usable Class D range of 224.0.0.0 to 239.255.255.255.
  • These addresses represent groups, you should remember by now. So there is no concept of a subnet.

Well-Known Multicast Addresses

  • Permanent multicast groups – 224.0.0.0 – 224.0.1.255.
    • 224.0.0.0 – 224.0.0.255
      • Use locally only; this range is not forwarded by routers.
      • 224.0.0.1 – all multicast hosts
      • 224.0.0.2 – all mutlicast routers
      • 224.0.0.4 – DVMRP routers
      • 224.0.0.5 – all OSPF routers
      • 224.0.0.6 – OSPF designated routers
      • 224.0.0.9 – RIPv2 routers
      • 224.0.0.10 – EIGRP routers
      • 224.0.0.13 – PIM routers
      • 224.0.0.22 – IGMPv3
      • 224.0.0.25 – RGMP
    • 224.0.1.0 – 224.0.1.255
      • This range is forwarded by routers.
      • 224.0.1.39 – Cisco proprietary Auto-Rendezvous (Auto-RP) Announce
      • 224.0.1.40 – Cisco-RP Discovery
  • Source-Specific Multicast (SSM) – 232.0.0.0 – 232.255.255.255. SSM allows applications to choose what source will send them the multicast. The idea is that a recipient using SSM will end up with a better quality multicast if he is getting it from a source of a better quality. This feature relies upon IGMPv3; there’s practically no application using this yet because of how new it is.
  • GLOP – 233.0.0.0 – 233.255.255.255. RFC 2770. GLOP is not an acronym. A GLOP multicast address is one that has been registered by an ASN holder. So if you’re a private company wanting your own global multicast addresses for your applications, you can use a 256-address GLOP block. The GLOP will be formed by converting your ASN number into a 16-bit binary address. Split that 16-bit binary into 2 8 bit chunks; each 8-bit chunk will form the second and third octet of your GLOP.
  • Private (conceptually like RFC1918) – 239.0.0.0 – 239.255.255.255. You can use these locally on your network, but they aren’t supposed to bleed out onto the Internet.

Other multicast addresses not defined in the well-known ranges are considered transient ranges. Anyone is free to use them. It’s left up to good netizenship to use the address and then release it when you’re not using it anymore.

How To Convert A Multicast IP to a Multicast MAC – the quick summary – the first half (24 bits) of the MAC will always be 01-00-5E. The second half (24 bits) will always be a binary 0 + the last 23 bits of the multicast IP. More details follow.

  • Convert the IP to binary. Remember that the first 4 bits are always going to be 1110.
  • Replace the 1110 with the 6 hex digits (2 bits) 01-00-5E. Your multicast MAC will always start with 01-00-5E.
  • The next 5 bits of the binary IP translate to a single binary 0 in the MAC.
  • The last 23 bits of the binary IP translate to the last 23 bits of the binary MAC.
  • Now convert the last half of the binary MAC (the binary 0 + 23 other bits = 24 bits total) into hex.
  • Take the first half 01-00-5E with the second half you computed in the step above, and you’ve got it.

Note that this method does not always provide a unique MAC. There is a small chance that 2 applications could translate to the same MAC on the same segment, in which case the receivers would know from L3 that the multicast was not intended for them. But this is not desirable behavior and something to avoid if you are in control of multicast addressing on your network.