[Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-06-01 Thread Dan Kortschak
I don't claim that the packets are not being sent, but rather that the system does not work as expected out of the box when it did in a previous LTR. I don't really care what package is the cause except to help get the problem fixed. I have done as much debugging of this as I am capable since

[Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-05-27 Thread Dan Kortschak
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

[Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-05-26 Thread Dan Kortschak
Before I get a chance to look into this later today, I'd like to note that the network device is not firewalling those packets since a few days ago before I installed 18.04 on this machine it was behaving as expected and the 16.04 machine mentioned in the OP is not being blocked (it is on a

[Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-05-26 Thread Trent Lloyd
The most likely cause for this is that you have packets outbound on port 5353 firewalled either locally or on your network device. When another host pings the address, the responses are sent via multicast and Avahi caches that response, and so can then use it without having to transmit a packet.

[Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-05-26 Thread Dan Kortschak
~ $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830531 Title: .local domain look ups do not trigger name publication To