However, a developer selling a game for $50 doesn’t have the technical support budget to provide telephone support for people trying to configure their own “Net 10” IP network at home, so for the sake of ease-of-use, that developer also had to support AppleTalk (in the Macintosh version) and NETBIOS or IPX (in the Windows version) for people to play network games at home. For example, a game developer writing a multi-player game would usually support IP to allow game-play across the Internet. One major problem with using IP for wide-area communication and AppleTalk, NETBIOS, or something else for local communication, was that it required application developers to support multiple different protocols with different semantics, conventions, and operational models. On Windows PCs, Microsoft NETBIOS and Novell IPX provided similar ease-of-use on small networks. Now that it’s common for computers to have IEEE 802.11 (“AirPort”) networking built-in, you don’t even need cables or a hub. In the 1990s the same was true using Ethernet - if you took a group of Macs and plugged them into an Ethernet hub, you had a working AppleTalk network, using AppleTalk-over-Ethernet. Back in the 1980s if you took a group of Macs and connected them together with LocalTalk cabling, you had a working AppleTalk network, without any expert intervention, without needing to set up special servers like a DHCP server or a DNS server. Historically, AppleTalk handled this very well. Zeroconf is not limited to networks with just two hosts, but as we scale up our technologies to larger networks, we always have to be sure we haven’t forgotten the two-devices (and no DHCP server) case. That means making it possible to take two laptop computers, and connect them with a crossover Ethernet cable, and have them communicate usefully using IP, without needing a man in a white lab coat to set it all up for you. The specification for IPv4 Link-Local Addressing is complete, but the work to improve network ease-of-use (Zero Configuration Networking) continues. If you’re making a networked device today, there’s no excuse not to include IPv4 Link-Local Addressing. IPv4LL is available for Linux and for embedded operating systems. By the time the Working Group completed its work on Dynamic Configuration of IPv4 Link-Local Addresses and wrapped up in July 2003, IPv4LL was implemented and shipping in Mac OS (9 & X), Microsoft Windows (98, ME, 2000, XP, 2003), in every network printer from every major printer vendor, and in many assorted network devices from a variety of vendors. Before that it was totally solid on MacOS too.The IETF Zeroconf Working Group was chartered September 1999 and held its first official meeting at the 46 th IETF in Washington, D.C., in November 1999. I first noticed the issue in September, around the time Mojave was released. If I try to access the same speakers (a mix of Airplay 1 & 2 devices) from iOS (iPhone, AppleTV) everything works perfectly. This happens on every Mac I've tried it on, across 2 locations (a total of 5 Macs). The console then fills up with all the messages you would expect (given the network just dropped), plus a lot of these messages:Įrrorđ8:37:30.876185 +0000ĚirPlayXPCHelper endpoint_CopyProperty:1127: got error -12784/0xFFFFCE10 kCMBaseObjectError_PropertyNotFound Whether it's on WiFi or Ethernet, the network completely drops for several seconds (see video here ). I have a bizarre, ongoing problem accessing Airplay speakers from iTunes 12.9.2.5 on Mojave: every time I select an Airplay speaker from the list in iTunes it completely kills the network on the Mac.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |