AirPrint via an AI agent: xiiaozet + Canon MG2580S

I needed network printing from my Mac without babysitting USB cables. The setup looked simple on paper. It was not.

The mess I started with

Home Wi‑Fi is split across two subnets:

• huaguancats — 192.168.1.x
• ASUS_C8 — a different LAN the Mac often lands on

The printer side is a Canon PIXMA MG2580S hanging off a cheap xiiaozet WIFI-3L USB Wi‑Fi dongle. I pointed Hermes (Chippy) at the problem and let it dig instead of guessing myself.

What the dongle actually is

First discovery: the xiiaozet is not a smart print server. No SSH. No useful admin UI. No AirPrint advertisement of its own.

It is basically a dumb JetDirect bridge — raw TCP 9100 to whatever USB printer is plugged in. Once you stop expecting IPP/AirPrint from the dongle, the rest of the design gets obvious.

Driver reality check

Generic PostScript and ESC/POS were dead ends on the MG2580S. The working path is Gutenprint, not Apple's generic drivers and not a thermal receipt stack.

Bridge that works

I put CUPS + Gutenprint on server-hm, on the same 192.168.1.x side as the dongle:

socket://192.168.1.101:9100

That host becomes the real print server. The Mac is just an IPP client talking to CUPS on server-hm — AirPrint-style from the laptop's point of view, even though the last hop is raw 9100.

Cross-subnet pain was real. When the Mac was on ASUS_C8 and the dongle/printer lived on huaguancats, discovery and "it should just work" assumptions failed until the bridge sat on the printer subnet and exposed IPP cleanly.

CUPS green is not paper on the tray

CUPS went green. Queue accepted jobs. That still does not mean a page hit the floor.

I only trusted the setup after a physical confirmation — actual paper coming out of the MG2580S. Software status lied politely until the mechanical path was proven.

What I took away

1. Cheap Wi‑Fi USB print dongles are often TCP 9100 only. Design around that.
2. PIXMA MG2580S wants Gutenprint, not generic PS.
3. Put the CUPS bridge on the printer subnet; let the Mac be an IPP client.
4. Dual Wi‑Fi homes break "local printer" fairy tales until you own the routing story.
5. Agents are useful here: scan the LAN, identify the dongle personality, pick the driver, wire the queue. Still verify with paper.

This is the kind of home-lab glue I actually want agents for — tedious discovery, concrete config, no slide deck.