-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I noticed I have installed a long list of hp utilities: cer@Telcontar:~> hp-[TAB][TAB] hp-align hp-pkservice hp-check hp-plugin hp-clean hp-pqdiag hp-colorcal hp-print hp-config_usb_printer hp-printsettings hp-devicesettings hp-probe hp-diagnose_plugin hp-query hp-diagnose_queues hp-sendfax hp-doctor hp-setup hp-fab hp-systray hp-faxsetup hp-testpage hp-firmware hp-timedate hp-info hp-toolbox hp-levels hp-uninstall hp-linefeedcal hp-unload hp-logcapture hp-upgrade hp-makecopies hp-wificonfig hp-makeuri cer@Telcontar:~> hp- But they all fail: cer@Telcontar:~> hp-info HP Linux Imaging and Printing System (ver. 3.21.10) Device Information Utility ver. 5.2 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. error: No device found that support this feature. cer@Telcontar:~> hp-toolbox gives some information as to why. It opens a GUI, then a popup says "no Installed HP Devices Found" - see photo: https://susepaste.org/21567804 Now, I don't want to install a new printer, mine is installed and working. but notice what it says at the bottom: Note: Only devices installed with the hp: or hpfac: CUPS backend will appear in the HP Device Manager. What I have in CUPS is: Description: HP Color LaserJet CP1510 Series Postscript (recommended) Location: Red local Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: socket://bilbo.valinor:9100 Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided Indeed, if I allow hp-toolbox to create a printer ((after dropping the firewall), it does so and it appears in all tools. And cups shows a new printer: Description: Created using hptoolbox Location: Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: hp:/net/HP_Color_LaserJet_CP1515n?ip=192.168.1.3 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided Curious. - -- Cheers Carlos E. R. (from 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYih3Phwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVaZgAn0uOqQTj7HGV49ZZsfJB B5tWX7TUAJ0eXD+7GCV1CatpdE/h+lB/R0v03A== =/KhL -----END PGP SIGNATURE-----
* Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I noticed I have installed a long list of hp utilities:
cer@Telcontar:~> hp-[TAB][TAB] hp-align hp-pkservice hp-check hp-plugin hp-clean hp-pqdiag hp-colorcal hp-print hp-config_usb_printer hp-printsettings hp-devicesettings hp-probe hp-diagnose_plugin hp-query hp-diagnose_queues hp-sendfax hp-doctor hp-setup hp-fab hp-systray hp-faxsetup hp-testpage hp-firmware hp-timedate hp-info hp-toolbox hp-levels hp-uninstall hp-linefeedcal hp-unload hp-logcapture hp-upgrade hp-makecopies hp-wificonfig hp-makeuri cer@Telcontar:~> hp-
But they all fail:
cer@Telcontar:~> hp-info
HP Linux Imaging and Printing System (ver. 3.21.10) Device Information Utility ver. 5.2
Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
error: No device found that support this feature. cer@Telcontar:~>
hp-toolbox gives some information as to why. It opens a GUI, then a popup says "no Installed HP Devices Found" - see photo: https://susepaste.org/21567804
Now, I don't want to install a new printer, mine is installed and working. but notice what it says at the bottom:
Note: Only devices installed with the hp: or hpfac: CUPS backend will appear in the HP Device Manager.
so you installed the printer using cups or yast and not hp-setup but expect the hplip applications to recognize and admin your printer????
What I have in CUPS is:
Description: HP Color LaserJet CP1510 Series Postscript (recommended) Location: Red local Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: socket://bilbo.valinor:9100 Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided
Indeed, if I allow hp-toolbox to create a printer ((after dropping the firewall), it does so and it appears in all tools.
And cups shows a new printer:
Description: Created using hptoolbox Location: Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: hp:/net/HP_Color_LaserJet_CP1515n?ip=192.168.1.3 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided
Curious.
sounds like yast does not conform to the expectations of hplip which from my experience, *just works*. I have two printers installed using hplip/hp-setup and both appear in yast. maybe you need to file a bug report against yast. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 2022-03-09 18:28, Patrick Shanahan wrote:
* Carlos E. R. <> [03-09-22 11:40]:
Hi,
I noticed I have installed a long list of hp utilities:
cer@Telcontar:~> hp-[TAB][TAB] hp-align hp-pkservice hp-check hp-plugin hp-clean hp-pqdiag hp-colorcal hp-print hp-config_usb_printer hp-printsettings hp-devicesettings hp-probe hp-diagnose_plugin hp-query hp-diagnose_queues hp-sendfax hp-doctor hp-setup hp-fab hp-systray hp-faxsetup hp-testpage hp-firmware hp-timedate hp-info hp-toolbox hp-levels hp-uninstall hp-linefeedcal hp-unload hp-logcapture hp-upgrade hp-makecopies hp-wificonfig hp-makeuri cer@Telcontar:~> hp-
But they all fail:
cer@Telcontar:~> hp-info
HP Linux Imaging and Printing System (ver. 3.21.10) Device Information Utility ver. 5.2
Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
error: No device found that support this feature. cer@Telcontar:~>
hp-toolbox gives some information as to why. It opens a GUI, then a popup says "no Installed HP Devices Found" - see photo: https://susepaste.org/21567804
Now, I don't want to install a new printer, mine is installed and working. but notice what it says at the bottom:
Note: Only devices installed with the hp: or hpfac: CUPS backend will appear in the HP Device Manager.
so you installed the printer using cups or yast and not hp-setup but expect the hplip applications to recognize and admin your printer????
YaST said it was using hplip, and that could be over a decade ago for me to remember many details.
What I have in CUPS is:
Description: HP Color LaserJet CP1510 Series Postscript (recommended) Location: Red local Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: socket://bilbo.valinor:9100 Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided
Indeed, if I allow hp-toolbox to create a printer ((after dropping the firewall), it does so and it appears in all tools.
And cups shows a new printer:
Description: Created using hptoolbox Location: Driver: HP Color LaserJet CP1510 Series Postscript (recommended) (color) Connection: hp:/net/HP_Color_LaserJet_CP1515n?ip=192.168.1.3 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided
Curious.
sounds like yast does not conform to the expectations of hplip which from my experience, *just works*.
I have two printers installed using hplip/hp-setup and both appear in yast.
maybe you need to file a bug report against yast.
Maybe. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
Hi,
I noticed I have installed a long list of hp utilities:
They are probably all from hplip.
But they all fail:
.. to identify any HP device. -- Per Jessen, Zürich (5.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
On 2022-03-09 21:26, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
I noticed I have installed a long list of hp utilities:
They are probably all from hplip.
yes: cer@Telcontar:~> wrpm hp-info hplip-3.21.10-4.3.1.x86_64 cer@Telcontar:~>
But they all fail:
.. to identify any HP device.
Yes. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
But they all fail:
.. to identify any HP device.
Yes.
Good. On my network certainly :-) -- Per Jessen, Zürich (4.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 2022-03-09 03:45:34 Carlos E. R. wrote:
|Hi, | |I noticed I have installed a long list of hp utilities: | |cer@Telcontar:~> hp-[TAB][TAB] |hp-align hp-pkservice |hp-check hp-plugin |hp-clean hp-pqdiag |hp-colorcal hp-print |hp-config_usb_printer hp-printsettings |hp-devicesettings hp-probe |hp-diagnose_plugin hp-query |hp-diagnose_queues hp-sendfax |hp-doctor hp-setup |hp-fab hp-systray |hp-faxsetup hp-testpage |hp-firmware hp-timedate |hp-info hp-toolbox |hp-levels hp-uninstall |hp-linefeedcal hp-unload |hp-logcapture hp-upgrade |hp-makecopies hp-wificonfig |hp-makeuri |cer@Telcontar:~> hp- | |But they all fail: | |cer@Telcontar:~> hp-info | |HP Linux Imaging and Printing System (ver. 3.21.10) |Device Information Utility ver. 5.2 | |Copyright (c) 2001-18 HP Development Company, LP |This software comes with ABSOLUTELY NO WARRANTY. |This is free software, and you are welcome to distribute it |under certain conditions. See COPYING file for more details. | |error: No device found that support this feature. |cer@Telcontar:~> | | |hp-toolbox gives some information as to why. It opens a GUI, then a popup |says "no Installed HP Devices Found" - see photo: | https://susepaste.org/21567804 | |Now, I don't want to install a new printer, mine is installed and working. |but notice what it says at the bottom: | | Note: Only devices installed with the hp: or hpfac: CUPS backend will | appear in the HP Device Manager. | |What I have in CUPS is: | | Description: HP Color LaserJet CP1510 Series Postscript (recommended) | Location: Red local | Driver: HP Color LaserJet CP1510 Series Postscript (recommended) | (color) Connection: socket://bilbo.valinor:9100 | Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided | | |Indeed, if I allow hp-toolbox to create a printer ((after dropping the |firewall), it does so and it appears in all tools. | |And cups shows a new printer: | | Description: Created using hptoolbox | Location: | Driver: HP Color LaserJet CP1510 Series Postscript (recommended) | (color) Connection: hp:/net/HP_Color_LaserJet_CP1515n?ip=192.168.1.3 | Defaults: job-sheets=none, none media=na_letter_8.5x11in | sides=one-sided | | |Curious.
Why do you have to drop your firewall? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.3 x86_64
* Carlos E. R.
On 2022-03-12 09:47, J Leslie Turriff wrote:
On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500 just open those on the firewall, and/or close when finished scanning. fwiw: I have never had to do this for my hp printer scanning over a network. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]:
On 2022-03-12 09:47, J Leslie Turriff wrote:
On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
* Carlos E. R.
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]:
On 2022-03-12 09:47, J Leslie Turriff wrote:
On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address) I *assign* static ip addresses to all my printers so I can know which I want to print to and from where. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]:
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]:
On 2022-03-12 09:47, J Leslie Turriff wrote:
On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I. But the hp tools I cited in the initial post want to scan and find the printer. Even Yast does the same. You can let it scan, which fails normally, or tell it the IP directly which works. I always tell the address directly. Dropping the firewall in a computer on the LAN which is somehow protected from outside by a router is no big deal. After all, there are several machines there that have no firewall at all, and run obsolete firmware - the printer itself, for instance. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
* Carlos E. R.
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]:
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]:
On 2022-03-12 09:47, J Leslie Turriff wrote:
On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I.
But the hp tools I cited in the initial post want to scan and find the printer.
no, they do not. I use the same tools and you can. hp-setup in "Device Discovery", select "Show Advanced Options" and "Manual Discovery" enter the requested IP Address -> Next and it has been this way for many years.
Even Yast does the same. You can let it scan, which fails normally, or tell it the IP directly which works. I always tell the address directly.
Dropping the firewall in a computer on the LAN which is somehow protected from outside by a router is no big deal. After all, there are several machines there that have no firewall at all, and run obsolete firmware - the printer itself, for instance.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 2022-03-12 19:26, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 13:06]:
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]:
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]:
On 2022-03-12 09:47, J Leslie Turriff wrote: > On 2022-03-09 03:45:34 Carlos E. R. wrote:
...
> > Why do you have to drop your firewall?
Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I.
But the hp tools I cited in the initial post want to scan and find the printer.
no, they do not. I use the same tools and you can. hp-setup in "Device Discovery", select "Show Advanced Options" and "Manual Discovery" enter the requested IP Address -> Next
and it has been this way for many years.
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found. Now, drop the firewall and repeat: printer is found. That's HP functionality to scan the network and find printers. Yes, I am aware that you can bypass it and use the "advanced" method to enter the IP manually. The culprit appears to be this: <0.4> 2022-03-12T19:37:08.034831+01:00 Telcontar kernel - - - [96076.796132] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49215 PROTO=UDP SPT=427 DPT=36525 LEN=342 The destination port on the computer (36525) is random, so I do not know what port to open. svrloc 427/udp # Server Location [Veizades] A second try produces: <0.4> 2022-03-12T19:41:47.618524+01:00 Telcontar kernel - - - [96356.379741] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49256 PROTO=UDP SPT=427 DPT=36772 LEN=342 Different port. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
* Carlos E. R.
On 2022-03-12 19:26, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 13:06]:
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]:
On 2022-03-12 14:22, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 04:00]: > On 2022-03-12 09:47, J Leslie Turriff wrote: > > On 2022-03-09 03:45:34 Carlos E. R. wrote: > > ... > > > > > Why do you have to drop your firewall? > > Printer scanning doesn't work otherwise.
hp scanning uses ports: UDP 427 TCP 9220,9500
just open those on the firewall, and/or close when finished scanning.
fwiw: I have never had to do this for my hp printer scanning over a network.
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I.
But the hp tools I cited in the initial post want to scan and find the printer.
no, they do not. I use the same tools and you can. hp-setup in "Device Discovery", select "Show Advanced Options" and "Manual Discovery" enter the requested IP Address -> Next and it has been this way for many years.
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers. Yes, I am aware that you can bypass it and use the "advanced" method to enter the IP manually.
The culprit appears to be this:
<0.4> 2022-03-12T19:37:08.034831+01:00 Telcontar kernel - - - [96076.796132] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49215 PROTO=UDP SPT=427 DPT=36525 LEN=342
The destination port on the computer (36525) is random, so I do not know what port to open.
svrloc 427/udp # Server Location [Veizades]
A second try produces:
<0.4> 2022-03-12T19:41:47.618524+01:00 Telcontar kernel - - - [96356.379741] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49256 PROTO=UDP SPT=427 DPT=36772 LEN=342
Different port.
appears you should use the proper tool, hp-setup rather than hp-toolbox which is primarily for displaying information and adjusting existing printer connections. why do you argue and provide information which supports that hp-toolbox is not the correct application? Just utilize the proper application. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
On 2022-03-12 20:02, Patrick Shanahan wrote:
* Carlos E. R.
[03-12-22 13:44]: On 2022-03-12 19:26, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 13:06]:
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]:
On 2022-03-12 14:22, Patrick Shanahan wrote: > * Carlos E. R. <> [03-12-22 04:00]: >> On 2022-03-12 09:47, J Leslie Turriff wrote: >>> On 2022-03-09 03:45:34 Carlos E. R. wrote: >> >> ... >> >>> >>> Why do you have to drop your firewall? >> >> Printer scanning doesn't work otherwise. > > hp scanning uses ports: > UDP 427 > TCP 9220,9500 > > just open those on the firewall, and/or close when finished scanning. > > fwiw: I have never had to do this for my hp printer scanning over a > network. >
Sorry, I don't mean using the printer scanner, but the computer scanning for a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I.
But the hp tools I cited in the initial post want to scan and find the printer.
no, they do not. I use the same tools and you can. hp-setup in "Device Discovery", select "Show Advanced Options" and "Manual Discovery" enter the requested IP Address -> Next and it has been this way for many years.
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers. Yes, I am aware that you can bypass it and use the "advanced" method to enter the IP manually.
The culprit appears to be this:
<0.4> 2022-03-12T19:37:08.034831+01:00 Telcontar kernel - - - [96076.796132] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49215 PROTO=UDP SPT=427 DPT=36525 LEN=342
The destination port on the computer (36525) is random, so I do not know what port to open.
svrloc 427/udp # Server Location [Veizades]
A second try produces:
<0.4> 2022-03-12T19:41:47.618524+01:00 Telcontar kernel - - - [96356.379741] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49256 PROTO=UDP SPT=427 DPT=36772 LEN=342
Different port.
appears you should use the proper tool, hp-setup rather than hp-toolbox which is primarily for displaying information and adjusting existing printer connections.
why do you argue and provide information which supports that hp-toolbox is not the correct application? Just utilize the proper application.
Because I'm explaining what I did, not what is the perfect/shorter road. I can not change the past. hp-toolbox appeared to me to be the master tool I wanted, and in fact, it calls hp-setup internally. It calls several other tools depending on what menu option is clicked. And no, I am not arguing. You are. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
* Carlos E. R.
On 2022-03-12 20:02, Patrick Shanahan wrote:
* Carlos E. R.
[03-12-22 13:44]: On 2022-03-12 19:26, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 13:06]:
On 2022-03-12 18:59, Patrick Shanahan wrote:
* Carlos E. R. <> [03-12-22 12:45]: > On 2022-03-12 14:22, Patrick Shanahan wrote: > > * Carlos E. R. <> [03-12-22 04:00]: > > > On 2022-03-12 09:47, J Leslie Turriff wrote: > > > > On 2022-03-09 03:45:34 Carlos E. R. wrote: > > > > > > ... > > > > > > > > > > > Why do you have to drop your firewall? > > > > > > Printer scanning doesn't work otherwise. > > > > hp scanning uses ports: > > UDP 427 > > TCP 9220,9500 > > > > just open those on the firewall, and/or close when finished scanning. > > > > fwiw: I have never had to do this for my hp printer scanning over a > > network. > > > > > Sorry, I don't mean using the printer scanner, but the computer scanning for > a printer on the network with broadcast packets.
you cannot get the printer local network address from the router instead of dropping the firewall? arp ip neighbor http://192.168.1.254 (or *your* router/gateway address)
I *assign* static ip addresses to all my printers so I can know which I want to print to and from where.
So do I.
But the hp tools I cited in the initial post want to scan and find the printer.
no, they do not. I use the same tools and you can. hp-setup in "Device Discovery", select "Show Advanced Options" and "Manual Discovery" enter the requested IP Address -> Next and it has been this way for many years.
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers. Yes, I am aware that you can bypass it and use the "advanced" method to enter the IP manually.
The culprit appears to be this:
<0.4> 2022-03-12T19:37:08.034831+01:00 Telcontar kernel - - - [96076.796132] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49215 PROTO=UDP SPT=427 DPT=36525 LEN=342
The destination port on the computer (36525) is random, so I do not know what port to open.
svrloc 427/udp # Server Location [Veizades]
A second try produces:
<0.4> 2022-03-12T19:41:47.618524+01:00 Telcontar kernel - - - [96356.379741] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=49256 PROTO=UDP SPT=427 DPT=36772 LEN=342
Different port.
appears you should use the proper tool, hp-setup rather than hp-toolbox which is primarily for displaying information and adjusting existing printer connections.
why do you argue and provide information which supports that hp-toolbox is not the correct application? Just utilize the proper application.
Because I'm explaining what I did, not what is the perfect/shorter road. I can not change the past.
hp-toolbox appeared to me to be the master tool I wanted, and in fact, it calls hp-setup internally. It calls several other tools depending on what menu option is clicked.
And no, I am not arguing. You are.
-- Cheers / Saludos,
Carlos E. R. (from 15.3 x86_64 at Telcontar)
have it your way, you will dismiss it anyway. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems. -- Per Jessen, Zürich (8.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-) Many attacks on enterprise networks came from inside. I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work. Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained. It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 2022-03-12 14:43:58 Carlos E. R. wrote:
|On 2022-03-12 20:44, Per Jessen wrote: |> Carlos E. R. wrote: |>> I used "hp-toolbox". On "device setup", select "network", "Next". |>> Answer after a while: no printer found. |>> |>> Now, drop the firewall and repeat: printer is found. |>> |>> That's HP functionality to scan the network and find printers. |> |> I have to say, I find HP's approach entirely right, not to expect anyone |> to be running firewalls on local systems. | |Kind of :-) | |Many attacks on enterprise networks came from inside. | |I would prefer to document (a link in the error message) what to open in |the firewall to make search for printers work. Notice that YaST has this |problem for decades, devs have not been able to provide a configuration |for the SuSEfirewall2 to open whatever is needed available as an option |from the printer configuration module, or at least explained. | |It is a common complaint from newbies, for many years, that scan for |printer in *SUSE doesn't work.
I know I'm probably weird to think this, but I would expect their tool to examine /etc/hosts or other local network config files as the first step to locating printers. The idea that a LAN with a few devices on it should be managed dynamically (with something like DHCP) seems silly to me. I also (as another commenter does) assign my local devices statically (outside of DHCP) and put them into /etc/hosts; it's the easiest way, since I have fewer than a dozen devices to manage, and I don't have to worry about devices' IP addresses mysteriously changing behind my back. Leslie --
On 2022-03-12 22:36, J Leslie Turriff wrote:
On 2022-03-12 14:43:58 Carlos E. R. wrote:
|On 2022-03-12 20:44, Per Jessen wrote: |> Carlos E. R. wrote:
I know I'm probably weird to think this, but I would expect their tool to examine /etc/hosts or other local network config files as the first step to locating printers. The idea that a LAN with a few devices on it should be managed dynamically (with something like DHCP) seems silly to me. I also (as another commenter does) assign my local devices statically (outside of DHCP) and put them into /etc/hosts; it's the easiest way, since I have fewer than a dozen devices to manage, and I don't have to worry about devices' IP addresses mysteriously changing behind my back.
Certainly. But their design was made for Windows, and there is no such thing in Windows as a maintained host file, specially on homes. People just expect to plug in a new computer and a new printer and have one find another, automatically. The behaviour in Linux simply emulates this, and it does work - if the firewall is not in the way. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On Sat, 12 Mar 2022 21:43:58 +0100
"Carlos E. R."
On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
It's weird. The first time I read this thread, I could swear it was Carlos saying HP's approach was right, and Per pointing out the enterprise risks ... But in a way I think only Carlos' approach can be correct, so far. It's possible for people to be running firewalls, so any self-respecting designer/programmer needs to deal with that. However ...
I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work.
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
That's just sad :(
* Dave Howorth
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R."
wrote: On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
It's weird. The first time I read this thread, I could swear it was Carlos saying HP's approach was right, and Per pointing out the enterprise risks ...
But in a way I think only Carlos' approach can be correct, so far. It's possible for people to be running firewalls, so any self-respecting designer/programmer needs to deal with that. However ...
I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work.
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
That's just sad :(
have you experienced this? I have not and *many* years ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R."
wrote: On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
It's weird. The first time I read this thread, I could swear it was Carlos saying HP's approach was right, and Per pointing out the enterprise risks ...
We won't let facts get in our way :-)
And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Yep! they could at least warn you. -- Per Jessen, Zürich (9.8°C)
On 2022-03-12 23:22, Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R." <> wrote:
On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
It's weird. The first time I read this thread, I could swear it was Carlos saying HP's approach was right, and Per pointing out the enterprise risks ...
But in a way I think only Carlos' approach can be correct, so far. It's possible for people to be running firewalls, so any self-respecting designer/programmer needs to deal with that. However ...
I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work.
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Linux people have been doing this for long, pointing to a link, if the
explanation is long.
We can, I hope, judge that the links appear safe.
Examples found:
grep http: /var/log/mail
grep https: /var/log/mail
<2.3> 2018-02-23 13:19:10 Telcontar dovecot - - - imap: Error: Time
just moved backwards by 1 seconds. I'll sleep now until we're back in
present. http://wiki2.dovecot.org/TimeMovedBackwards
<2.3> 2013-06-17 14:40:12 Telcontar fetchmail 13271 - - For help, see
http://www.fetchmail.info/fetchmail-FAQ.html#R15
<2.3> 2022-01-30T13:03:27.768501+01:00 Telcontar freshclam 2297 - -
check_for_new_database_version: Failed to find daily database using
server https://database.clamav.net.
I remember two others from gmx and google too, when they consider my
attempt to send email as spam, but can't locate them. And in those cases
the URL contain my IP address.
Printer errors, in /var/log/messages:
<1.1> 2022-03-12T13:56:42.292414+01:00 Telcontar - - - -
hp-upgrade[21980]: error: HPLIP upgrade is disabled by openSUSE for
security reasons, see https://bugzilla.suse.com/show_bug.cgi?id=853405 -
if you like to upgrade HPLIP, use an openSUSE software package manager
like YaST or zypper.
other:
<5.4> 2022-02-24T13:25:59.625951+01:00 Telcontar rsyslogd - - - action
'action-4-builtin:ompipe' suspended (module 'builtin:ompipe'), retry 0.
There should be messages before this one giving the reason for
suspension. [v8.2106.0 try https://www.rsyslog.com/e/2007 ]
Ah, yes:
<2.6> 2022-02-22T22:22:01.244145+01:00 Telcontar postfix 17974 - -
1D6B5320978: to=
Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
That's just sad :(
I don't know if sad, but they claim that doesn't happen with Ubuntu, and that does irk me a bit, not knowing why. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2022-03-12 23:22, Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R." <> wrote:
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Linux people have been doing this for long, pointing to a link, if the explanation is long.
We can, I hope, judge that the links appear safe.
Examples found: [snip]
I think this is the point where it is reasonable to suggest someone might like to offer a patch for our hplip package. Especially as this has been going on for many years. Problem: no HP printers found. Solution 1: https://www.hp.com/us-en/shop/cv/printers Solution 2: open port xxx in your firewall.
Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
That's just sad :(
I don't know if sad, but they claim that doesn't happen with Ubuntu, and that does irk me a bit, not knowing why.
Maybe port 427 is open by default. -- Per Jessen, Zürich (12.3°C)
On 2022-03-13 11:13, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-12 23:22, Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R." <> wrote:
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Linux people have been doing this for long, pointing to a link, if the explanation is long.
We can, I hope, judge that the links appear safe.
Examples found: [snip]
I think this is the point where it is reasonable to suggest someone might like to offer a patch for our hplip package. Especially as this has been going on for many years.
Problem: no HP printers found.
Solution 1: https://www.hp.com/us-en/shop/cv/printers
Sorry, what do you see here as solution? :-?
Solution 2: open port xxx in your firewall.
That also would not work. It is, AFAIK, an answer to a broadcast, and it doesn't come back in a fixed port number.
Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
That's just sad :(
I don't know if sad, but they claim that doesn't happen with Ubuntu, and that does irk me a bit, not knowing why.
Maybe port 427 is open by default.
Port 427...? Ah, I see. No, it is outgoing port 427 on the printer, the incoming port number on the computer is unknown, random. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2022-03-13 11:13, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-12 23:22, Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R." <> wrote:
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Linux people have been doing this for long, pointing to a link, if the explanation is long.
We can, I hope, judge that the links appear safe.
Examples found: [snip]
I think this is the point where it is reasonable to suggest someone might like to offer a patch for our hplip package. Especially as this has been going on for many years.
Problem: no HP printers found.
Solution 1: https://www.hp.com/us-en/shop/cv/printers
Sorry, what do you see here as solution? :-?
no HP printers found -> buy an HP printer :-)
Solution 2: open port xxx in your firewall.
That also would not work. It is, AFAIK, an answer to a broadcast, and it doesn't come back in a fixed port number.
Well, I don't have any HP printers, so that's all I can suggest. -- Per Jessen, Zürich (14.1°C)
On 2022-03-13 12:04, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-13 11:13, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-12 23:22, Dave Howorth wrote:
On Sat, 12 Mar 2022 21:43:58 +0100 "Carlos E. R." <> wrote:
The difficulty with this approach is that we're all taught not to click on unexpected links offered to us, so the explanation would have to be spelled out in the error message itself. And if HP is using random ports it doesn't make any sense anyway. Basically HP is wrong!
Linux people have been doing this for long, pointing to a link, if the explanation is long.
We can, I hope, judge that the links appear safe.
Examples found: [snip]
I think this is the point where it is reasonable to suggest someone might like to offer a patch for our hplip package. Especially as this has been going on for many years.
Problem: no HP printers found.
Solution 1: https://www.hp.com/us-en/shop/cv/printers
Sorry, what do you see here as solution? :-?
no HP printers found -> buy an HP printer :-)
:-D But I do have an HP printer.
Solution 2: open port xxx in your firewall.
That also would not work. It is, AFAIK, an answer to a broadcast, and it doesn't come back in a fixed port number.
Well, I don't have any HP printers, so that's all I can suggest.
Ok :-) -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
Solution 2: open port xxx in your firewall.
That also would not work. It is, AFAIK, an answer to a broadcast, and it doesn't come back in a fixed port number.
[snip]
I don't know if sad, but they claim that doesn't happen with Ubuntu, and that does irk me a bit, not knowing why.
Maybe port 427 is open by default.
Port 427...? Ah, I see. No, it is outgoing port 427 on the printer, the incoming port number on the computer is unknown, random.
It is what HP suggests too. Maybe it is worth trying out? https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Enable... -- Per Jessen, Zürich (14.4°C)
On 2022-03-13 12:55, Per Jessen wrote:
Carlos E. R. wrote:
Solution 2: open port xxx in your firewall.
That also would not work. It is, AFAIK, an answer to a broadcast, and it doesn't come back in a fixed port number.
[snip]
I don't know if sad, but they claim that doesn't happen with Ubuntu, and that does irk me a bit, not knowing why.
Maybe port 427 is open by default.
Port 427...? Ah, I see. No, it is outgoing port 427 on the printer, the incoming port number on the computer is unknown, random.
It is what HP suggests too. Maybe it is worth trying out?
https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Enable...
And much more, but Ok, I will try. [...] Nope. FW_SERVICES_EXT_UDP="sip h323hostcall 5060:5100 mdns 4674 4667 427" -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work. Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
I expect s/not been able/not been willing/
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
So surely there is a neat article in the SDB describing the issue and how it is best resolved? -- Per Jessen, Zürich (9.8°C)
On 2022-03-13 10:09, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-12 20:44, Per Jessen wrote:
Carlos E. R. wrote:
I used "hp-toolbox". On "device setup", select "network", "Next". Answer after a while: no printer found.
Now, drop the firewall and repeat: printer is found.
That's HP functionality to scan the network and find printers.
I have to say, I find HP's approach entirely right, not to expect anyone to be running firewalls on local systems.
Kind of :-)
Many attacks on enterprise networks came from inside.
I would prefer to document (a link in the error message) what to open in the firewall to make search for printers work. Notice that YaST has this problem for decades, devs have not been able to provide a configuration for the SuSEfirewall2 to open whatever is needed available as an option from the printer configuration module, or at least explained.
I expect s/not been able/not been willing/
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
So surely there is a neat article in the SDB describing the issue and how it is best resolved?
Not that I'm aware of.
But I'm aware of the issue for over a decade, and the maintainer is also
aware of it (jsmeix?). Basically he said once he is printer expert, not
firewall expert.
Found it - but not in the archive:
Date: Thu, 2 Jul 2009 11:40:40 +0200 (CEST)
From: Johannes Meixner <...>
To: Boris Epstein <...>
Cc: openSUSE Mailing List
Just wondering if anybody knows off the top of their head which services I need to allow in my firewall in order to allow my OpenSuSE 11.1 system to find printers on the local network.
See http://bugzilla.novell.com/show_bug.cgi?id=498429 For some background information regarding Firewall settings with YaST see also https://bugzilla.novell.com/show_bug.cgi?id=468426 For basic information regarding CUPS and printing in the network see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell Kind Regards Johannes Meixner --------- Date: Tue, 3 Aug 2010 12:46:46 +0200 (CEST) From: Johannes Meixner <...> To: Carlos F Lange <...> Cc: opensuse@opensuse.org Subject: Re: [opensuse] why no "cups" entry in YaST Firewall Allowed Services in 11.3? Hello, On Jul 26 20:13 Carlos F Lange wrote:
In the Firewall Configuration of YaST, the list of services to allow for the External Zone no longer contains "cups". Instead, When setting up the Printer Configuration to accept printer announcements from CUPS servers, YaST pops up a recommendation to open UDP port 631 in the firewall.
There should be no recommendation to open any port in the firewall. But the current popup texts could be misunderstood to do it. Therefore I filed https://bugzilla.novell.com/show_bug.cgi?id=627799
Any sane reason to make this process less convenient?
This is intentionally to avoid that almost all normal users open a security hole because in the usual network environments, the IPP port should never be opened for the EXT zone, see http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings Additionally you may have a look at https://bugzilla.novell.com/show_bug.cgi?id=610327 Kind Regards Johannes Meixner --------- Notice that finding CUPS is not the same as finding a printer, not the same method and port, AFAIK. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2022-03-13 10:09, Per Jessen wrote:
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
So surely there is a neat article in the SDB describing the issue and how it is best resolved?
Not that I'm aware of.
From about two minutes worth of googling:
https://en.opensuse.org/SDB:How_to_set-up_a_HP_printer https://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings https://forums.opensuse.org/showthread.php/518376-Can-t-detect-HP-network-pr... https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Enable... The last two are the best. The two top ones look like they could do with updating.
But I'm aware of the issue for over a decade, and the maintainer is also aware of it (jsmeix?). Basically he said once he is printer expert, not firewall expert.
Well, that seems to be a decent opportunity for someone to contribute, either to the SDB or to the hplip package (I am assuming that is the one?). However, seeing as noone has been bothered for a decade, maybe it isn't such a major issue ? -- Per Jessen, Zürich (12.6°C)
On 2022-03-13 12:01, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-13 10:09, Per Jessen wrote:
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
So surely there is a neat article in the SDB describing the issue and how it is best resolved?
Not that I'm aware of.
From about two minutes worth of googling:
I know all those links, except the last two.
+++-------------- Network Printer Setup: 1. From the hp-setup menu choose the option "Network/Ethernet..." 2. Click the "Show Advanced Options" button, check the "Manual Discovery" checkbox and enter the printer's IP address 3. Click "Next" and continue setting up the printer as described above --------------++- Enter the IP... so the instructions assume that discovery is not going to work. I might contribute to that article and mention dropping the firewall. Oh, look, it is already there: +++-------------- Troubleshooting As a workaround it may help to temporarily disable the firewall for network printers to be found. Once the printer has been found and added, the firewall should be re-enabled. The right solution is to properly set up networking and firewall. For more information see SDB:CUPS and SANE Firewall settings in particular the section "What is Specific Regarding Firewall Setup for Printing". --------------++- Well, I have to say that there is nothing there about discovery of HP printers. It explains what to do to make CUPS work, not discovery of HP printers (except dropping the entire firewall in the first sentence, just as I did).
This is the paragraph I posted above. Nothing there about discovery of HP printers.
https://forums.opensuse.org/showthread.php/518376-Can-t-detect-HP-network-pr...
«Try stopping the firewall first just while you configure with hp-setup.» And the poster confirms that this does work.
https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Enable...
The last two are the best. The two top ones look like they could do with updating.
Only the last one handles the issue of "HP discovery". We have to allow "Zeroconf/Bonjour Multicast DNS" in the firewall - the new one, not SuSEfirewall2 as I still have. I searched for "zero" in /etc/sysconfig/SuSEfirewall2 and it is not mentioned. Notice that I remember threads in the past saying that this was dangerous to allow. It also requires services to be started (not mentioned in the article. I paste here the contents of that link, so that they are available for future searchs: +++-------------- How to unblock ports and enable services in the firewall HPLIP Version: All Printer(s): All Linux OS Distribution(s): opensuse, rhel Notes: - 1 Firewall Settings HPLIP uses service discovery protocols like avahi, SLP to discover network resources like printers in a Local Area Network(LAN). These services listen at well defined port numbers. Therefore to allow resource discovery, it is required certain ports should not be blocked by firewall, if any, running on the host machine. By default in OpenSuse/RHEL etc., all the ports are blocked due to security considerations. In this particular scenario HPLIP cannot discover the printers on LAN using network discovery methods (slp, avahi, mDNS/bonjour). To allow network discovery methods to discover printers in LAN follow the steps mentioned below. OpenSUSE Avahi Go to Yast Control Center and click on Firewall. Select Allowed Services on the left hand side pane. Click on Service to Allow drop-down, which will show a list of services we can enable using this firewall utility. To allow avahi to discover the devices through hp-setup utility, select Zeroconf/Bonjour Multicast DNS and select Add from drop down, and click on Next at the bottom right corner. The OpenSuse Firewall Utility will display Firewall Configuration Summary. Click on Finish to compelete the process. mDNS/Bonjour Go to Yast Control Center and click on Firewall Select Custom Rules on left pane, select Zone as External and then select Add at the bottom. A pop up will appear . Provide the values of the parameter as : Source Network 0/0, Protocol UDP, Ports 5353 Click on Add at the bottom right. The OpenSuSe rewall utility will display Firewall Conguration Summary Click on Finish to complete the process. SLP Go to Yast Control Center and click on Firewall. Select Custom Rules on left pane, select Zone as External and then select Add at the bottom. A pop up will appear . Provide the values of the parameter as : Source Network 0/0, Protocol UDP, Ports 427 Click on Add at the bottom right. The OpenSuSe rewall utility will display Firewall Conguration Summary Click on Finish to complete the process. For advanced usage of the SuSeFirewall2 utility and more details about the above options check the following link https://en.opensuse.org/SuSEfirewall2 RHEL mDNS/Bonjour 1.Go to Firewall Configuration on RHEL system. 2. Switch to Public->Ports tab. 3. Click Add button. 4. Input 5353 in Port/Range text box. 5. Select protocol type as udp. 6. Save the changes. --------------++-
But I'm aware of the issue for over a decade, and the maintainer is also aware of it (jsmeix?). Basically he said once he is printer expert, not firewall expert.
Well, that seems to be a decent opportunity for someone to contribute, either to the SDB or to the hplip package (I am assuming that is the one?). However, seeing as noone has been bothered for a decade, maybe it isn't such a major issue ?
AFAIK, Ubuntu doesn't have an issue. So, HP doesn't have an issue. *SUSE does. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 2022-03-13 12:55, Carlos E. R. wrote:
On 2022-03-13 12:01, Per Jessen wrote:
Carlos E. R. wrote:
On 2022-03-13 10:09, Per Jessen wrote:
It is a common complaint from newbies, for many years, that scan for printer in *SUSE doesn't work.
So surely there is a neat article in the SDB describing the issue and how it is best resolved?
Not that I'm aware of.
From about two minutes worth of googling:
I know all those links, except the last two.
...
https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Enable...
The last two are the best. The two top ones look like they could do with updating.
Only the last one handles the issue of "HP discovery".
I just noticed this text in the terminal where I had run hp-setup: Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp) error: No devices found on bus: net error: HPLIP cannot detect printers in your network. This may be due to existing firewall settings blocking the required ports. When you are in a trusted network environment, you may open the ports for network services like mdns and slp in the firewall. For detailed steps follow the link. http://hplipopensource.com/node/374 But that link is dead. Redirects to https://developers.hp.com/hp-linux-imaging-and-printing/node/374 which responds Page not found The requested page "/hp-linux-imaging-and-printing/node/374" could not be found. And no, doesn't work with SuSEfirewall2. FW_SERVICES_EXT_UDP="sip h323hostcall 5060:5100 mdns slp 427 4674 4667" I have avahi-daemon.service and avahi-daemon.socket enabled. avahi-dnsconfd.service is not. I activated it, no difference. With all these tests, I see this on the firewall log: <0.4> 2022-03-15T11:09:32.296997+01:00 Telcontar kernel - - - [165601.945448] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:d8:61:a1:5a:bd:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=192.168.1.14 LEN=362 TOS=0x00 PREC=0x00 TTL=64 ID=31194 PROTO=UDP SPT=427 DPT=38972 LEN=342 Which is blocked incoming, from printer on port UDP 427, but on the computer comes on a random port. Something on the outgoing broadcast (guess) says what port the hp application will be listening, but somehow the kernel is not aware that it is a reply communication and the firewall blocks it. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (5)
-
Carlos E. R.
-
Dave Howorth
-
J Leslie Turriff
-
Patrick Shanahan
-
Per Jessen