Content deleted Content added
m ws |
m HTTP to HTTPS for SourceForge |
||
| (One intermediate revision by one other user not shown) | |||
Line 10:
Computer networks use numeric [[network address]]es to identify communications endpoints in a network of participating devices. This is similar to the [[Plain old telephone service|telephone network]] which assigns a string of digits to identify each telephone. In modern [[networking protocol]]s, information to be transmitted is divided into a series of [[network packet]]s. Every packet contains the source and destination addresses for the transmission. [[Network router]]s examine these addresses to determine the best network path in [[Packet forwarding|forwarding the data packet]] at each step toward its destination.
Similarly to telephones being labeled with their telephone number, it was a common practice in early networks to attach an address label to networked devices. The dynamic nature of modern networks, especially residential networks in which devices are powered up only when needed, desire dynamic address assignment mechanisms that do not require user involvement for initialization and management. These systems automatically give themselves common names chosen either by the equipment manufacturer, such as a brand and model number, or chosen by users for identifying their equipment. The names and addresses are then automatically entered into a [[directory service]].
Early computer networking was built upon technologies of the telecommunications networks and thus protocols tended to fall into two groups: those intended to connect local devices into a [[local area network]] (LAN), and those intended primarily for long-distance communications. The latter [[wide area network]] (WAN) systems tended to have centralized setup, where a [[network administrator]] would manually assign addresses and names. LAN systems tended to provide more automation of these tasks so that new equipment could be added to a LAN with a minimum of operator and administrator intervention.
Line 118:
* Apple Mac OS and MS Windows have supported link-local addresses since [[Windows 98]] and [[Mac OS 8.5]] (both released in 1998).<ref name="rfc3927" /> Apple released its open-source implementation in the [[Darwin (operating system)|Darwin]] bootp package.
* [[Avahi (software)|Avahi]] contains an implementation of IPv4LL in the avahi-autoipd tool.
* Zero-Conf IP (zcip)<ref>{{Citation | url =
* [[BusyBox]] can embed a simple IPv4LL implementation.
* Stablebox,<ref>{{Citation | url = http://code.google.com/p/stablebox/ | title = Code | contribution = Stable box}}</ref> a fork from Busybox, offers a slightly modified IPv4LL implementation named llad.
Line 143:
==External links==
* {{Citation | url =
* {{Citation | url =
* {{Citation | url = http://mono-project.com/Mono.Zeroconf | title = Mono.Zeroconf | publisher = Mono project}}, a cross platform (Linux, MS Windows, Apple Mac), unified Mono/.NET library for Zeroconf, supporting both Bonjour and Avahi.
* {{Citation | url =
* {{Citation | url = http://files.multicastdns.org/draft-cheshire-dnsext-multicastdns.txt | title = Multicast DNS | last = Cheshire | first = Stuart | type = draft}}.
* {{Citation | url = http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt | publisher = DNS-SD | title = DNS-Based Service Discovery Specification | last = Cheshire | first = Stuart | type = draft}}.
| |||