On Sat, 20 May 2023 08:24:39 +0200
john doe wrote:
> >
> > .home.arpa ? I had never heard of it until you mentioned it. You are
> > suggesting that I change every reference to localdomain to
> > .home.arpa? Implementing that change is going to be a major pain in
> > the arse.
>
> My idea was t
On 5/17/23 21:56, Charles Curley wrote:
On Wed, 17 May 2023 19:21:23 +0200
john doe wrote:
A few things, that I spotted while reading this thread and Im' not
sure if you got everything working!
Thank you. No, I don't have everything working.
- MDNS is using .local
- .localdomain should be
On Wed, 17 May 2023 19:21:23 +0200
john doe wrote:
> A few things, that I spotted while reading this thread and Im' not
> sure if you got everything working!
Thank you. No, I don't have everything working.
>
> - MDNS is using .local
> - .localdomain should be moved to .home.arpa (see RFC)! :)
On 5/15/23 16:46, Charles Curley wrote:
On Mon, 15 May 2023 07:31:29 -0600
Charles Curley wrote:
I solved that one. I had closed TCP port 9100. Opening that up on the
server got me running. However, that did not solve the problem for the
other two protocols.
Correction. That didn't solve it.
On Mon 15 May 2023 at 18:29:12 +0100, Brian wrote:
> On Mon 15 May 2023 at 16:33:42 +0100, Brian wrote:
>
> [...]
>
> > Good. The issue is solved, but how do you feel about being adventurous?
> >
> > Assuming you have deleted the three non-working queues,'lpstat -a' and
> > s-c-p should show on
Charles Curley wrote:
> On Mon, 15 May 2023 20:30:38 -0400
> Timothy M Butterworth wrote:
>
> > > I also have an ancient i386 IBM R51 running Bookworm, dragon. On
> > > dragon, using system-config-printer, I can see the printer
> > > automagically discovered. I can open up the queue window for t
On Mon, 15 May 2023 20:30:38 -0400
Timothy M Butterworth wrote:
> > I also have an ancient i386 IBM R51 running Bookworm, dragon. On
> > dragon, using system-config-printer, I can see the printer
> > automagically discovered. I can open up the queue window for the
> > printer, and request a test
On Sun, May 14, 2023 at 1:30 PM Charles Curley <
charlescur...@charlescurley.com> wrote:
> I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
> "no driver" multifunction printers. It works fine on Bullseye. I have
> the printer hooked up via USB to a server, hawk, and it prints
On 5/15/23 14:32, Charles Curley wrote:
On Mon, 15 May 2023 12:18:56 -0400
gene heskett wrote:
this is interesting Brian, but how do I adapt it to my brother
printers? All I can get by substituting the queue name M234 is
"printer or class does not exist".
Right. M234 is the name assigned pre
On Mon, 15 May 2023 12:18:56 -0400
gene heskett wrote:
> this is interesting Brian, but how do I adapt it to my brother
> printers? All I can get by substituting the queue name M234 is
> "printer or class does not exist".
Right. M234 is the name assigned previously. You get the URI(s) of
availab
On 5/15/23 07:10, Brian wrote:
On Sun 14 May 2023 at 20:57:23 -0600, Charles Curley wrote:
On Sun, 14 May 2023 23:30:25 +0100
Brian wrote:
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
We take it that dragon, hawk and the printer are network connected.
Give what you get f
On Mon 15 May 2023 at 08:24:28 -0600, Charles Curley wrote:
> On Mon, 15 May 2023 12:09:33 +0100
> Brian wrote:
[...]
> Ah, OK. So can I get rid of the three queues and print directly to the
> printer?
Indeed you can! 'lpstat -l -e' should show only the printer on the network
and a working loc
On Mon, 15 May 2023 15:42:51 +0100
Brian wrote:
> On Mon 15 May 2023 at 08:07:12 -0600, Charles Curley wrote:
>
> [...]
> [...]
> >
> > Possibly just legacy habits. I'm not accustomed to this automation.
> >
>
> Possibly. You are not alone in this. The thinking appears to be: "I
> hav
On Mon, 15 May 2023 07:31:29 -0600
Charles Curley wrote:
> I solved that one. I had closed TCP port 9100. Opening that up on the
> server got me running. However, that did not solve the problem for the
> other two protocols.
Correction. That didn't solve it. I realized that port 9100 on hawk is
On Mon 15 May 2023 at 08:07:12 -0600, Charles Curley wrote:
> On Mon, 15 May 2023 14:22:14 +0100
> Brian wrote:
> >
> > Consider: the printer can be discovered via mDNS/DNS-SD by all
> > machines on the network. ideapc does this and hasn't any difficulty
> > printing. So why set up a server when
On Mon, 15 May 2023 12:09:33 +0100
Brian wrote:
> Useful data but an aside first:
>
> The pdl= key lacks image/urf. HP claims AirPrint support for the
> device (URF=V1.4,...). It looks like you have been sold a pup. A
> firmware update?
I will look into that later today.
>
> > root@dragon:~#
On Mon, 15 May 2023 14:22:14 +0100
Brian wrote:
> > Not that I know of.
>
> Blocking port 5353 (mdns) is not unknown.
True. It is open (udp) on hawk (server) and ideapc, where I am running
shorewall (iptables). dragon has firewalld, which simply shows the
service, mdns, as open, but does not
On Sun, 14 May 2023 14:04:51 -0600
Charles Curley wrote:
> I also enabled "port 9100" printing on the printer, and went directly
> to it:
>
> socket://hpm234ethernet.localdomain:9100
>
> The printer spun its wheels, reported an error and stopped without
> printing. Nothing in the event log.
I
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 19:48:07 +0200
> john doe wrote:
>
> > On 5/14/23 19:29, Charles Curley wrote:
> > [...]
> >
> > The below, is what I would try:
> >
> > - On the non-working client, Are you restricting outbound traffic at
> >
On Sun 14 May 2023 at 20:57:23 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 23:30:25 +0100
> Brian wrote:
>
> > On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
>
>
> >
> > We take it that dragon, hawk and the printer are network connected.
> >
> > Give what you get from dra
On Sun, 14 May 2023 23:30:25 +0100
Brian wrote:
> On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
>
> We take it that dragon, hawk and the printer are network connected.
>
> Give what you get from dragon with
>
> avahi-browse -rt _ipp._tcp
> avahi-browse -rt _uscan._tcp
> d
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 19:48:07 +0200
> john doe wrote:
>
> > On 5/14/23 19:29, Charles Curley wrote:
> > [...]
> >
> > The below, is what I would try:
> >
> > - On the non-working client, Are you restricting outbound traffic at
> >
On Sun, 14 May 2023 19:48:07 +0200
john doe wrote:
> On 5/14/23 19:29, Charles Curley wrote:
> [...]
>
> The below, is what I would try:
>
> - On the non-working client, Are you restricting outbound traffic at
> all
Not that I know of.
> or for testing purposes can you disable the FW?
I
On 5/14/23 19:29, Charles Curley wrote:
I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
"no driver" multifunction printers. It works fine on Bullseye. I have
the printer hooked up via USB to a server, hawk, and it prints just
fine.
I have a client, ideapc, which sees the pr
I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
"no driver" multifunction printers. It works fine on Bullseye. I have
the printer hooked up via USB to a server, hawk, and it prints just
fine.
I have a client, ideapc, which sees the printer and prints to it just
fine.
I also
25 matches
Mail list logo
