ufp: Multifunction printer identified as scanner

Package Name

ufp

Maintainer

@nbd168

OpenWrt Version

00c8b5c612

OpenWrt Target/Subtarget

mediatek/filogic

Steps to Reproduce

ufp ver 2025.09.23~7d9f3bee-r1

@cmonroe

Actual Behaviour

My Epson XP=2200 is identified as a scanner, perhaps because its last umdns entry is for the scanner. Not sure the best way for ufp to handle cases where a device maps to multiple classes.

{ "_pdl-datastream._tcp": { "EPSON XP-2200 Series": { "iface": "br-lan", "txt": "txtvers=1", "txt": "priority=30", "txt": "ty=EPSON XP-2200 Series", "txt": "usb_MFG=EPSON", "txt": "usb_MDL=XP-2200 Series", "txt": "product=(EPSON XP-2200 Series)", "txt": "pdl=application/vnd.epson.escpr", "txt": "qtotal=1", "txt": "adminurl=http://EPSON481201.local.:80/PRESENTATION/", "txt": "note=" } }, "_printer._tcp": { "EPSON XP-2200 Series": { "iface": "br-lan", "txt": "txtvers=1", "txt": "priority=50", "txt": "ty=EPSON XP-2200 Series", "txt": "usb_MFG=EPSON", "txt": "usb_MDL=XP-2200 Series", "txt": "product=(EPSON XP-2200 Series)", "txt": "pdl=application/vnd.epson.escpr", "txt": "rp=auto", "txt": "qtotal=1", "txt": "adminurl=http://EPSON481201.local.:80/PRESENTATION/", "txt": "note=" } }, "_scanner._tcp": { "EPSON XP-2200 Series": { "iface": "br-lan", "txt": "txtvers=1", "txt": "ty=EPSON XP-2200 Series", "txt": "adminurl=http://EPSON481201.local.:80/PRESENTATION/", "txt": "mfg=EPSON", "txt": "mdl=XP-2200 Series", "txt": "UUID=cfe92100-67c4-11d4-a45f-f82551481201", "txt": "scannerAvailable=1", "txt": "note=" } } }

Confirmation Checklist

• The package is maintained in this repository.
• I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
• I am reporting an issue for OpenWrt, not an unsupported fork.

No source file or test is named; start by reproducing the ufp output and reviewing the reported umdns records for _pdl-datastream._tcp, _printer._tcp, and _scanner._tcp. Done means a multifunction device such as the Epson XP-2200 is handled correctly rather than being identified only as a scanner, with the intended behavior for multiple classes established.