I have checked iptables and there are no rules. # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Looking at the the network traffic leaves me bewildered. There is too much variability to be able to make any sense of what is going on. Sometimes ping works and sometimes not. Restarting avahi-daemon does not appear to make any difference to this apart from the obvious flurry of packets when it does. avahi-resolve-host-name does not behave significantly differently to ping (it does sometimes work, but then so does ping). I'm lost with trying to sort this out though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication Status in avahi package in Ubuntu: Incomplete Bug description: On my local network I find that with 18.04 network name lookups using .local domains no not work unless stimulated by a non-18.04 machine first. This is observed for ssh, http, https and ping, but probably not limited to those. To demonstrate this here is a ping example. ~ $ ping pi.local ping: pi.local: Name or service not known ~ $ ping pi.local ping: pi.local: Name or service not known # At this point head to another machine running 16.04.6 and execute ping pi.local. # This is immediately successful. Then head back to the 18.04 machine. ~ $ ping pi.local PING pi.local (192.168.108.28) 56(84) bytes of data. 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms 64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms ^C --- pi.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7018ms rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms After a couple of minutes, the name resolution fails again, but can be brought back again by following the procedure above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 26 20:04:58 2019 InstallationDate: Installed on 2019-05-22 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1830531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
