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
