Bureaucrats, oversight, Administrators
1,194
edits
Difference between revisions of "Mesh/Firmware/Zeroconf"
Jump to navigation
Jump to search
no edit summary
Jwentwistle (talk | contribs) (→Software: added avahi-publish) |
Tunabananas (talk | contribs) |
||
| (3 intermediate revisions by one other user not shown) | |||
| 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 10: | Line 8: | ||
* [http://fedorasolved.org/Members/fenris02/zero-configuration-networking-avahi avahi service examples] - a few examples of services | * [http://fedorasolved.org/Members/fenris02/zero-configuration-networking-avahi avahi service examples] - a few examples of services | ||
To | To broadcast a service (the easy way): | ||
* Use <code>avahi-publish</code> | * Use <code>avahi-publish</code> | ||
*: <code>$ avahi-publish -s <NAME> <SERVICE TYPE> <PORT></code> | *: <code>$ avahi-publish -s <NAME> <SERVICE TYPE> <PORT> <KEY VALUES></code> | ||
When you broadcast through command line you can add as many keyvalues to your service. Our service browser has the following key values: | |||
* scope - registering the serivce with a service-browser | |||
* type - category of service | |||
* region - the area where the service is hosted (to minimize latency) | |||
''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] == | ||
| Line 77: | Line 86: | ||
[http://wiki.projectmeshnet.org/DNS mesh DNS software]: HypeDNS vs decentralized servers | [http://wiki.projectmeshnet.org/DNS mesh DNS software]: HypeDNS vs decentralized servers | ||
[[Category:Mesh]] | |||