Avahi Zeroconf - Revision history

Karellen: Updated for v20

2023-02-22T03:03:40Z

Updated for v20

← Older revision		Revision as of 03:03, 22 February 2023
Line 2:		Line 2:

	'''Avahi''' is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite, which together are branded as '''ZeroConf'''. This enables Kodi (beginning with [[Archive:XBMC v11 (Eden) changelog\|v11 "Eden"]]) to recognize media sources present on your local network without being explicitly configured for where the sources are located and what protocol is used. Compatible technology is built-in to Apple MacOS (branded as Bonjour) and installers are also available for Windows, Linux and derivates like BSD.		'''Avahi''' is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite, which together are branded as '''ZeroConf'''. This enables Kodi (beginning with [[Archive:XBMC v11 (Eden) changelog\|v11 "Eden"]]) to recognize media sources present on your local network without being explicitly configured for where the sources are located and what protocol is used. Compatible technology is built-in to Apple MacOS (branded as Bonjour) and installers are also available for Windows, Linux and derivates like BSD.



	== Installation ==		== Installation ==
Line 14:		Line 16:
	* '''{{Big\|*BSD:}}'''		* '''{{Big\|*BSD:}}'''
	** '''''FreeBSD:''''' From a terminal emulator, execute the command<blockquote><code>pkg install avahi-app avahi-libdns nss_mdns</code></blockquote>		** '''''FreeBSD:''''' From a terminal emulator, execute the command<blockquote><code>pkg install avahi-app avahi-libdns nss_mdns</code></blockquote>



	== Services supported by Kodi ==		== Services supported by Kodi ==
Line 26:		Line 30:
	<br />		<br />
	Most HTSP (e.g. [https://tvheadend.org Tvheadend]), SMB/CIFS (e.g. [https://www.samba.org Samba] v3.3+), WebDAV (e.g. [https://wiki.gnome.org/phodav PhoDAV]) and DAAP (e.g. [https://www.apple.com/itunes/ iTunes] v4.0+, [https://ampache.org/ Ampache] v3.8.0+) servers have support for ZeroConf built-in. This means that these services should be announced automatically when the Avahi daemon is also installed and enabled on the device running them, and no static service announcement configuration should be needed.		Most HTSP (e.g. [https://tvheadend.org Tvheadend]), SMB/CIFS (e.g. [https://www.samba.org Samba] v3.3+), WebDAV (e.g. [https://wiki.gnome.org/phodav PhoDAV]) and DAAP (e.g. [https://www.apple.com/itunes/ iTunes] v4.0+, [https://ampache.org/ Ampache] v3.8.0+) servers have support for ZeroConf built-in. This means that these services should be announced automatically when the Avahi daemon is also installed and enabled on the device running them, and no static service announcement configuration should be needed.



	== Static service announcements ==		== Static service announcements ==
Line 37:		Line 43:

	The section below has some sample configurations which would allow static announcements for the supported protocols. For general information according to the config files see the [https://linux.die.net/man/5/avahi.service avahi.service(5) man page].		The section below has some sample configurations which would allow static announcements for the supported protocols. For general information according to the config files see the [https://linux.die.net/man/5/avahi.service avahi.service(5) man page].


	=== Sample service configurations ===		=== Sample service configurations ===

	==== Network File System (NFS) server ====		==== Network File System (NFS) server ====
	The following configuration would announce an NFS server (operating on the default NFS port 2049) with the exported path <code>/path/to/nfsexport</code>. The Kodi ZeroConf Browser would show this entry as '''NFS server at <name of server>'''. The "%h" is a substitution variable which gets replaced by the hostname of the device providing the service. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;">nfs://<ip of server>:2049/path/to/nfsexport/</code>'''		The following configuration would announce an NFS server (operating on the default NFS port 2049) with the exported path <code>/path/to/nfsexport</code>. The Kodi ZeroConf Browser would show this entry as '''NFS server at <name of server>'''. The "%h" is a substitution variable which gets replaced by the hostname of the device providing the service. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;">nfs://<ip of server>:2049/path/to/nfsexport/</code>'''
Line 55:		Line 63:
	</service-group>		</service-group>
	</syntaxhighlight></blockquote>		</syntaxhighlight></blockquote>


	==== Web-based Distributed Authoring and Versioning (WebDAV) server ====		==== Web-based Distributed Authoring and Versioning (WebDAV) server ====
Line 73:		Line 82:
	</syntaxhighlight></blockquote>		</syntaxhighlight></blockquote>


	==== Secure File Transfer Protocol (SFTP over SSH) server ====		==== Secure File Transfer Protocol (SFTP over SSH) server ====
	The following configuration would announce an SSH server with SFTP enabled (on the default TCP port 22) with an accessible path <code>/path/to/be/accessed</code>, the user account <code>sshuser</code> and account password <code>sshpass</code>. The Kodi ZeroConf Browser would show this entry as '''SFTP on <name of server>'''. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;"><nowiki>sftp://sshuser:sshpass@<ip of server>:22/path/to/be/accessed/</nowiki></code>'''		The following configuration would announce an SSH server with SFTP enabled (on the default TCP port 22) with an accessible path <code>/path/to/be/accessed</code>, the user account <code>sshuser</code> and account password <code>sshpass</code>. The Kodi ZeroConf Browser would show this entry as '''SFTP on <name of server>'''. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;"><nowiki>sftp://sshuser:sshpass@<ip of server>:22/path/to/be/accessed/</nowiki></code>'''
Line 91:		Line 101:
	</service-group>		</service-group>
	</syntaxhighlight></blockquote>		</syntaxhighlight></blockquote>


	==== File Transfer Protocol (FTP) server ====		==== File Transfer Protocol (FTP) server ====
	The following configuration would announce an FTP server (on the default TCP port 21) with an accessible path <code>/ftppath</code>, the user account <code>ftpuser</code> and account password <code>ftppass</code>. The Kodi ZeroConf Browser would show this entry as '''FTP on <name of server>'''. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;"><nowiki>ftp:/ftpuser:ftppass@<ip of server>:21/ftppath/</nowiki></code>'''		The following configuration would announce an FTP server (on the default TCP port 21) with an accessible path <code>/ftppath</code>, the user account <code>ftpuser</code> and account password <code>ftppass</code>. The Kodi ZeroConf Browser would show this entry as '''FTP on <name of server>'''. When examining this entry, Kodi would show the available path on that service as the following URL: '''<code style="white-space: pre;"><nowiki>ftp:/ftpuser:ftppass@<ip of server>:21/ftppath/</nowiki></code>'''
Line 110:		Line 121:
	</service-group>		</service-group>
	</syntaxhighlight></blockquote>		</syntaxhighlight></blockquote>


	==== Server Message Block/Common Internet File System (SMB/CIFS) server ====		==== Server Message Block/Common Internet File System (SMB/CIFS) server ====
	:{{Note\|This Avahi service file would only be needed if running a version of Samba prior to v3.3.x, as subsequent versions provide configuration keys to manage the servers ZeroConf announcements from within its own primary configuration file '<var>smb.conf</var>'.}}		:{{Note\|This Avahi service file would only be needed if running a version of Samba prior to v3.3.x, as subsequent versions provide configuration keys to manage the servers ZeroConf announcements from within its own primary configuration file '<var>smb.conf</var>'.}}
Line 127:		Line 139:
	</service-group>		</service-group>
	</syntaxhighlight></blockquote>		</syntaxhighlight></blockquote>



	== External links ==		== External links ==
Line 132:		Line 146:


	{{updated\|19}}


			{{updated\|20}}
	[[Category:File sharing]]		[[Category:File sharing]]

Karellen: thanks for the update roguescholar

2021-09-03T00:45:48Z

thanks for the update roguescholar

← Older revision		Revision as of 00:45, 3 September 2021
Line 1:		Line 1:
			{{mininav\| [[File sharing]] }}

	'''Avahi''' is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite, which together are branded as '''ZeroConf'''. This enables Kodi (beginning with [[Archive:XBMC v11 (Eden) changelog\|v11 "Eden"]]) to recognize media sources present on your local network without being explicitly configured for where the sources are located and what protocol is used. Compatible technology is built-in to Apple MacOS (branded as Bonjour) and installers are also available for Windows, Linux and derivates like BSD.		'''Avahi''' is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite, which together are branded as '''ZeroConf'''. This enables Kodi (beginning with [[Archive:XBMC v11 (Eden) changelog\|v11 "Eden"]]) to recognize media sources present on your local network without being explicitly configured for where the sources are located and what protocol is used. Compatible technology is built-in to Apple MacOS (branded as Bonjour) and installers are also available for Windows, Linux and derivates like BSD.

Line 130:		Line 132:


			{{updated\|19}}
	[[Category:File sharing]]		[[Category:File sharing]]

RogueScholar: Rewrite entire page and fix dead end status

2021-08-11T13:03:25Z

Rewrite entire page and fix dead end status

Show changes

Davu at 23:03, 18 August 2020

2020-08-18T23:03:48Z

← Older revision		Revision as of 23:03, 18 August 2020
Line 11:		Line 11:
	== Services supported by Kodi ==		== Services supported by Kodi ==

	~~XBMC~~ can receive service announcements for the following protocols: samba, FTP, HTSP, WebDAV, NFS and SFTP (ssh server).		Kodi can receive service announcements for the following protocols: samba, FTP, HTSP, WebDAV, NFS and SFTP (ssh server).

	Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.		Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.
Line 87:		Line 87:

	==== SAMBA service - pre 3.3.x (/etc/avahi/services/smb.service) ====		==== SAMBA service - pre 3.3.x (/etc/avahi/services/smb.service) ====
	The following configuration would announce a SAMBA server (on default port ~~139~~). Kodi Zeroconf browser would show this entry as ''SAMBA on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available shares on that samba server.		The following configuration would announce a SAMBA server (on default port 445). Kodi Zeroconf browser would show this entry as ''SAMBA on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available shares on that samba server.

	<?xml version="1.0" standalone='no'?>		<?xml version="1.0" standalone='no'?>
Line 95:		Line 95:
	<service>		<service>
	<type>_smb._tcp</type>		<type>_smb._tcp</type>
	<port>~~139~~</port>		<port>445</port>
	</service>		</service>
	</service-group>		</service-group>

Karellen at 09:21, 20 July 2020

2020-07-20T09:21:11Z

← Older revision		Revision as of 09:21, 20 July 2020
Line 11:		Line 11:
	== Services supported by Kodi ==		== Services supported by Kodi ==

	XBMC can receive service announcements for the following protocols~~. [[Windows File Sharing (SMB/SAMBA/CIFS)\|~~samba]], ~~[[Media Source~~ FTP~~\|FTP]]~~, HTSP, [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).		XBMC can receive service announcements for the following protocols: samba, FTP, HTSP, WebDAV, NFS and SFTP (ssh server).

	Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.		Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.
Line 99:		Line 99:
	</service-group>		</service-group>

	~~[[Category:Manual]]~~
	[[Category:File sharing]]		[[Category:File sharing]]

Karellen at 22:19, 16 June 2020

2020-06-16T22:19:18Z

← Older revision		Revision as of 22:19, 16 June 2020
Line 11:		Line 11:
	== Services supported by Kodi ==		== Services supported by Kodi ==

	XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], ~~[[HTS Tvheadend\|~~HTSP]], [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).		XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], HTSP, [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).

	Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.		Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.

NattyG93: Removed unnecessary (and ungrammatical) article.

2016-11-13T02:46:48Z

Removed unnecessary (and ungrammatical) article.

← Older revision		Revision as of 02:46, 13 November 2016
Line 13:		Line 13:
	XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], [[HTS Tvheadend\|HTSP]], [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).		XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], [[HTS Tvheadend\|HTSP]], [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).

	~~The most~~ HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.		Most HTSP, samba (minimum version 3.3.x), WEBDAV and iTunes (DAAP) servers are supposed to have support for zeroconf built in. This means that these services should be announcent automatically when avahi is installed. No static service announcement configuration should be needed then.

	== Static service announcement ==		== Static service announcement ==

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:26:16Z

Bot: Automated text replacement (- XBMC + Kodi )

Sleinen: /* NFS service (/etc/avahi/services/nfs.service) */ The default NFS port is 2049, not 2149. I'm pretty sure that this is meant here.

2014-11-28T17:30:27Z

NFS service (/etc/avahi/services/nfs.service): The default NFS port is 2049, not 2149. I'm pretty sure that this is meant here.

← Older revision		Revision as of 17:30, 28 November 2014
Line 26:		Line 26:

	==== NFS service (/etc/avahi/services/nfs.service) ====		==== NFS service (/etc/avahi/services/nfs.service) ====
	The following configuration would announce a NFS server (with the nfs default port ~~2149~~) with the exported path ''/path/to/nfsexport''. XBMC Zeroconf browser would show this entry as ''NFS server at <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - XBMC would show the available path on that service with ''/path/to/nfsexport''. Clicking on that one would generate the following url: '''nfs://<ip of server>:2049/path/to/nfsexport/'''		The following configuration would announce a NFS server (with the nfs default port 2049) with the exported path ''/path/to/nfsexport''. XBMC Zeroconf browser would show this entry as ''NFS server at <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - XBMC would show the available path on that service with ''/path/to/nfsexport''. Clicking on that one would generate the following url: '''nfs://<ip of server>:2049/path/to/nfsexport/'''


Line 35:		Line 35:
	<service>		<service>
	<type>_nfs._tcp</type>		<type>_nfs._tcp</type>
	<port>~~2149~~</port>		<port>2049</port>
	<txt-record>path=/path/to/nfsexport</txt-record>		<txt-record>path=/path/to/nfsexport</txt-record>
	</service>		</service>

NedBot: Robot: Changing Category:XBMC Manual to Category:Manual

2014-11-17T21:17:18Z

Robot: Changing Category:XBMC Manual to Category:Manual

← Older revision		Revision as of 21:17, 17 November 2014
Line 99:		Line 99:
	</service-group>		</service-group>

	[[Category:~~XBMC~~ Manual]]		[[Category:Manual]]
	[[Category:File sharing]]		[[Category:File sharing]]

← Older revision		Revision as of 08:26, 4 May 2015
Line 2:		Line 2:
	== General ==		== General ==
	=== What is Avahi (Zeroconf) ===		=== What is Avahi (Zeroconf) ===
	<section begin="intro"/>Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables ~~XBMC~~ to recognize media sources inside your local network without knowing where the sources are located and what protocol is used. Compatible technology is found in Apple MacOS X (branded Bonjour and sometimes Zeroconf). Avahi is available for linux and derivates (BSD) afaik.<section end="intro"/>		<section begin="intro"/>Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables Kodi to recognize media sources inside your local network without knowing where the sources are located and what protocol is used. Compatible technology is found in Apple MacOS X (branded Bonjour and sometimes Zeroconf). Avahi is available for linux and derivates (BSD) afaik.<section end="intro"/>

	For more details have a look at [http://www.avahi.org avahi.org].		For more details have a look at [http://www.avahi.org avahi.org].
Line 9:		Line 9:
	Since the Installation of Avahi depends on the used operating system please realise that this page only covers the configuration of static service announcements (for services which don't have avahi support included). For installation instructions just use a www search engine with the keywords "install avahi on <enter operting system here".		Since the Installation of Avahi depends on the used operating system please realise that this page only covers the configuration of static service announcements (for services which don't have avahi support included). For installation instructions just use a www search engine with the keywords "install avahi on <enter operting system here".

	== Services supported by ~~XBMC~~ ==		== Services supported by Kodi ==

	XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], [[HTS Tvheadend\|HTSP]], [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).		XBMC can receive service announcements for the following protocols. [[Windows File Sharing (SMB/SAMBA/CIFS)\|samba]], [[Media Source FTP\|FTP]], [[HTS Tvheadend\|HTSP]], [[WebDAV]], [[NFS]] and [[SFTP]] (ssh server).
Line 17:		Line 17:
	== Static service announcement ==		== Static service announcement ==
	=== What about it? ===		=== What about it? ===
	For services which don't support zeroconf registration there is an easy possibility to make avahi announce them. For each service which should be announced there has to be a configuration file. Normally these files should reside in /etc/avahi/services and end with the file extension ".service". The ~~XBMC~~ zeroconf browser supports txt-records. This means that it can parse some of the official DNS-SD keys (see [http://www.dns-sd.org/ServiceTypes.html ServiceTypes] under "Defined TXT keys"). ~~XBMC~~ parses the "path","u"(username) and "p"(password) keys. This allows to specify a complete service including the path and account information for accessing it.		For services which don't support zeroconf registration there is an easy possibility to make avahi announce them. For each service which should be announced there has to be a configuration file. Normally these files should reside in /etc/avahi/services and end with the file extension ".service". The Kodi zeroconf browser supports txt-records. This means that it can parse some of the official DNS-SD keys (see [http://www.dns-sd.org/ServiceTypes.html ServiceTypes] under "Defined TXT keys"). Kodi parses the "path","u"(username) and "p"(password) keys. This allows to specify a complete service including the path and account information for accessing it.

	'''The Avahi daemon has to run on the same server which hosts the services which should be announced.'''		'''The Avahi daemon has to run on the same server which hosts the services which should be announced.'''
Line 26:		Line 26:

	==== NFS service (/etc/avahi/services/nfs.service) ====		==== NFS service (/etc/avahi/services/nfs.service) ====
	The following configuration would announce a NFS server (with the nfs default port 2049) with the exported path ''/path/to/nfsexport''. ~~XBMC~~ Zeroconf browser would show this entry as ''NFS server at <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - ~~XBMC~~ would show the available path on that service with ''/path/to/nfsexport''. Clicking on that one would generate the following url: '''nfs://<ip of server>:2049/path/to/nfsexport/'''		The following configuration would announce a NFS server (with the nfs default port 2049) with the exported path ''/path/to/nfsexport''. Kodi Zeroconf browser would show this entry as ''NFS server at <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available path on that service with ''/path/to/nfsexport''. Clicking on that one would generate the following url: '''nfs://<ip of server>:2049/path/to/nfsexport/'''


Line 41:		Line 41:

	==== WEBDAV service (/etc/avahi/services/webdav.service) ====		==== WEBDAV service (/etc/avahi/services/webdav.service) ====
	The following configuration would announce a WebDAV server (e.x. apache at port 80) with the accessible path ''/webdav/path''. ~~XBMC~~ Zeroconf browser would show this entry as ''WebDav on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - ~~XBMC~~ would show the available path on that service with ''/webdav/path''. Clicking on that one would generate the following url: '''dav://<ip of server>:80/webdav/path/'''.		The following configuration would announce a WebDAV server (e.x. apache at port 80) with the accessible path ''/webdav/path''. Kodi Zeroconf browser would show this entry as ''WebDav on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available path on that service with ''/webdav/path''. Clicking on that one would generate the following url: '''dav://<ip of server>:80/webdav/path/'''.

	<?xml version="1.0" standalone='no'?>		<?xml version="1.0" standalone='no'?>
Line 55:		Line 55:

	==== SFTP service (/etc/avahi/services/sftp.service) ====		==== SFTP service (/etc/avahi/services/sftp.service) ====
	The following configuration would announce a sftp/ssh server (on default port 22) with the accessible path ''/path/to/be/accessed'', the user ''sshuser'' and the password ''sshpass''. ~~XBMC~~ Zeroconf browser would show this entry as ''SFTP on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - ~~XBMC~~ would show the available path on that service with ''/path/to/be/accessed''. Clicking on that one would generate the following url: '''sftp://sshuser:sshpass@<ip of server>:22/path/to/be/accessed/'''.		The following configuration would announce a sftp/ssh server (on default port 22) with the accessible path ''/path/to/be/accessed'', the user ''sshuser'' and the password ''sshpass''. Kodi Zeroconf browser would show this entry as ''SFTP on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available path on that service with ''/path/to/be/accessed''. Clicking on that one would generate the following url: '''sftp://sshuser:sshpass@<ip of server>:22/path/to/be/accessed/'''.

	<?xml version="1.0" standalone='no'?>		<?xml version="1.0" standalone='no'?>
Line 71:		Line 71:

	==== FTP service (/etc/avahi/services/ftp.service) ====		==== FTP service (/etc/avahi/services/ftp.service) ====
	The following configuration would announce a FTP server (on default port 21) with the accessible path ''/ftppath'', the user ''ftpuser'' and the password ''ftppass''. ~~XBMC~~ Zeroconf browser would show this entry as ''FTP on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - ~~XBMC~~ would show the available path on that service with ''/ftppath''. Clicking on that one would generate the following url: '''ftp:/ftpuser:ftppass@<ip of server>:21/ftppath/'''.		The following configuration would announce a FTP server (on default port 21) with the accessible path ''/ftppath'', the user ''ftpuser'' and the password ''ftppass''. Kodi Zeroconf browser would show this entry as ''FTP on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available path on that service with ''/ftppath''. Clicking on that one would generate the following url: '''ftp:/ftpuser:ftppass@<ip of server>:21/ftppath/'''.

	<?xml version="1.0" standalone='no'?>		<?xml version="1.0" standalone='no'?>
Line 87:		Line 87:

	==== SAMBA service - pre 3.3.x (/etc/avahi/services/smb.service) ====		==== SAMBA service - pre 3.3.x (/etc/avahi/services/smb.service) ====
	The following configuration would announce a SAMBA server (on default port 139). ~~XBMC~~ Zeroconf browser would show this entry as ''SAMBA on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - ~~XBMC~~ would show the available shares on that samba server.		The following configuration would announce a SAMBA server (on default port 139). Kodi Zeroconf browser would show this entry as ''SAMBA on <name of server>''. The "%h" gets substituted by the hostname of the server. When clicking this entry - Kodi would show the available shares on that samba server.

	<?xml version="1.0" standalone='no'?>		<?xml version="1.0" standalone='no'?>