It still requires the device to be capable to print...
And the user to find the printer select it and so on. And must expose more ports on the network beside 443...
So, indeed cups is a great solution, but not to the problem I want to solve.
I do use cups in fact for the trusted part of the network, driverless printing for windows and Linux. Android doesn't even need cups since it picks up the printer directly from the printer itself (AirPrint or whatevee that's called).
I have a very similar issue.
Seems like Android will bypass your DNS resolver and thus cannot resolve your local names.
I have my home services on "home.mydomain.com" accessible from outside and re-mapped to "192.168.0.1" (my internal server IP) at home, and all PCs can access it while all android phones can only resolve to the public IP.
I feel it's something related to DoT or similar but haven't yet dig in that.
It still requires the device to be capable to print...
And the user to find the printer select it and so on. And must expose more ports on the network beside 443...
So, indeed cups is a great solution, but not to the problem I want to solve.
I do use cups in fact for the trusted part of the network, driverless printing for windows and Linux. Android doesn't even need cups since it picks up the printer directly from the printer itself (AirPrint or whatevee that's called).