Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Ralph On 29/07/2019 20:30, t...@ls83.eclipse.co.uk wrote: While following on from the fresh install on AP0, and still on AP0: # avahi-browse -at + wlp1s0 IPv6 Brother HL-5270DN series @ golux Internet Printer local + wlp1s0 IPv6 Canon MP230 series @ golux Internet Printer local + wlp1s0 IPv6 AirPrint HL-5270DN-Home @ golux Internet Printer local + wlp1s0 IPv6 AirPrint MP230 @ golux Internet Printer local + wlp1s0 IPv6 Brother HL-5270DN series @ golux Secure Internet Printer local + wlp1s0 IPv6 Canon MP230 series @ golux Secure Internet Printer local + wlp1s0 IPv6 golux Remote Disk Management local + wlp1s0 IPv6 Canon MP230 series @ golux UNIX Printer local + wlp1s0 IPv6 Brother HL-5270DN series @ golux UNIX Printer local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 Web Site local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 _psia._tcp local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 _CGI._tcp local As above, AP0 shows only IPv6 entries. I have IPv6 disabled on that AP (a Draytek 2862), following our discussions where you suggested I try that. On AP1 and AP2 I get IPv4 entries too. If I disable IPv6 on AP0 (which causes it to reboot), then I can print while connected to it (just a reboot doesn't normally help). That's until I connect to AP1 and back again. Toggling IPv6 on AP0 (enabling it), again allows me to print. However, in each case the lpstat -s report is "bad". IPv4 entries in the avahi-browse report tie in with the ability to print. So looks like IPv6 is playing a role in this, though not in an obviously direct way. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Ralph On 29/07/2019 11:55, Ralph Corderoy wrote: Hi Tim, # apt-get purge cups cups-common cups-daemon # apt-get install cups cups-common cups-daemon If I do this while Wifi connected to AP1, then lpstat on laptop: #lpstat -s no system default destination device for AirPrint_HL_5270DN_Home_golux: implicitclass://AirPrint_HL_5270DN_Home_golux/ device for AirPrint_MP230_golux: implicitclass://AirPrint_MP230_golux/ device for Brother_HL_5270DN_series_golux: implicitclass://Brother_HL_5270DN_series_golux/ device for Canon_MP230_series_golux: implicitclass://Canon_MP230_series_golux/ - all good. If you repeat that purge and install whilst connected to AP0 instead, do you still get the same good lpstat result? That would show it's whatever AP is connected during the starting of CUPS after install that's good rather than some difference between AP0 and AP1 that makes AP1 break things. No, I get the bad lpstat response. Another command to try with the different APs is ‘avahi-browse -at’. I'm guessing the local CUPS is also using mDNS/DNS-SD to discover local network things and this may show if it's CUPS having problems, or discovery in general. While following on from the fresh install on AP0, and still on AP0: # avahi-browse -at + wlp1s0 IPv6 Brother HL-5270DN series @ golux Internet Printer local + wlp1s0 IPv6 Canon MP230 series @ goluxInternet Printer local + wlp1s0 IPv6 AirPrint HL-5270DN-Home @ golux Internet Printer local + wlp1s0 IPv6 AirPrint MP230 @ goluxInternet Printer local + wlp1s0 IPv6 Brother HL-5270DN series @ golux Secure Internet Printer local + wlp1s0 IPv6 Canon MP230 series @ goluxSecure Internet Printer local + wlp1s0 IPv6 golux Remote Disk Management local + wlp1s0 IPv6 Canon MP230 series @ goluxUNIX Printer local + wlp1s0 IPv6 Brother HL-5270DN series @ golux UNIX Printer local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 Web Site local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 _psia._tcp local + wlp1s0 IPv6 UPNP IPC-D120 - 214492577 _CGI._tcp local So looks OK. BTW, following your earlier suggestion, I have IPv6 switched off on AP0. I found a bug in this area, though I don't think it's related. It does suggest this area isn't problem free, though. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928838 Yes, and I was getting this problem before upgrading the laptop to Debian 10. New bit of info: if I connect to AP1 after being on AP0 and go to an application (Evince), I /can/ print. For each printer I get three listings: for the HL5270DN the AirPrint_HL_5270DN_Home_golux and Brother_HL_5270DN_series_golux ones (as reported by lpstat) are greyed out but an additional HL-5270DN-Home one is available and works. Cheers Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Tim, > # apt-get purge cups cups-common cups-daemon > # apt-get install cups cups-common cups-daemon > > If I do this while Wifi connected to AP1, then lpstat on laptop: > > #lpstat -s > no system default destination > device for AirPrint_HL_5270DN_Home_golux: > implicitclass://AirPrint_HL_5270DN_Home_golux/ > device for AirPrint_MP230_golux: implicitclass://AirPrint_MP230_golux/ > device for Brother_HL_5270DN_series_golux: > implicitclass://Brother_HL_5270DN_series_golux/ > device for Canon_MP230_series_golux: > implicitclass://Canon_MP230_series_golux/ > > - all good. If you repeat that purge and install whilst connected to AP0 instead, do you still get the same good lpstat result? That would show it's whatever AP is connected during the starting of CUPS after install that's good rather than some difference between AP0 and AP1 that makes AP1 break things. Another command to try with the different APs is ‘avahi-browse -at’. I'm guessing the local CUPS is also using mDNS/DNS-SD to discover local network things and this may show if it's CUPS having problems, or discovery in general. I found a bug in this area, though I don't think it's related. It does suggest this area isn't problem free, though. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928838 -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-08-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
