Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Ralph On 01/08/2019 13:24, t...@ls83.eclipse.co.uk wrote: Reading through this and comparing router setups, work is not configured as an IGMP proxy, but home is. Will do some more tests with that disabled later today. That appears to fix it. Well, to the extent I was testing. lpstat -s is still coming up with two non-working versions of each printer (Airprint_printername_servername and printermanufacturer_printername_series_server_name). Evince greys these out but also comes up with the plain printername, which works. Libreoffice doesn't. lpq -a finds nothing at all. This may be down to something on the CUPS server, so will compare with the work config. 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 01/08/2019 11:00, Ralph Corderoy wrote: Hi Tim, At work, where I have a similar Draytek router, I see the printers with lpstat -s, no problem. Google found https://www.draytek.co.uk/support/guides/kb-bonjour-setup, Bonjour being another name for mDNS that's involved in service discovery, but Draytek restrict readership to registered users so I've no idea if it's worth reading. :-( I'm registers - the Draytek's can advertise their own services with Bonjour, so that's what that is about. Neither of my routers have this enabled. This answer has lots of interesting detail on what a crazily complex area it is. :-) https://superuser.com/questions/730288/why-do-some-wifi-routers-block-multicast-packets-going-from-wired-to-wireless/733115#733115 Reading through this and comparing router setups, work is not configured as an IGMP proxy, but home is. Will do some more tests with that disabled later today. 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, > At work, where I have a similar Draytek router, I see the printers > with lpstat -s, no problem. Google found https://www.draytek.co.uk/support/guides/kb-bonjour-setup, Bonjour being another name for mDNS that's involved in service discovery, but Draytek restrict readership to registered users so I've no idea if it's worth reading. :-( This answer has lots of interesting detail on what a crazily complex area it is. :-) https://superuser.com/questions/730288/why-do-some-wifi-routers-block-multicast-packets-going-from-wired-to-wireless/733115#733115 -- 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
Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Ralph On 31/07/2019 22:14, t...@ls83.eclipse.co.uk wrote: Couple of things I'll try here. I see the router has a recent firmware update which I'll flash. And I have a similar Draytek router at work. I'll see if I get the same issues there. Updated the router. I do now sometimes see the printers when connected to AP0, but it's not consistent. At work, where I have a similar Draytek router, I see the printers with lpstat -s, no problem. Next steps will be a detailed comparison of the home/work CUPS server configs, switch off AP1 and AP2, and compare router configs. 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 31/07/2019 11:30, Ralph Corderoy wrote: Hi Tim, Basically, it's a toggle setting and toggling the IPv6 resets the router and I get IPv4 entries in the avahi-browse response (IPv6 enabled or disabled). Switching to one of the other AP's, and back again, and I just get IPv6 entries appearing, whether IPv6 is enabled or disabled on AP0 (which is definitely strange). Could it be that IPv6 responses are being remembered when talking to a non-AP0 but then can't be used with AP0? If the laptop temporarily disabled IPv6 on the Wi-Fi interface then it would be using IPv4 to all APs? Something like this should do. It's temporary, resetting to default on reboot. i=wls34# Change to suit. ip a s dev $i # Show the ‘before’. sysctl net.ipv6.conf.$i.disable_ipv6 sudo -i sysctl net.ipv6.conf.$i.disable_ipv6=1 ip a s dev $i Just tried this, important to rerun after AP reconnect, and it sheds some light on the issue. Connected to AP0 with IPv6 disabled on the laptop and on AP0, I get no response to avahi-browse -at That's to be expected following the earlier test result. However, it's good to confirm it. So I guess that tells us that Avahi browsing is not getting through that router on IPv4, and that CUPS is having a problem with Avahi on IPv6? Couple of things I'll try here. I see the router has a recent firmware update which I'll flash. And I have a similar Draytek router at work. I'll see if I get the same issues there. 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, > Basically, it's a toggle setting and toggling the IPv6 resets the > router and I get IPv4 entries in the avahi-browse response (IPv6 > enabled or disabled). Switching to one of the other AP's, and back > again, and I just get IPv6 entries appearing, whether IPv6 is enabled > or disabled on AP0 (which is definitely strange). Could it be that IPv6 responses are being remembered when talking to a non-AP0 but then can't be used with AP0? If the laptop temporarily disabled IPv6 on the Wi-Fi interface then it would be using IPv4 to all APs? Something like this should do. It's temporary, resetting to default on reboot. i=wls34# Change to suit. ip a s dev $i # Show the ‘before’. sysctl net.ipv6.conf.$i.disable_ipv6 sudo -i sysctl net.ipv6.conf.$i.disable_ipv6=1 ip a s dev $i -- 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
Re: [Dorset] CUPS browsing fails on Wifi access point
Hi Ralph On 30/07/2019 12:41, Ralph Corderoy wrote: Hi Tim, I'm compiling a summary of your results. # avahi-browse -at + wlp1s0 IPv6 Brother HL-5270DN series @ golux Internet Printer 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), Am I reading that correctly? Despite IPv6 being disabled on AP0, when connected to it avahi-browse shows IPv6 results? It then goes on to say IPv6 is then altered to be disabled on that AP, but it already was? Or are some 4/6 en/dis mixed up? :-) They are a bit mixed up. Basically, it's a toggle setting and toggling the IPv6 resets the router and I get IPv4 entries in the avahi-browse response (IPv6 enabled or disabled). Switching to one of the other AP's, and back again, and I just get IPv6 entries appearing, whether IPv6 is enabled or disabled on AP0 (which is definitely strange). I did find https://wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem#The_CUPS_Error_Log that describes how to get more information out of CUPS. I'll take a look. 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, I'm compiling a summary of your results. > > # avahi-browse -at > > + wlp1s0 IPv6 Brother HL-5270DN series @ golux Internet Printer 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), Am I reading that correctly? Despite IPv6 being disabled on AP0, when connected to it avahi-browse shows IPv6 results? It then goes on to say IPv6 is then altered to be disabled on that AP, but it already was? Or are some 4/6 en/dis mixed up? :-) I did find https://wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem#The_CUPS_Error_Log that describes how to get more information out of CUPS. -- 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
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
[Dorset] CUPS browsing fails on Wifi access point
Hi I have a long-standing issue with connecting to a CUPS server on a network which has 3 Wifi access points. CUPS server is running Debian 9, tests are with a Debian 10 laptop. Starting with a fresh re-install of CUPS on the laptop: # 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. Disconnect from AP1 and connect to AP0 and I get: # lpstat -s no system default destination device for AirPrint_HL_5270DN_Home_golux: ///dev/null device for AirPrint_MP230_golux: ///dev/null device for Brother_HL_5270DN_series_golux: ///dev/null device for Canon_MP230_series_golux: ///dev/null From then on it's game over. Can reconnect to AP1, restart CUPS on the laptop but printers showing ///dev/null. Ralph - I know we discussed this a couple of months back - however this condition where the printers are permanently lost is new, I'm guessing following the upgrade to Debian 10 (CUPS 2.2.10). 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
