Most Popular Articles
Not the final solution
DHCP alone didn't solve all IT's management issues as offices became more interconnected. Think back to the first networked laser printers with an Ethernet port on the back. To send a document to that printer, you needed to install a driver and tell the driver what the printer's address was before you hit print. DHCP could take care of addressing the printer when it booted up, but that won't help you find the printer when installing the driver. Plus, with DHCP being dynamic, what if the address changed? It would be a lot easier for everyone if a user could just hit print and have the computer tell the user what printers it could find.
That's where Multicast DHCP comes in. Apple calls it Bonjour. Microsoft calls it UPnP (Universal Plug and Play). Collectively, it's known as Zeroconf. The end result is that you can plug in a Vista desktop, a Macbook and a Linux Netbook on the same switch and see each other's shared files without a lengthy setup process, and all three of those machines can see the printers on the network without fuss. It just works.
If a modern home or office network can virtually set itself up, why can't an IP audio network? Using the same principles of Multicast DHCP, it can.
Three technologies come together to make everything happen: link-local addressing, Multicast DNS, and DNS Service Discovery.
Link-local addressing, also known as AutoIP, is how a device assigns itself an IP address when there isn't a DHCP server around to hand it an address when it starts up. This is needed for two scenarios: very small LANs where communication is desired without the overhead of running a DHCP server, and a safety net for devices to continue to communicate while the DHCP server is down.
When a device starts and cannot contact a DHCP server, it randomly pulls an address from the link-local pool, which is 22.214.171.124 to 126.96.36.199. Because there is no central authority keeping track of the addresses used, the machine must test to see if the address it chose is in use. If it passes the test, it announces to the world what it is and what its address is; if it fails, it picks another address at random and starts the process again. If a DHCP server joins the network, machines will then ask it for a new address and let it keep order from that point forward.
Machines that receive link-local addresses can only communicate with each other on the local network; they cannot communicate with other subnets or the Internet. This is because its link-local address is only guaranteed to be unique on the local network.
Of course, in a radio station, users prefer to look for audio with sensible names such as “ISDN 1” and “Air Monitor” instead of IP addresses such as 192.168.3.200. Plus, with addresses changing dynamically, it's critical that ISDN 1 is always ISDN 1 and not CD 1 after addresses were reassigned. Multicast DNS manages this for us because users are looking for services instead of IP addresses.
Acceptable Use Policy blog comments powered by Disqus
[an error occurred while processing this directive]
Today in Radio History
The history of radio broadcasting extends beyond the work of a few famous inventors.
Read each issue online in our Digital Edition Format in your Web browser.
EAS Information More on EAS
The feed provides feeds for all US states and territories.
Need a calendar for your computer desktop? Use one of ours.
Information from manufacturers and associations about industry news, products, technology and business announcements.
Browse Back Issues[an error occurred while processing this directive]
Also in the January Issue
- Trends in Technology: AES-X210, The "Missing Piece" of AES67?
- FCC Proposes Online Publc File Rules for Radio
- RF Engineering: Licensing AM Stations Using Method of Moments
- Field Report: Zoom H6