I have a wireless Brother MFCJ1360DW printer. I’m used to P&P. CUPS shows it’s ready to print, but when I send a test page, it’s “waiting for the printer to become available.” I don’t see it in the router config. There’s a BRW on 5G, but I configured the printer for 2.4G. CUPS also shows it’s USB connected, usb://dev/usb/lp0. What’s this lp0? Any suggestions?
Do you have the printer connected via USB? I ask because the usb://dev/usb/lp0 URI means CUPS thinks the printer is connected via the Linux USB printer device (/dev/usb/lp0). That’s not a network connection.
Please show the output of lpstat -t from a terminal.
You should be able to print the printer’s “Network Configuration Report” and check that it has successfully joined your Wi-Fi networkand has an IP address. If it does, see if you can ping that address from your computer.
If the printer is on the network, try discovering it with driverless or ippfind. Modern network printers generally support driverless (IPP Everywhere/AirPrint) printing. Brother also provides dedicated CUPS drivers for most of its printers if you prefer to use those.
BTW, if the openSUSE firewall (Firewalld) is active, you may need to allow the mdns service (UDP port 5353). Otherwise, automatic discovery with driverless, ippfind, or avahi-browse may not work, even if the printer is reachable by IP.
> lpstat -t
scheduler is running
no system default destination
device for MFCJ1360DW: usb://dev/usb/lp0
MFCJ1360DW accepting requests since Sat 18 Jul 2026 08:52:25 PM PDT
printer MFCJ1360DW is idle. enabled since Sat 18 Jul 2026 08:52:25 PM PDT
ippfind and driverless both show no results.
What steps did you take to getting your printer connected to your Wi-Fi network? I assume this part is done (as per the user manual directions)?
Again, you may need to confirm the openSUSE firewall status and configuration, otherwise we’re left to guess…
sudo systemctl status firewalld
sudo firewalld-cmd --list-all
If you prefer a GUI, you can install firewall-config. Application is the same name. Otherwise, it should be present in Cockpit, but check if the firewall is even active as per the command I gave already.
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; preset>
Active: active (running) since Wed 2026-07-15 11:08:18 PDT; 5 days ago
Invocation: d8038f6123d44a4bbbdf7ad8bfb2ffb2
Docs: man:firewalld(1)
Main PID: 1466 (firewalld)
Tasks: 2 (limit: 18903)
CPU: 429ms
CGroup: /system.slice/firewalld.service
└─1466 /usr/bin/python3.13 /usr/sbin/firewalld --nofork --nopid
Jul 15 11:08:18 linuxdesktop systemd[1]: Starting firewalld - dynamic firewall >
Jul 15 11:08:18 linuxdesktop systemd[1]: Started firewalld - dynamic firewall d>
I’m getting a note “End” when I enter these commands. How do I end the session?
Speculating that it has opened the results in a viewer called less because there is more text than fits on the screen? Press the q key to exit back to the command prompt. Anyway, you can see that the firewall is active. How about sharing sudo firewalld-cmd --list-all as requested?
sudo: firewalld-cmd: command not found
Sorry should be…
sudo firewall-cmd --list-all
> sudo firewall-cmd --list-all
[sudo] password for root:
public (default, active)
target: default
ingress-priority: 0
egress-priority: 0
icmp-block-inversion: no
interfaces: eth0 wlan0
sources:
services: cockpit dhcpv6-client
ports:
protocols:
forward: yes
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
As root:
firewall-cmd --permanent --add-service=ipp
and
firewall-cmd --permanent --add-service=mdns
restart your firewall:
systemctl restart firewalld.service
now
driverless
should work.
1 Like
Actually, only the mdns port needs to be open here for discovery to work.
The ipp TCP port 631 only needs to be open for incoming IPP connections if your computer is acting as a CUPS print server for other devices.
Helpful wiki pages:
https://en.opensuse.org/SDB:Installing_a_Printer
https://en.opensuse.org/Concepts_printing
1 Like
So remove ipp as root:
firewall-cmd --permanent --remove-service=ipp
restart the firewall:
systemctl restart firewalld.service
I’ve confirmed the IP address of the printer. CUPS doesn’t recognize it as a network device. It lists it as a USB connection. I can’t ping the printer right now. Any suggestions what to do next?
This reads as though you initially had it connected as a USB printer. You can delete that configuration if not using it that way.
If your firewall is now configured properly ie you’ve already allowed mDNS through the firewall as mentioned earlier, the printer should be automatically discovered and available as a driverless (IPP Everywhere) printer. It should be enumerated by lpstat -e,driverless, or ippfind commands.
However, since you can’t ping the printer, it suggests that you still have a network connectivity issue. I’d first check that the printer is connected to the network and that the IP address is correct.
Returning to your initial statements…
…I’d start by confirming that it’s actually connected to your Wi-Fi. Printing the printer’s network status page can help verify its current SSID and IP address. Refer to your printer’s user manual if not sure how to do this.
If it is connected but still isn’t reachable from your PC, check if the router has “wireless client isolation” (sometimes called AP isolation or device isolation) enabled, as that can prevent devices on Wi-Fi from communicating with each other.