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
