Simply sudo zypper in nmap
…
Use zypper for package search: zypper se -s nmap
Simply sudo zypper in nmap
…
Use zypper for package search: zypper se -s nmap
Sonne:~ # zypper addrepo https://download.opensuse.org/repositories/network:utilities/openSUSE_Factory_PowerPC/network:utilities.repo network-utilities
…
Repository 'network-utilities' successfully added
…
Sonne:~ # zypper refresh
…
Repository 'network-utilities' is invalid.
[network-utilities|https://download.opensuse.org/repositories/network:utilities/openSUSE_Factory_PowerPC/network:utilities.repo] Failed to retrieve new repository metadata.
…
Did you read the last comment? Simply install nmap from the standard openSUSE Tumbleweed repo. No need to add some abritrary (invalid) repos for PowerPC!!!
Btw, “if” you want to add some repo you should familiarize yourself with the command syntax. There are even correct examples on the s.o.o site. By using the repo file, you don’t need to specify the repo alias yourself (as you did). The repo name is part of the repo file…
Sonne:~ # zypper install nmap
Loading repository data…
Reading installed packages…
‘nmap’ not found in package names. Trying capabilities.
No provider of ‘nmap’ found.
Resolving package dependencies…
Nothing to do.
How will software distributions evolve further also for network utilities?
@elfring Stay on focus for the issue please, nmap is in the non-oss repo, just install that, no more, no less.
Provide the folks trying to help you with the requested information.
Really? You do not not even have a proper set of Tumbleweed repos…?
test@testbox:~> LANG=C sudo zypper in nmap
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
nmap
1 new package to install.
Package download size: 5.8 MiB
Package install size change:
| 25.5 MiB required by packages that will be installed
25.5 MiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
test@testbox:~> LANG=C zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
--+----------------------------+-------------------+---------+-----------+---------+------+----------+--------+----------------------------------------------------------------------------+---------
1 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss?mediahandler=curl2 | openSUSE
2 | openSUSE:repo-openh264 | repo-openh264 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed?mediahandler=curl2 | openSUSE
3 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss?mediahandler=curl2 | openSUSE
4 | openSUSE:repo-oss-debug | repo-oss-debug | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/tumbleweed/repo/oss?mediahandler=curl2 | openSUSE
5 | openSUSE:repo-oss-source | repo-oss-source | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/tumbleweed/repo/oss?mediahandler=curl2 | openSUSE
6 | openSUSE:update-tumbleweed | update-tumbleweed | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/update/tumbleweed?mediahandler=curl2 | openSUSE
test@testbox:~>
Markus_Elfring@Sonne:~> nmap -F 192.168.178.31
Starting Nmap 7.95 ( https://nmap.org ) at 2025-05-30 09:46 CEST
Nmap scan report for KMDD37DF.fritz.box (192.168.178.31)
Host is up (0.022s latency).
Not shown: 92 closed tcp ports (conn-refused)
PORT STATE SERVICE
21/tcp open ftp
80/tcp open http
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
515/tcp open printer
631/tcp open ipp
9100/tcp open jetdirect
Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds
Will the software capabilities be clarified any further for this device?
The results show that it has port 631 open (consistent with a printer supporting the IPP protocol). If the printer was advertising itself via Bonjour, CUPS would dynamically enumerate it as an IPP printer ie no configuration needed. However, you can manually configure CUPS for this printer using
sudo lpadmin -p printername -E -v ipp://192.168.178.31/ipp/print -m everywhere
Substitute ‘pirntername’ with an actual printer name you’d like to use.
See how that goes.
I would appreciate to see more of such functionality in action (also on my system).
Thanks for such information.
I was unsure about the required path for this print service.
Another test printout has succeeded with KWrite for a small text file.
Will the chances grow to achieve the same result also with the USB connection?
Ok, so IPP printing is working as expected. This printer model only supports IPP (Internet Printing Protocol) over network connections, and not over USB.