289
edits
Difference between revisions of "Mesh/Firmware/Zeroconf"
added service details
Jwentwistle (talk | contribs) (added a bit more details) |
Jwentwistle (talk | contribs) (added service details) |
||
| Line 1: | Line 1: | ||
We need a basic DNS client (and server) on the nodes. Zero-configuration (zeroconf) networking is software which configures a domain name server (DNS), dynamic host configuration protocol (DHCP), and other network settings with no configuration. The domain server returns a service (or files) from a destination (typically based on an IP address) | We need a basic DNS client (and server) on the nodes. Zero-configuration (zeroconf) networking is software which configures a domain name server (DNS), dynamic host configuration protocol (DHCP), and other network settings with no configuration. The domain server returns a service (or files) from a destination (typically based on an IP address). | ||
=Software= | =Software= | ||
The mDNS responder (avahi) browses and controls mDNS software (nss-mdns). | The mDNS responder (avahi) browses and controls mDNS software (nss-mdns). The mDNS responder allows you to broadcast and resolve a computer's address on the (mesh) network. When services are available on the computer, they can be accessible through the resolved name, but they aren't broadcasted until listed in the avahi services folder (etc/avahi/services). | ||
The format for broadcasting these services on the network are made by each of the service files. | |||
* [http://avahi.org/download/avahi.service.5.xml avahi service file] - the xml tags used by avahi | |||
* [http://www.dns-sd.org/ServiceTypes.html service types] - the services available for the <code><type></code> and <code><subtype></code> tags | |||
* [http://fedorasolved.org/Members/fenris02/zero-configuration-networking-avahi avahi service examples] - a few examples of services | |||
== [http://avahi.org/ avahi] == | == [http://avahi.org/ avahi] == | ||