Difference between revisions of "Mesh/Firmware/Zeroconf"
Jump to navigation
Jump to search
Jwentwistle (talk | contribs) (added details to publishing) |
Jwentwistle (talk | contribs) (switched sections for software and publishing) |
||
| 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). | ||
=Publish= | |||
To broadcast a service on the network (the long way) and load on boot: | To broadcast a service on the network (the long way) and load on boot: | ||
| Line 22: | Line 18: | ||
''Example: <code><avahi-publish -s search _http._tcp 80 scope=peoplesopen.net type=search region=oakland</code>'' | ''Example: <code><avahi-publish -s search _http._tcp 80 scope=peoplesopen.net type=search region=oakland</code>'' | ||
=Software= | |||
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). | |||
== [http://avahi.org/ avahi] == | == [http://avahi.org/ avahi] == | ||