Solution for Canon Pixma E470 Printer and Scanner Detection Issues with firewalld Enabled

General system Community contributions
1

Printer Model

Canon Pixma E470

Driver Installed on Endeavour OS

Driver: canon-pixma-ts5055-complete (from AUR)
CUPS: Active and enabled

Issue Description

The printer and scanner are not detected when firewalld is enabled. However, both functions correctly when firewalld is disabled.

Troubleshooting Steps

I attempted to enable several ports as recommended by the Canon website and various forums. This resolved the issue for the printer, but the scanner remains undetected, and the cnijlgmon3 service fails to recognize the printer.

Update 19/06/2025: cnijlgmon3 is an old name, it’s scangearmp2 now.

List of Port Numbers

Port Purpose
TCP/UDP 9100 For printing using Raw protocol
TCP/UDP 1900 For Universal Plug and Play (UPnP) operation
TCP/UDP 5222 For Google Cloud Print and PIXMA Cloud Link
TCP/UDP 5357 For acquiring the printer information (WSDAPI)
TCP/UDP 8611 Canon BJNP port for printing
TCP/UDP 8612 Canon BJNP port for scanning (Applicable models only)
TCP/UDP 8613 Canon BJNP port for sending and receiving faxes from the PC (Applicable models only)

Solution

In firewalld, select the preferred zone and add the printer’s MAC address to the Rich Rules. No additional port numbers need to be added, as I ultimately cleared my list of port numbers.

sudo firewall-cmd --permanent --zone=home --add-rich-rule='rule family="ipv4" source mac="xx:xx:xx:xx:xx:xx" accept'
sudo firewall-cmd --reload
2 Likes
2

that is bizarre. Just got a canon imageclass and did not go through this. This is a network printer and not a personal home pc, I am assuming?
Either way, good work getting to the bottom of that. Just enabling ports allowed the OS to detect the physical device.
Printers/scanners can take hours :slight_smile:

1 Like
3

It’s a network printer intended for personal home use, allowing all family members to access it from their own devices. :blush:

And yes, it took me hours to resolved the issue :stuck_out_tongue:

4

makes more sense. I woulda expected network recognition but inability to print because of the firewall. Not seeing it at all, on the other hand, is interesting.