On Sun 26 Feb 2023 at 17:09:51 +0300, Reco wrote:
> Hi.
>
> On Sat, Feb 25, 2023 at 11:26:21PM +, Brian wrote:
> > > It's interesting how you bring up DHCP, yet do not mention DHCP option 9
> > > (aka "option lpr-servers" in ISC lingo).
> > > A proper implementation of DHCP options
Hi.
On Sat, Feb 25, 2023 at 11:26:21PM +, Brian wrote:
> > It's interesting how you bring up DHCP, yet do not mention DHCP option 9
> > (aka "option lpr-servers" in ISC lingo).
> > A proper implementation of DHCP options would make DNS-SD (and other
> > assorted kludges) completely
On Sat 25 Feb 2023 at 22:22:55 +0300, Reco wrote:
> On Sat, Feb 25, 2023 at 06:30:28PM +, Brian wrote:
> > On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote:
> >
> > > Hi.
> > >
> > > On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote:
> > > > On Fri, Feb 17, 2023 at 05:35:11PM
On Sat, Feb 25, 2023 at 06:30:28PM +, Brian wrote:
> On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote:
>
> > Hi.
> >
> > On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote:
> > > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> > > > Try this next time you're on site:
>
On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote:
> Hi.
>
> On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote:
> > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> > > Try this next time you're on site:
> > >
> > > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print
Hi.
On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote:
> On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> > Try this next time you're on site:
> >
> > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere
>
> This worked. I printed two copies of the
On Fri 24 Feb 2023 at 12:58:15 -0500, Greg Wooledge wrote:
> On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> > Try this next time you're on site:
> >
> > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere
>
> This worked. I printed two copies of the single-page PDF
On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> Try this next time you're on site:
>
> lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere
This worked. I printed two copies of the single-page PDF from Chrome
without any further problems.
I've gotta say, though, this
On 16/02/2023 22:41, Greg Wooledge wrote:
2) Also suggested: avahi-browse -rt _ipp._tcp
This year, the output of that command no longer contains my printer's
IP address. Last year, it did. I have no idea why this has changed.
Avahi was mentioned in the ipv6 thread, so I decided to
On Fri 17 Feb 2023 at 09:05:39 -0500, Greg Wooledge wrote:
> On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote:
[...]
> > avahi-browse -rt _ipp._tcp
> > avahi-browse -rt _uscan._tcp
> >
> > (I would find that data useful for my records).
>
> wooledg:~$ avahi-browse -rt _ipp._tcp 2>&1
Hi.
On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote:
> So the printer WORKS. It is ON THE NETWORK. I can print TEXT to it
> using port 9100.
>
> What I CANNOT do is find it in CUPS. Or avahi-browse, or driverless, or
> any of these other commands that are so allegedly
On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote:
> On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote:
>
> > wooledg:~$ cat /etc/debian_version
> > 11.6
> > wooledg:~$ lpstat -l -e
> > Canon_LBP712C_UFR_II_ permanent
> > ipp://localhost/printers/Canon_LBP712C_UFR_II_
> >
On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote:
> wooledg:~$ cat /etc/debian_version
> 11.6
> wooledg:~$ lpstat -l -e
> Canon_LBP712C_UFR_II_ permanent
> ipp://localhost/printers/Canon_LBP712C_UFR_II_
> ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/
This is a print
On Thu, Feb 16, 2023 at 03:51:47PM -0500, gene heskett wrote:
> I hate to ask the obvious, but is the net cable plugged into that printer?
See below.
On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote:
> 4) Also mentioned: port 9100.
>For grins, I did "telnet 10.76.172.100 9100"
On 2/16/23 16:09, Bob McGowan wrote:
On 2/16/23 12:01 PM, Brian wrote:
On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote:
On 2/16/23 11:14 AM, Brian wrote:
On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote:
[1]to...@tuxteam.de [2023-02-16 16:53:02] wrote:
Just for
On 2/16/23 12:01 PM, Brian wrote:
On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote:
On 2/16/23 11:14 AM, Brian wrote:
On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote:
[1]to...@tuxteam.de [2023-02-16 16:53:02] wrote:
Just for kicks: have you tried sending a PS (or
On 2/16/23 15:33, Greg Wooledge wrote:
On Thu, Feb 16, 2023 at 06:57:46PM +0200, Teemu Likonen wrote:
Here is my version which I suggest turning into a shell alias, function
or script:
avahi-browse -atrp 2>/dev/null | awk -F\; \
'$1 == "=" { printf "%-23s %-26s %5s
On Thu, Feb 16, 2023 at 06:57:46PM +0200, Teemu Likonen wrote:
> Here is my version which I suggest turning into a shell alias, function
> or script:
>
> avahi-browse -atrp 2>/dev/null | awk -F\; \
> '$1 == "=" { printf "%-23s %-26s %5s %s\n",$7,$8,$9,$5 }'
>
> It should print lines
On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote:
>On 2/16/23 11:14 AM, Brian wrote:
>
> On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote:
>
>
> [1]to...@tuxteam.de [2023-02-16 16:53:02] wrote:
>
> Just for kicks: have you tried sending a PS (or *gasp* PDF) file
> down
On 2/16/23 11:14 AM, Brian wrote:
On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote:
to...@tuxteam.de [2023-02-16 16:53:02] wrote:
Just for kicks: have you tried sending a PS (or *gasp* PDF) file
down that alley (e.g. with
On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote:
> to...@tuxteam.de [2023-02-16 16:53:02] wrote:
> > Just for kicks: have you tried sending a PS (or *gasp* PDF) file
> > down that alley (e.g. with socat)?
> >
> > For That One Form in the Year this might be just sufficient...
> >
> >
On Thu 16 Feb 2023 at 10:41:33 -0500, Greg Wooledge wrote:
[...]
> 3) Also suggested: driverless
>Here's what I get this year:
>
>wooledg:~$ driverless
>ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/
>
>That's all. And no, that's not the right printer. That's the
On Thu, Feb 16, 2023 at 11:52:21AM -0500, Stefan Monnier wrote:
> to...@tuxteam.de [2023-02-16 16:53:02] wrote:
> > Just for kicks: have you tried sending a PS (or *gasp* PDF) file
> > down that alley (e.g. with socat)?
> >
> > For That One Form in the Year this might be just sufficient...
> >
> >
* 2023-02-16 10:41:33-0500, Greg Wooledge wrote:
> 1) Someone suggested: avahi-discover -r _print-caps._tcp
>When I tried it last year, it simply hung with no visible output
>until Ctrl-C'ed.
Here is my version which I suggest turning into a shell alias, function
or script:
to...@tuxteam.de [2023-02-16 16:53:02] wrote:
> Just for kicks: have you tried sending a PS (or *gasp* PDF) file
> down that alley (e.g. with socat)?
>
> For That One Form in the Year this might be just sufficient...
>
> Hint: start with a small one :)
I don't think "a small one" can be small
On 2/16/23 08:41, Greg Wooledge wrote:
It's tax season again, so once again I am putting myself through the
utter hell that is attempting to print my city's Income Tax Forms.
(Yes, this is mandatory. No, they do not accept electronic submissions.
You must use paper and ink. Yes, they require
On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote:
[...]
> 4) Also mentioned: port 9100.
>For grins, I did "telnet 10.76.172.100 9100" and after that connected
>I typed "HELLO WORLD", then pressed Enter, then Ctrl-] q Enter to
>close the telnet session.
>
>That
It's tax season again, so once again I am putting myself through the
utter hell that is attempting to print my city's Income Tax Forms.
(Yes, this is mandatory. No, they do not accept electronic submissions.
You must use paper and ink. Yes, they require you to print your own
forms. No, they
On Mon 11 Apr 2022, at 19:23, Brian wrote:
> On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote:
>
>> On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote:
>> > BTW. I am interested in how using /usr/lib/cups/backend/snmp went.
>> > Its drawback is that not all printers provide an snmp
On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote:
> On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote:
> > BTW. I am interested in how using /usr/lib/cups/backend/snmp went.
> > Its drawback is that not all printers provide an snmp service.
>
> wooledg:~$ /usr/lib/cups/backend/snmp
On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote:
> BTW. I am interested in how using /usr/lib/cups/backend/snmp went.
> Its drawback is that not all printers provide an snmp service.
wooledg:~$ /usr/lib/cups/backend/snmp
network socket://10.76.172.120 "HP LaserJet 4250" "hp LaserJet 4250"
On Mon 11 Apr 2022 at 13:04:12 -0400, Greg Wooledge wrote:
> On Mon, Apr 11, 2022 at 05:47:07PM +0100, Brian wrote:
> > What does
> >
> >avahi-browse -rt _ipp._tcp | grep -B3 port
> >
> > give for this device?
>
> = eno1 IPv4 Canon LBP351dn (f9:7a:4a) Internet Printer
On Mon, Apr 11, 2022 at 05:47:07PM +0100, Brian wrote:
> What does
>
>avahi-browse -rt _ipp._tcp | grep -B3 port
>
> give for this device?
= eno1 IPv4 Canon LBP351dn (f9:7a:4a) Internet Printer
local
hostname = [dhcp-10-76-172-100.local]
address =
On Mon 11 Apr 2022 at 11:53:38 -0400, Greg Wooledge wrote:
> On Mon, Apr 11, 2022 at 03:40:12PM +0100, Brian wrote:
> > A third way forward:
> >
> > "implicitclass://Canon_LBP351dn_f9_7a_4a_/" is the URI for this printer.
> > Canon_LBP351dn_f9_7a_4a_ is the printer's Service Name.
> >
> >
On Mon, Apr 11, 2022 at 03:40:12PM +0100, Brian wrote:
> A third way forward:
>
> "implicitclass://Canon_LBP351dn_f9_7a_4a_/" is the URI for this printer.
> Canon_LBP351dn_f9_7a_4a_ is the printer's Service Name.
>
> avahi-resolve -n Canon_LBP351dn_f9_7a_4a_.local
>
> should give the IP
On Fri 08 Apr 2022 at 13:22:26 -0400, Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
> > On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > Unfortunately, I was not able to find ANY way to determine
On Sunday, 10 April 2022 09:54:34 EDT Brian wrote:
> On Sun 10 Apr 2022 at 09:19:43 -0400, gene heskett wrote:
> > On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> > > /usr/lib/cups/backend/snmp
> >
> > The only machine I have here that has that file installed, an rpi4,
> > does not expose
On Sun 10 Apr 2022 at 21:29:30 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote:
>
> [...]
>
> > > forbidden of trying to do network scans, but the sysadmin wants to
> > > know. I can't blame him (I'm on speaking terms with him ;-)
> >
> > Not forbidden?
>
On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote:
[...]
> > forbidden of trying to do network scans, but the sysadmin wants to
> > know. I can't blame him (I'm on speaking terms with him ;-)
>
> Not forbidden?
>
> I know a corporate network or two which would get you disconnected
> if
On Sun 10 Apr 2022 at 20:39:15 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 06:47:36PM +0100, Brian wrote:
> > On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
> >
> > > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
> > >
> > > [...]
> > >
> > > > Many
On 2022-04-10 at 14:25, Brian wrote:
> On Sun 10 Apr 2022 at 08:52:09 -0400, The Wanderer wrote:
>
>> On 2022-04-10 at 08:38, Brian wrote:
>
> [...]
>
>>> The CUPS web interface is not designed to show the IP address but
>>> to display the URI.
>>
>> This, I think, is exactly the detail
On Sun, Apr 10, 2022 at 06:47:36PM +0100, Brian wrote:
> On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
>
> > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
> >
> > [...]
> >
> > > Many printers provide an snmp (Simple Network Management Protocol)
> > > service on port
On Sun 10 Apr 2022 at 08:52:09 -0400, The Wanderer wrote:
> On 2022-04-10 at 08:38, Brian wrote:
[...]
> > The CUPS web interface is not designed to show the IP address but to
> > display the URI.
>
> This, I think, is exactly the detail that's being complained of. If CUPS
> knows the IP
On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
>
> [...]
>
> > Many printers provide an snmp (Simple Network Management Protocol)
> > service on port 9100. Check with
> >
> > nmap 10.76.172.100
>
> I know a corporate
On Sun 10 Apr 2022 at 09:31:59 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 08:54:07 EDT Brian wrote:
> > On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
> >
> > [...]
> >
> > > This, FWIW, has nothing to do with cups and printer sharing, cups
> > > does
> > > its own
On Sun 10 Apr 2022 at 10:05:09 -0400, The Wanderer wrote:
> On 2022-04-10 at 09:54, Brian wrote:
>
> > The snmp backend is not installed in the location I gave but has
> > to be moved there. Do either
> >
> > mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp
> >
> > or
> >
On 2022-04-10 at 09:54, Brian wrote:
> The snmp backend is not installed in the location I gave but has
> to be moved there. Do either
>
> mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp
>
> or
>
> dpkg-reconfigure cups
I've never taken specific action in either of
On Sun 10 Apr 2022 at 09:19:43 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> > /usr/lib/cups/backend/snmp
> The only machine I have here that has that file installed, an rpi4, does
> not expose the printers address, only:
> pi@rpi4:~ $ sudo
On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
[...]
> Many printers provide an snmp (Simple Network Management Protocol)
> service on port 9100. Check with
>
> nmap 10.76.172.100
I know a corporate network or two which would get you disconnected
if you do that :)
Then you've got to
On Sun 10 Apr 2022 at 08:10:17 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
> > On 2022-04-10 at 07:08, gene heskett wrote:
> > > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> > >> I just don't install it.
> > >
> > > And how do you
On Sunday, 10 April 2022 08:54:07 EDT Brian wrote:
> On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
>
> [...]
>
> > This, FWIW, has nothing to do with cups and printer sharing, cups
> > does
> > its own advertising. All printers here are attached to this machine,
> > marked as
On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> /usr/lib/cups/backend/snmp
The only machine I have here that has that file installed, an rpi4, does
not expose the printers address, only:
pi@rpi4:~ $ sudo /usr/lib/cups/backend/snmp
network lpd://BRN30055C8A2DC8/BINARY_P1 "Brother
On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
[...]
> This, FWIW, has nothing to do with cups and printer sharing, cups does
> its own advertising. All printers here are attached to this machine,
> marked as shareable and I can put stuff on their output trays from any
> machine
On 2022-04-10 at 08:38, Brian wrote:
> On Sat 09 Apr 2022 at 20:21:12 -0400, The Wanderer wrote:
>
>> On 2022-04-09 at 07:56, Brian wrote:
>>> It is straightforward, I don't know about obvious to all users.
>>>
>>> avahi-browse -rt _ipp._tcp
>>
>> Does that get the information from CUPS?
>>
On Sunday, 10 April 2022 08:02:32 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> > > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
> >
> > Checking all my machines,
On Fri 08 Apr 2022 at 13:22:26 -0400, Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
> > On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > Unfortunately, I was not able to find ANY way to determine
On Sat 09 Apr 2022 at 20:21:12 -0400, The Wanderer wrote:
> On 2022-04-09 at 07:56, Brian wrote:
>
> > On Fri 08 Apr 2022 at 19:45:41 -0400, The Wanderer wrote:
> >
> >> (This is probably both overly long and overly repetitive, among
> >> possibly other undesirable things, but I'm running short
On 2022-04-10 at 08:10, gene heskett wrote:
> On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
>
>> On 2022-04-10 at 07:08, gene heskett wrote:
>>> And how do you accomplish that? Its automatically installed
>>> AFAIK. And once installed, apt will not remove it without
>>> destroying
On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
> On 2022-04-10 at 07:08, gene heskett wrote:
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> >> I just don't install it.
> >
> > And how do you accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>
> > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
>
> Checking all my machines, all but one was set to 1, fixed the others and
> redid the initramfs
On Sun, Apr 10, 2022 at 07:17:42AM -0400, The Wanderer wrote:
> On 2022-04-10 at 07:08, gene heskett wrote:
>
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>
> >> I just don't install it.
> >
> > And how do you accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:08:36AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
[...]
> > be putting AVAHI_DAEMON_DETECT_LOCAL=0 into some
> > /etc/default/avahi-daemon.
>
> Then whyintarnation does it not say that in what serves as a man page?
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
Checking all my machines, all but one was set to 1, fixed the others and
redid the initramfs as it said in 2 of the 5, in that file.
Thank you for that Tomas, now
On 2022-04-10 at 07:08, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>> I just don't install it.
>
> And how do you accomplish that? Its automatically installed AFAIK.
> And once installed, apt will not remove it without destroying the
> install. rm or
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
>
> [...]
>
> > Then why, after a decade and change of bitching about it because it
> > insists on putting a 169.254.xx,yy address in ones routing table that
> > only
On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
[...]
> Then why, after a decade and change of bitching about it because it
> insists on putting a 169.254.xx,yy address in ones routing table that
> only removing avahi fixes, has it not been fixed?
This would be an IPv4
On Sunday, 10 April 2022 02:33:21 EDT to...@tuxteam.de wrote:
> On Sat, Apr 09, 2022 at 08:21:12PM -0400, The Wanderer wrote:
>
> [...]
>
> > I honestly don't know the subject very well myself, but I'd
> > definitely
> > like to know it better than I do.
> >
> > One aspect of Windows printer
On Sat, Apr 09, 2022 at 08:21:12PM -0400, The Wanderer wrote:
[...]
> I honestly don't know the subject very well myself, but I'd definitely
> like to know it better than I do.
>
> One aspect of Windows printer sharing is that it makes it possible to
> connect a printer not directly to the
* 2022-04-10 03:59:25+0100, mick crane wrote:
> On 2022-04-10 01:21, The Wanderer wrote:
>>> avahi-browse -rt _ipp._tcp
>>
>> Does that get the information from CUPS?
>
> With printer connected via other PC (CUPS print server) there is no
> output from "avahi-browse -rt _ipp._tcp"
Should be,
On 2022-04-10 01:21, The Wanderer wrote:
avahi-browse -rt _ipp._tcp
Does that get the information from CUPS?
With printer connected via other PC (CUPS print server) there is no
output from "avahi-browse -rt _ipp._tcp"
mick
--
Key ID4BFEBB31
On 2022-04-09 at 07:56, Brian wrote:
> On Fri 08 Apr 2022 at 19:45:41 -0400, The Wanderer wrote:
>
>> (This is probably both overly long and overly repetitive, among
>> possibly other undesirable things, but I'm running short on time.)
>
> So I hope you do not mind if I do not reply to every
On Fri 08 Apr 2022 at 13:22:26 -0400, Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
> > On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > Unfortunately, I was not able to find ANY way to determine
On Sat, Apr 09, 2022 at 12:56:12PM +0100, Brian wrote:
> It woould have been far, far more useful to have had the queue name on
> the card. Perhaps it can be added? Printing then becomes a two minute,
> no-fuss job:
>
> lp -d DESTINATION FILE
I'm not on site now, so I can't recall all of the
On Fri 08 Apr 2022 at 19:57:53 -0500, David Wright wrote:
> On Fri 08 Apr 2022 at 23:44:29 (+0100), Brian wrote:
> > On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
>
> > > What I understood Greg as asking about is how to get CUPS to *tell* you
> > > what the IP address it knows about
On Fri 08 Apr 2022 at 19:45:41 -0400, The Wanderer wrote:
> (This is probably both overly long and overly repetitive, among possibly
> other undesirable things, but I'm running short on time.)
So I hope you do not mind if I do not reply to every point you make.
> On 2022-04-08 at 18:44, Brian
On Sat, 2022-04-09 at 00:05 +0100, Brian wrote:
> On Fri 08 Apr 2022 at 21:07:18 +0100, Tixy wrote:
>
> > On Fri, 2022-04-08 at 20:18 +0100, Brian wrote:
> > > On Fri 08 Apr 2022 at 17:59:10 +0100, Tixy wrote:
> > >
> > > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > >
On 2022-04-08 17:10, Greg Wooledge wrote:
If you don't want to read the background information, the question is:
How is one *supposed* to figure out which autodetected printer is the
correct one, apart from trial and error?
I think you'd set up a printer on your machine with
On Fri 08 Apr 2022 at 23:44:29 (+0100), Brian wrote:
> On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
> > What I understood Greg as asking about is how to get CUPS to *tell* you
> > what the IP address it knows about for a given printer object is. That
> > doesn't seem to be an
(This is probably both overly long and overly repetitive, among possibly
other undesirable things, but I'm running short on time.)
On 2022-04-08 at 18:44, Brian wrote:
> On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
>
>> On 2022-04-08 at 15:52, Brian wrote:
>> > You didn't like my
On Sat, Apr 09, 2022 at 12:05:01AM +0100, Brian wrote:
> On Fri 08 Apr 2022 at 21:07:18 +0100, Tixy wrote:
> > I wasn't expecting a different IP address but, given Greg's experience,
>
> I think we have a differnet understanding of what The OP's experience
> was.
I knew the printer's IP address
On Fri 08 Apr 2022 at 21:07:18 +0100, Tixy wrote:
> On Fri, 2022-04-08 at 20:18 +0100, Brian wrote:
> > On Fri 08 Apr 2022 at 17:59:10 +0100, Tixy wrote:
> >
> > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > Unfortunately, I was not able to find ANY way to determine the IP
>
On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
> On 2022-04-08 at 15:52, Brian wrote:
>
> > On Fri 08 Apr 2022 at 15:22:58 -0400, Greg Wooledge wrote:
> >
> >> On Fri, Apr 08, 2022 at 08:08:22PM +0100, Brian wrote:
>
> >>> Now contact you highly paid sys admins to ask them to add a
On Fri, Apr 08, 2022 at 08:52:26PM +0100, Brian wrote:
> You didn't like my bus analogy, did you?
I don't think it's a very good analogy for this situation.
> What makes you think that knowing an IP address tells you where
> any machine of any description is located?
Because the device is (was)
On 2022-04-08 at 15:52, Brian wrote:
> On Fri 08 Apr 2022 at 15:22:58 -0400, Greg Wooledge wrote:
>
>> On Fri, Apr 08, 2022 at 08:08:22PM +0100, Brian wrote:
>>> Now contact you highly paid sys admins to ask them to add a
>>> "Location" field to whatever the server/printer is advertising.
>>
On Fri, 2022-04-08 at 20:18 +0100, Brian wrote:
> On Fri 08 Apr 2022 at 17:59:10 +0100, Tixy wrote:
>
> > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > Unfortunately, I was not able to find ANY way to determine the IP
> > > addresses of the autodetected printers that were
On Fri, Apr 08, 2022 at 08:24:00PM +0100, Brian wrote:
> avahi-browse -rt _ipp._tcp
>
> is better.
That one actually works. It completes in under 1 second, and it
includes IP addresses in its output.
Out of curiosity, I tried omitting the -r option, to try to figure out
what "resolve" means
On Fri 08 Apr 2022 at 15:22:58 -0400, Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 08:08:22PM +0100, Brian wrote:
> > On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
> > > How is one *supposed* to figure out which autodetected printer is the
> > > correct one, apart from trial and
On Fri 08 Apr 2022 at 15:30:13 (-0400), Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 08:28:31PM +0200, didier gaumet wrote:
> > CLI:
> >
> > # avahi-browse -r _print-caps._tcp
> > (from the avahi-utils package)
>
> I tried this with and without the -r (which according to the man page
> asks
On Fri 08 Apr 2022 at 15:22:58 (-0400), Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 08:08:22PM +0100, Brian wrote:
> > On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
> > > How is one *supposed* to figure out which autodetected printer is the
> > > correct one, apart from trial and
On 4/8/22 10:22, Greg Wooledge wrote:
On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
Unfortunately, I was not able to find ANY way to determine the IP
addresses of the autodetected
On Fri, Apr 08, 2022 at 08:28:31PM +0200, didier gaumet wrote:
> CLI:
>
> # avahi-browse -r _print-caps._tcp
> (from the avahi-utils package)
I tried this with and without the -r (which according to the man page
asks to "resolve services", but it doesn't say what kind of resolution
it's doing).
On Fri 08 Apr 2022 at 20:08:22 (+0100), Brian wrote:
> On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
> > How is one *supposed* to figure out which autodetected printer is the
> > correct one, apart from trial and error?
>
> Fancy an analogy?
>
> My local bus intercange has display
On Fri 08 Apr 2022 at 20:28:31 +0200, didier gaumet wrote:
> Hello Greg,
>
> Perhaps, try:
>
> GUI:
>
> avahi-discover from the avahi-discover package presents a network tree:
> you can find the IP adresses of the printers
>
> CLI:
>
> # avahi-browse -r _print-caps._tcp
> (from the
On Fri, Apr 08, 2022 at 08:08:22PM +0100, Brian wrote:
> On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
> > How is one *supposed* to figure out which autodetected printer is the
> > correct one, apart from trial and error?
> Now contact you highly paid sys admins to ask them to add a
On Fri 08 Apr 2022 at 17:59:10 +0100, Tixy wrote:
> On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > Unfortunately, I was not able to find ANY way to determine the IP
> > addresses of the autodetected printers that were presented to me.
>
> If I go to http://localhost:631/printers/
On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
[Misconceptions snipped. It would take too long to comment on and refute
every single one of them, interesting though they may be.]
> After all this, I have two final comments:
>
> 1) To whomever received two surprise printer test
Hello Greg,
Perhaps, try:
GUI:
avahi-discover from the avahi-discover package presents a network tree:
you can find the IP adresses of the printers
CLI:
# avahi-browse -r _print-caps._tcp
(from the avahi-utils package)
In my case it's sufficient to detect my network printer but I do not
On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
> On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > Unfortunately, I was not able to find ANY way to determine the IP
> > > addresses of the autodetected printers that were
On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > Unfortunately, I was not able to find ANY way to determine the IP
> > addresses of the autodetected printers that were presented to me.
>
> If I go to http://localhost:631/printers/
I
On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> Unfortunately, I was not able to find ANY way to determine the IP
> addresses of the autodetected printers that were presented to me.
If I go to http://localhost:631/printers/ and click on my printer it
shows amongst other information:
100 matches
Mail list logo
