Difference between revisions of "Mesh/Firmware/Zeroconf"
Jwentwistle (talk | contribs) (added more programs to avahi) |
Jwentwistle (talk | contribs) (added more zero configuration details) |
||
| Line 1: | Line 1: | ||
We need a basic DNS client (and server) on the nodes. We want to use the [http://en.wikipedia.org/wiki/Service_Location_Protocol Service Location Protocol] (SLP) to implement a domain service. The domain server returns a service (or files) from a destination (typically based on an IP address), such that the domain server resolves google.com at the 74.125.224.65 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. We want to use the [http://en.wikipedia.org/wiki/Service_Location_Protocol Service Location Protocol] (SLP) to implement a domain service. The domain server returns a service (or files) from a destination (typically based on an IP address), such that the domain server resolves google.com at the 74.125.224.65 address. | ||
=Software= | =Software= | ||
Revision as of 23:29, 5 May 2014
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. We want to use the Service Location Protocol (SLP) to implement a domain service. The domain server returns a service (or files) from a destination (typically based on an IP address), such that the domain server resolves google.com at the 74.125.224.65 address.
Software
avahi
An implementation of the DNS Service Discovery and Multicast DNS specifications for Zeroconf networking. It uses D-Bus for communication between user applications and a system daemon. The daemon is used to coordinate application efforts in caching replies, necessary to minimize the traffic imposed on networks.
Avahi allows you to access computers using their hostnames. (documentation from archwiki) The services on the network can be hosted and discovered through the command line. Note: you must install nss-mdns for this to work, and have avahi-daemon.service enabled and running.
The program consists of these programs:
- avahi-browse - browse for mDNS/DNS-SD services using the daemon
- avahi-daemon - the mDNS/DNS-SD daemon
- avahi-daemon.conf - the configuration file for avahi-daemon
- avahi-discover - show a real-time graphical browse list for mDNS/DNS-SD network services
- avahi-dnsconfd - a Unicast DNS server made from mDNS/DNS-SD configuration daemon
Features:
- Embeddable mDNS stack (i.e. mDNS stack available as library)
- Ability to reflect mDNS traffic between multiple subnets
- Ability to configure a unicast DNS server automatically from server data published on the LAN
- Wide area DNS-SD support (read-only for now)
- Interface to GLIBC NSS using nss-mdns
mdns-utils
The OpenWRT package mdns-utils is actually just compiling part of Apple's mDNSResponder.
The mDNSClient utility only outputs lines to stderr (name, service type, and domain):
*** Found name = 'Foo', type = '_afpovertcp._tcp.', domain = 'local.'
The code that outputs this line is in the file mDNSResponder/mDNSPosix/Client.c in the function BrowseCallback.
Documentation
New DNS technologies on the LAN: mDNS, DNS-SD, LLMNR, PNRP
mesh DNS software: HypeDNS vs decentralized servers