All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] SLP (Service Location Protocol)
Date: Wed, 23 Jul 2014 17:02:44 +0200	[thread overview]
Message-ID: <53CFCE94.8060605@gmail.com> (raw)

Hi,

as talked about in the last OP conference call I want to make use of SLP
to discover printers in the network and especially to discover their
capabilities. Unfortunately documentation about using SLP, especially
with Ubuntu Linux, on the internet is sparse.

I want to let cups-browsed do this automatically, so that I can set up
driver-less print queues for printers with known languages (PDF,
PostScript, PCL, ...) but without polling the printer directly to not
wake up the printer from power save mode.

What I would like to know is:

1. How do I scan the network for SLP services without knowing service
names and types and without knowing which hosts in the network provide
services or are SLP directory agents?

2. In a typical SoHo network, are there SLP services or directory
agents? Are the usual SoHo routers directory agents? Or do I need to
to run an SLP server daemon on the local machine to be able to make use
of SLP?

3. How can I test my environment with command line tools?

I am very grateful for any help towards this.

   Till

             reply	other threads:[~2014-07-23 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 15:02 Till Kamppeter [this message]
2014-07-23 15:27 ` [Printing-architecture] SLP (Service Location Protocol) Pete Zannucci
2014-07-23 20:15 ` Michael Sweet
2014-07-23 20:36   ` Ira McDonald
2014-07-24  0:42     ` Michael Sweet
2014-07-24  2:10       ` Ira McDonald
2014-07-26 15:58         ` Till Kamppeter
2014-07-26 21:45           ` James Cloos
2014-07-28 13:35           ` Michael Sweet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CFCE94.8060605@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.