ACC SHELL
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 22. SLP Services in the Network</title><link rel="stylesheet" href="susebooks.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Documentation"><link rel="up" href="part.reference.services.html" title="Part V. Services"><link rel="prev" href="cha.basicnet.html" title="Chapter 21. Basic Networking"><link rel="next" href="cha.dns.html" title="Chapter 23. The Domain Name System"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header" border="0" class="bctable"><tr><td width="80%"><div class="breadcrumbs"><p><a href="index.html"> Documentation</a><span class="breadcrumbs-sep"> > </span><a href="book.opensuse.reference.html">Reference</a><span class="breadcrumbs-sep"> > </span><a href="part.reference.services.html">Services</a><span class="breadcrumbs-sep"> > </span><strong><a accesskey="p" title="Chapter 21. Basic Networking" href="cha.basicnet.html"><span>◀</span></a> <a accesskey="n" title="Chapter 23. The Domain Name System" href="cha.dns.html"><span>▶</span></a></strong></p></div></td></tr></table></div><div class="chapter" title="Chapter 22. SLP Services in the Network"><div class="titlepage"><div><div><h2 class="title"><a name="cha.slp"></a>Chapter 22. SLP Services in the Network<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#cha.slp">¶</a></span></h2></div></div></div><div class="toc"><p><b>Contents</b></p><dl><dt><span class="sect1"><a href="cha.slp.html#sec.slp.openslpinst">22.1. Installation</a></span></dt><dt><span class="sect1"><a href="cha.slp.html#sec.slp.sl.act">22.2. Activating SLP</a></span></dt><dt><span class="sect1"><a href="cha.slp.html#sec.slp.sl.fend">22.3. SLP Front-Ends in openSUSE</a></span></dt><dt><span class="sect1"><a href="cha.slp.html#sec.slp.sl.inst">22.4. Installation over SLP</a></span></dt><dt><span class="sect1"><a href="cha.slp.html#sec.slp.sl.reg">22.5. Providing Services via SLP</a></span></dt><dt><span class="sect1"><a href="cha.slp.html#sec.slp.info">22.6. For More Information</a></span></dt></dl></div><a class="indexterm" name="id484186"></a><a class="indexterm" name="id484194"></a><a class="indexterm" name="id484203"></a><a class="indexterm" name="id484208"></a><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>
The <span class="emphasis"><em>service location protocol</em></span> (SLP) was developed to
simplify the configuration of networked clients within a local network.
To configure a network client, including all required services, the
administrator traditionally needs detailed knowledge of the servers
available in the network. SLP makes the availability of selected services
known to all clients in the local network. Applications that support SLP
can use the information distributed and be configured automatically.
</p></div><p>
openSUSE® supports installation using installation sources provided
with SLP and contains many system services with integrated support for
SLP. YaST and Konqueror both have appropriate front-ends for SLP. You
can use SLP to provide networked clients with central functions, such as
an installation server, file server, or print server on your system.
</p><div class="important"><table border="0" cellpadding="3" cellspacing="0" width="100%" summary="Important: SLP Support in "><tr class="head"><td width="32"><img alt="[Important]" src="admon/important.png"></td><th align="left">SLP Support in openSUSE</th></tr><tr><td colspan="2" align="left" valign="top"><p>
Services that offer SLP support include cupsd, rsyncd, ypserv, openldap2,
ksysguardd, saned, kdm, vnc, login, smpppd, rpasswd
, postfix, and sshd (via fish).
</p></td></tr></table></div><div class="sect1" title="22.1. Installation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.openslpinst"></a>22.1. Installation<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.openslpinst">¶</a></span></h2></div></div></div><p>
All packages necessary to use SLP services are installed by default.
However, if you want to provide services via SLP, check that the
<code class="systemitem">openslp-server</code> package is installed. For SLP
daemon server configuration install the
<code class="systemitem">yast2-slp-server</code> package.
</p></div><div class="sect1" title="22.2. Activating SLP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.sl.act"></a>22.2. Activating SLP<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.sl.act">¶</a></span></h2></div></div></div><p>
slpd must run on your system to offer services with SLP. If the machine
should only operate as client, and does not offer services, it is not
necessary to run slpd. Like most system services in openSUSE, the
slpd daemon is controlled by means of a separate <span class="command"><strong>init</strong></span>
script. After the installation, the daemon is inactive by default. To
activate it temporarily, run
<span class="command"><strong>rcslpd <code class="option">start</code></strong></span> as
<code class="systemitem">root</code> or
<span class="command"><strong>rcslpd <code class="option">stop</code></strong></span> to stop it. Perform
a restart or status check with <code class="option">restart</code> or
<code class="option">status</code>. If slpd should be always active after booting,
enable slpd in YaST <span class="guimenu">System</span>+<span class="guimenu">System Services (Runlevel)</span> or run the
<span class="command"><strong>insserv</strong></span> <code class="option">slpd</code> command as
<code class="systemitem">root</code>.
</p></div><div class="sect1" title="22.3. SLP Front-Ends in"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.sl.fend"></a>22.3. SLP Front-Ends in openSUSE<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.sl.fend">¶</a></span></h2></div></div></div><p>
To find services provided via SLP in your network, use an SLP front-end
such as <span class="command"><strong>slptool</strong></span> (<code class="systemitem">openslp</code>
package) or YaST:
</p><div class="variablelist"><dl><dt><span class="term">slptool</span></dt><dd><p>
<a class="indexterm" name="id484394"></a> <a class="indexterm" name="id484405"></a> slptool is a command line program that can be used to
announce SLP inquiries in the network or announce proprietary
services. <span class="command"><strong>slptool</strong></span> <code class="option">--help</code>
lists all available options and functions. For example, to find all
time servers that announce themselves in the current network, run the
command:
</p><pre class="screen">slptool findsrvs service:ntp</pre></dd><dt><span class="term">YaST</span></dt><dd><p>
<a class="indexterm" name="id484445"></a> YaST also provides an SLP browser. However, this
browser is not available from the YaST Control Center. To start it,
run <span class="command"><strong>yast2 slp</strong></span> as
<code class="systemitem">root</code> user. Click on a
<span class="guimenu">Service Type</span> on the lefthand side to get more
information about a service.
</p></dd></dl></div></div><div class="sect1" title="22.4. Installation over SLP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.sl.inst"></a>22.4. Installation over SLP<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.sl.inst">¶</a></span></h2></div></div></div><p>
If you have an installation server with openSUSE installation media
within your network, this can be registered and offered with SLP. For
details, see <a class="xref" href="cha.deployment.remoteinst.html#sec.deployment.remoteinst.instserver" title="1.2. Setting Up the Server Holding the Installation Sources">Section 1.2, “Setting Up the Server Holding the Installation Sources”</a>. If
SLP installation is selected, linuxrc starts an SLP inquiry after the
system has booted from the selected boot medium and displays the sources
found.
</p></div><div class="sect1" title="22.5. Providing Services via SLP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.sl.reg"></a>22.5. Providing Services via SLP<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.sl.reg">¶</a></span></h2></div></div></div><a class="indexterm" name="id484513"></a><a class="indexterm" name="id484522"></a><p>
Many applications in openSUSE have integrated SLP support through
the use of the <code class="literal">libslp</code> library. If a service has not
been compiled with SLP support, use one of the following methods to make
it available via SLP:
</p><div class="variablelist"><dl><dt><span class="term">Static Registration with <code class="filename">/etc/slp.reg.d</code>
</span></dt><dd><p>
Create a separate registration file for each new service. This is an
example for registering a scanner service:
</p><pre class="screen">## Register a saned service on this system
## en means english language
## 65535 disables the timeout, so the service registration does
## not need refreshes
service:scanner.sane://$HOSTNAME:6566,en,65535
watch-port-tcp=6566
description=SANE scanner daemon</pre><p>
The most important line in this file is the <span class="emphasis"><em>service
URL</em></span>, which begins with <code class="literal">service:</code>. This
contains the service type (<code class="literal">scanner.sane</code>) and the
address under which the service is available on the server.
<em class="replaceable"><code>$HOSTNAME</code></em> is automatically replaced with
the full hostname. The name of the TCP port on which the relevant
service can be found follows, separated by a colon. Then enter the
language in which the service should appear and the duration of
registration in seconds. These should be separated from the service
URL by commas. Set the value for the duration of registration between
<code class="literal">0</code> and <code class="literal">65535</code>.
<code class="literal">0</code> prevents registration. <code class="literal">65535</code>
removes all restrictions.
</p><p>
The registration file also contains the two variables
<code class="systemitem">watch-port-tcp</code> and
<code class="systemitem">description</code>.
<code class="systemitem">watch-port-tcp</code> links the SLP service
announcement to whether the relevant service is active by having slpd
check the status of the service. The second variable contains a more
precise description of the service that is displayed in suitable
browsers.
</p></dd><dt><span class="term">Static Registration with <code class="filename">/etc/slp.reg</code>
</span></dt><dd><p>
The only difference between this method and the procedure with
<code class="filename">/etc/slp.reg.d</code> is that all services are grouped
within a central file.
</p></dd><dt><span class="term">Dynamic Registration with <span class="command"><strong>slptool</strong></span>
</span></dt><dd><p>
If a service needs to be registered dynamically without the need of
configuration files, use the slptool command line utility. The same
utility can also be used to deregister an existing service offering
without restarting slpd.
</p></dd></dl></div></div><div class="sect1" title="22.6. For More Information"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.slp.info"></a>22.6. For More Information<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.slp.info">¶</a></span></h2></div></div></div><div class="variablelist"><dl><dt><span class="term">RFC 2608, 2609, 2610</span></dt><dd><p>
RFC 2608 generally deals with the definition of SLP. RFC 2609 deals
with the syntax of the service URLs used in greater detail and RFC
2610 deals with DHCP via SLP.
</p></dd><dt><span class="term"><a class="ulink" href="http://www.openslp.org" target="_top">http://www.openslp.org</a>
</span></dt><dd><p>
The home page of the OpenSLP project.
</p></dd><dt><span class="term"><code class="filename">/usr/share/doc/packages/openslp</code>
</span></dt><dd><p>
This directory contains the documentation for SLP coming with the
<code class="systemitem">openslp-server</code> package, including a
<code class="filename">README.SuSE</code> containing the openSUSE details,
the RFCs, and two introductory HTML documents. Programmers who want to
use the SLP functions find more information in the
<span class="emphasis"><em>Programmers Guide</em></span> that is included in the
<code class="systemitem">openslp-devel</code> package.
</p></dd></dl></div></div></div><div class="navfooter"><table width="100%" summary="Navigation footer" border="0" class="bctable"><tr><td width="80%"><div class="breadcrumbs"><p><a href="index.html"> Documentation</a><span class="breadcrumbs-sep"> > </span><a href="book.opensuse.reference.html">Reference</a><span class="breadcrumbs-sep"> > </span><a href="part.reference.services.html">Services</a><span class="breadcrumbs-sep"> > </span><strong><a accesskey="p" title="Chapter 21. Basic Networking" href="cha.basicnet.html"><span>◀</span></a> <a accesskey="n" title="Chapter 23. The Domain Name System" href="cha.dns.html"><span>▶</span></a></strong></p></div></td></tr></table></div></body></html>
ACC SHELL 2018