Mesh/Firmware/Zeroconf - Revision history

Tunabananas at 04:19, 28 June 2018

2018-06-28T04:19:19Z

← Older revision		Revision as of 21:19, 27 June 2018
Line 86:		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]]

Jwentwistle: /* Publish */ fixed a typo

2014-05-09T07:16:27Z

Publish: fixed a typo

← Older revision		Revision as of 00:16, 9 May 2014
Line 17:		Line 17:
	* region - the area where the service is hosted (to minimize latency)		* 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>''		''Example: <code>$ avahi-publish -s search _http._tcp 80 scope=peoplesopen.net type=search region=oakland</code>''

	=Software=		=Software=

Jwentwistle: switched sections for software and publishing

2014-05-09T07:15:22Z

switched sections for software and publishing

← Older revision		Revision as of 00:15, 9 May 2014
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=~~		=Publish=

	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).

	==Publish ~~a Service=~~=

	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] ==

Jwentwistle: added details to publishing

2014-05-09T07:14:01Z

added details to publishing

← Older revision		Revision as of 00:14, 9 May 2014
Line 3:		Line 3:
	=Software=		=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).		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).

			==Publish a Service==

	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 12:
	* [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 ~~broachast~~ a service (the easy way):		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>''

	== [http://avahi.org/ avahi] ==		== [http://avahi.org/ avahi] ==

Jwentwistle: /* Software */ added avahi-publish

2014-05-09T05:42:24Z

Software: added avahi-publish

← Older revision		Revision as of 22:42, 8 May 2014
Line 5:		Line 5:
	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 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.~~		To broadcast a service on the network (the long way) and load on boot:
	* [http://avahi.org/download/avahi.service.5.xml avahi service file] - the xml tags used by avahi		* [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://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://fedorasolved.org/Members/fenris02/zero-configuration-networking-avahi avahi service examples] - a few examples of services

			To broachast a service (the easy way):
			* Use <code>avahi-publish</code>
			*: <code>$ avahi-publish -s <NAME> <SERVICE TYPE> <PORT></code>

	== [http://avahi.org/ avahi] ==		== [http://avahi.org/ avahi] ==
Line 19:		Line 23:
	The program consists of these programs:		The program consists of these programs:
	* [http://linux.die.net/man/8/avahi-daemon avahi-daemon] - the mDNS/DNS-SD daemon		* [http://linux.die.net/man/8/avahi-daemon avahi-daemon] - the mDNS/DNS-SD daemon
	* [http://linux.die.net/man/1/avahi-browse avahi-browse] - browse for mDNS/DNS-SD services ~~using~~ the daemon		* [http://linux.die.net/man/1/avahi-browse avahi-browse] - a text-based browser for mDNS/DNS-SD services using the daemon
			* [http://linux.die.net/man/1/avahi-discover avahi-discover] - a graphical browse list for mDNS/DNS-SD network services
			* [http://linux.die.net/man/1/avahi-publish-address avahi-publish] - register an mDNS/DNS-SD service or host name or address mapping through the daemon
	* [http://linux.die.net/man/1/avahi-resolve avahi-resolve] - resolves one or more mDNS/DNS host name(s) to IP address(es) (and vice versa) using the Avahi daemon		* [http://linux.die.net/man/1/avahi-resolve avahi-resolve] - resolves one or more mDNS/DNS host name(s) to IP address(es) (and vice versa) using the Avahi daemon
	* [http://linux.die.net/man/5/avahi-daemon.conf avahi-daemon.conf] - the configuration file for avahi-daemon		* [http://linux.die.net/man/5/avahi-daemon.conf avahi-daemon.conf] - the configuration file for avahi-daemon
	* [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		* [http://linux.die.net/man/8/avahi-autoipd avahi-autoipd] - a IPv4LL network address configuration daemon

Jwentwistle: added service details

2014-05-09T04:54:09Z

added service details

← Older revision		Revision as of 21:54, 8 May 2014
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)~~. Such that peoplesopen.net resolves 199.175.52.221 as the 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] ==

Jwentwistle: added a bit more details

2014-05-08T09:06:05Z

added a bit more details

← Older revision		Revision as of 02:06, 8 May 2014
Line 2:		Line 2:

	=Software=		=Software=

			The mDNS responder (avahi) browses and controls mDNS software (nss-mdns).

	== [http://avahi.org/ avahi] ==		== [http://avahi.org/ avahi] ==

Jwentwistle: removed slp details

2014-05-08T03:40:20Z

removed slp details

← Older revision		Revision as of 20:40, 7 May 2014
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~~. 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 peoplesopen.net resolves 199.175.52.221 as the 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). Such that peoplesopen.net resolves 199.175.52.221 as the IP address.

	=Software=		=Software=

Jwentwistle: /* avahi */ fixed a tag

2014-05-08T03:32:27Z

avahi: fixed a tag

← Older revision		Revision as of 20:32, 7 May 2014
Line 32:		Line 32:
	* Install <code>nss-mdns</code>		* Install <code>nss-mdns</code>
	* Edit configuration file		* Edit configuration file
	*: <code>$ sudo vim /etc/avahi/avahi-daemon.conf		*: <code>$ sudo vim /etc/avahi/avahi-daemon.conf</code>
	* Enable and run <code>avahi-daemon</code>		* Enable and run <code>avahi-daemon</code>

Jwentwistle: /* avahi */ added configuration file for avahi-daemon.conf

2014-05-08T03:30:51Z

avahi: added configuration file for avahi-daemon.conf

← Older revision		Revision as of 20:30, 7 May 2014
Line 31:		Line 31:
	*: <code>$ sudo avahi-autoipd -D <INTERFACE></code> (interface: wlan0, eth0)		*: <code>$ sudo avahi-autoipd -D <INTERFACE></code> (interface: wlan0, eth0)
	* Install <code>nss-mdns</code>		* Install <code>nss-mdns</code>
			* Edit configuration file
			*: <code>$ sudo vim /etc/avahi/avahi-daemon.conf
	* Enable and run <code>avahi-daemon</code>		* Enable and run <code>avahi-daemon</code>