Difference between revisions of "Mesh/Firmware/Zeroconf"

From Sudo Room
Jump to navigation Jump to search
(added installation instructions for avahi)
(changed the formatting)
Line 16: Line 16:
* [http://linux.die.net/man/1/avahi-discover avahi-discover] - show a real-time graphical browse list for mDNS/DNS-SD network services
* [http://linux.die.net/man/1/avahi-discover avahi-discover] - show a real-time graphical browse list for mDNS/DNS-SD network services
* [http://linux.die.net/man/8/avahi-dnsconfd avahi-dnsconfd] - a Unicast DNS server made from mDNS/DNS-SD configuration daemon
* [http://linux.die.net/man/8/avahi-dnsconfd avahi-dnsconfd] - a Unicast DNS server made from mDNS/DNS-SD configuration daemon
* [http://linux.die.net/man/8/avahi-autoipd avahi-autoipd] - a IPv4LL network address configuration daemon


Features:  
Features:  
Line 26: Line 27:


'''Installation''' (for ubuntu)
'''Installation''' (for ubuntu)
* Obtain an IPv4LL address, <code>$ sudo avahi-autoipd -D <INTERFACE></code> (interface: wlan0, eth0)
* Obtain an IPv4LL address
*: <code>$ sudo avahi-autoipd -D <INTERFACE></code> (interface: wlan0, eth0)
* Install <code>nss-mdns</code>
* Install <code>nss-mdns</code>
* Enable and run <code>avahi-daemon</code>
* Enable and run <code>avahi-daemon</code>

Revision as of 18:51, 7 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 peoplesopen.net resolves 199.175.52.221 as the IP address.

Software

avahi

An implementation of the DNS Service Discovery and Multicast DNS specifications for zero configuration 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:

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

Installation (for ubuntu)

  • Obtain an IPv4LL address
    $ sudo avahi-autoipd -D <INTERFACE> (interface: wlan0, eth0)
  • Install nss-mdns
  • Enable and run avahi-daemon

nss-mdns

This software broadcasts mDNS queries on every interface that supports multicasts, thereby allowing name resolution by common Unix/Linux programs in the ad-hoc mDNS domain (*.local). You don't interface with this software, but you need it for an mDNS responder (avahi).

  • Install nss-mdns
    Download the compressed file
    Extract the files: $ tar -xvf <FILENAME> (example: nss-mdns.0.10.tar.gz)
    Go into the directory: $ cd <FOLDER> (example: nss-mdns.0.10)
    $ ./configure
    $ make
    $ sudo make install

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