On 02/23/2017 12:47 AM, Seth Arnold wrote:
On Wed, Feb 22, 2017 at 04:42:46PM -0300, Till Kamppeter wrote:
So it looks like that we need to work with an extra interface (dummy0 with
IPv6) and find a way to let Avahi broadcast the interface's own host name or
Would you mind changing the name to
On Wed, Feb 22, 2017 at 04:42:46PM -0300, Till Kamppeter wrote:
> So it looks like that we need to work with an extra interface (dummy0 with
> IPv6) and find a way to let Avahi broadcast the interface's own host name or
Would you mind changing the name to something that would more clearly
reflect
On 01/21/2017 09:56 AM, TJ wrote:
On 16/01/17 18:05, Till Kamppeter wrote:
In the beginning I used localhost:6 which makes polling capabilities
and status, printing, and web interface work, but the printer could not
be Avahi-broadcasted and so CUPS and cups-browsed could not discover it.
P
On 01/21/2017 09:56 AM, TJ wrote:
On 16/01/17 18:05, Till Kamppeter wrote:
In the beginning I used localhost:6 which makes polling capabilities
and status, printing, and web interface work, but the printer could not
be Avahi-broadcasted and so CUPS and cups-browsed could not discover it.
P
On 16/01/17 18:05, Till Kamppeter wrote:
> In the beginning I used localhost:6 which makes polling capabilities
> and status, printing, and web interface work, but the printer could not
> be Avahi-broadcasted and so CUPS and cups-browsed could not discover it.
>
Possibly not the ideal solution
tl;dr: Creating an emulated remote machine representing a USB printer as
it was a network printer, without VM with it's own kernel
Hi,
I am developing the ippusbxd daemon to support IPP-over-USB printers:
https://github.com/tillkamppeter/ippusbxd/
Modern network printers use IPP (Internet Pri