My printer itself registers a privet address on mDNS, even though I have tried to disable this in its settings. When I use the connector to drive it, the connector is unable to create a local privet name. I get this error:
Avahi failed to register Behemoth due to a naming collision
The connector should handle this naming conflict.
该提问来源于开源项目:google/cloud-print-connector