Skip to content
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.

avahi hostname conflict #8

Open
DanLipsitt opened this issue Jul 23, 2015 · 0 comments
Open

avahi hostname conflict #8

DanLipsitt opened this issue Jul 23, 2015 · 0 comments

Comments

@DanLipsitt
Copy link

I am experiencing an Avahi bug that appears to be triggered (perhaps indirectly) by netconnectd on a debian jessie system.

Sometimes when the wifi connection is lost, avahi experiences a hostname conflict with itself when netconnectd brings the connection back up. In other words, avahi thinks that the hostname is taken, even though it isn't. Avahi then increments the hostname (e.g. from example.local to example-2.local, which makes the system unreachable unless you know what's going on.

I can sometimes trigger this bug by running ifdown wlan0, but it doesn't work every time.

I have a suspicion that this has something to do with the sequence in which netconnectd restarts things. Perhaps dnsmasq is caching things in a way it shouldn't, and needs to be reset.

Below is what the system logs look like when this bug occurs. I am investigating this issue, but if you have any insight it would be appreciated.

19:45:54 netconnectd[325]: 2015-07-22 19:45:54,740 - netconnectd.server - INFO - Waiting for connection on socket...
19:45:54 netconnectd[325]: 2015-07-22 19:45:54,746 - netconnectd.server - INFO - Recv: '{"status":{}}\x00'
19:45:54 netconnectd[325]: 2015-07-22 19:45:54,809 - netconnectd.server - INFO - Send: {"result":{"connections":{"ap":false,"wifi":true,"wired":false},"devs":["wlan0"],"wifi":{"valid_config":true,"current_address":"0A:18:D6:87:C5:DA","present":true,"current_ssid":"Type A Machines"},"link":true}}
19:45:54 netconnectd[325]: 2015-07-22 19:45:54,818 - netconnectd.server - INFO - Waiting for connection on socket...
19:45:56 kernel: [ 1741.697518] cfg80211: Calling CRDA to update world regulatory domain
19:47:26 netconnectd[325]: 2015-07-22 19:47:26,612 - netconnectd.server - INFO - Link down, got a configured wifi connection, trying that
19:47:26 rsyslogd-2007: action 'action 17' suspended, next retry is Wed  19:48:56 2015 [try http://www.rsyslog.com/e/2007 ]
19:47:26 dhclient: Killed old client process
19:47:27 dhclient: Internet Systems Consortium DHCP Client 4.3.1
19:47:27 dhclient: Copyright 2004-2014 Internet Systems Consortium.
19:47:27 dhclient: All rights reserved.
19:47:27 dhclient: For info, please visit https://www.isc.org/software/dhcp/
19:47:27 dhclient: 
19:47:27 dhclient: Listening on LPF/wlan0/14:cc:20:27:3e:17
19:47:27 dhclient: Sending on   LPF/wlan0/14:cc:20:27:3e:17
19:47:27 dhclient: Sending on   Socket/fallback
19:47:27 dhclient: DHCPRELEASE on wlan0 to 172.16.0.1 port 67
19:47:27 avahi-daemon[352]: Withdrawing address record for 172.16.0.115 on wlan0.
19:47:27 avahi-daemon[352]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 172.16.0.115.
19:47:27 avahi-daemon[352]: Interface wlan0.IPv4 no longer relevant for mDNS.
19:47:27 wpa_supplicant[678]: wlan0: CTRL-EVENT-DISCONNECTED bssid=0a:18:d6:87:c5:da reason=3 locally_generated=1
19:47:27 avahi-daemon[352]: Interface wlan0.IPv6 no longer relevant for mDNS.
19:47:27 avahi-daemon[352]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fdc8:235a:9db8:0:16cc:20ff:fe27:3e17.
19:47:27 avahi-daemon[352]: Withdrawing address record for fdc8:235a:9db8:0:16cc:20ff:fe27:3e17 on wlan0.
19:47:28 wpa_supplicant[678]: wlan0: CTRL-EVENT-TERMINATING
19:47:28 wpa_supplicant[1148]: Successfully initialized wpa_supplicant
19:47:28 kernel: [ 1833.913336] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
19:47:29 dhclient: Internet Systems Consortium DHCP Client 4.3.1
19:47:29 dhclient: Copyright 2004-2014 Internet Systems Consortium.
19:47:29 dhclient: All rights reserved.
19:47:29 dhclient: For info, please visit https://www.isc.org/software/dhcp/
19:47:29 dhclient: 
19:47:29 dhclient: Listening on LPF/wlan0/14:cc:20:27:3e:17
19:47:29 dhclient: Sending on   LPF/wlan0/14:cc:20:27:3e:17
19:47:29 dhclient: Sending on   Socket/fallback
19:47:29 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
19:47:30 wpa_supplicant[1149]: wlan0: SME: Trying to authenticate with 0a:18:d6:87:c5:da (SSID='Type A Machines' freq=2462 MHz)
19:47:30 kernel: [ 1835.790388] wlan0: authenticate with 0a:18:d6:87:c5:da
19:47:30 kernel: [ 1835.828505] wlan0: send auth to 0a:18:d6:87:c5:da (try 1/3)
19:47:30 wpa_supplicant[1149]: wlan0: Trying to associate with 0a:18:d6:87:c5:da (SSID='Type A Machines' freq=2462 MHz)
19:47:30 kernel: [ 1835.832094] wlan0: authenticated
19:47:30 kernel: [ 1835.837040] wlan0: associate with 0a:18:d6:87:c5:da (try 1/3)
19:47:30 kernel: [ 1835.841575] wlan0: RX AssocResp from 0a:18:d6:87:c5:da (capab=0x31 status=0 aid=18)
19:47:30 kernel: [ 1835.843884] wlan0: associated
19:47:30 kernel: [ 1835.844018] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
19:47:30 wpa_supplicant[1149]: wlan0: Associated with 0a:18:d6:87:c5:da
19:47:30 wpa_supplicant[1149]: wlan0: WPA: Key negotiation completed with 0a:18:d6:87:c5:da [PTK=CCMP GTK=CCMP]
19:47:30 wpa_supplicant[1149]: wlan0: CTRL-EVENT-CONNECTED - Connection to 0a:18:d6:87:c5:da completed [id=0 id_str=]
19:47:31 avahi-daemon[352]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::16cc:20ff:fe27:3e17.
19:47:31 avahi-daemon[352]: New relevant interface wlan0.IPv6 for mDNS.
19:47:31 avahi-daemon[352]: Registering new address record for fe80::16cc:20ff:fe27:3e17 on wlan0.*.
19:47:32 avahi-daemon[352]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::16cc:20ff:fe27:3e17.
19:47:32 avahi-daemon[352]: Joining mDNS multicast group on interface wlan0.IPv6 with address fdc8:235a:9db8:0:16cc:20ff:fe27:3e17.
19:47:32 avahi-daemon[352]: Registering new address record for fdc8:235a:9db8:0:16cc:20ff:fe27:3e17 on wlan0.*.
19:47:32 avahi-daemon[352]: Withdrawing address record for fe80::16cc:20ff:fe27:3e17 on wlan0.
19:47:32 avahi-daemon[352]: Withdrawing address record for 192.168.7.2 on usb0.
19:47:32 avahi-daemon[352]: Withdrawing workstation service for usb0.
19:47:32 avahi-daemon[352]: Withdrawing workstation service for wlan0.
19:47:32 avahi-daemon[352]: Withdrawing workstation service for eth0.
19:47:32 avahi-daemon[352]: Withdrawing workstation service for lo.
19:47:32 avahi-daemon[352]: Host name conflict, retrying with series1-1139
19:47:32 avahi-daemon[352]: Registering new address record for 192.168.7.2 on usb0.IPv4.
19:47:32 avahi-daemon[352]: Registering new address record for fdc8:235a:9db8:0:16cc:20ff:fe27:3e17 on wlan0.*.
19:47:32 avahi-daemon[352]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
19:47:33 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
19:47:33 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
19:47:33 dhclient: DHCPOFFER from 172.16.0.1
19:47:33 dhclient: DHCPACK from 172.16.0.1
19:47:33 avahi-daemon[352]: Joining mDNS multicast group on interface wlan0.IPv4 with address 172.16.0.115.
19:47:33 avahi-daemon[352]: New relevant interface wlan0.IPv4 for mDNS.
19:47:33 avahi-daemon[352]: Registering new address record for 172.16.0.115 on wlan0.IPv4.
19:47:33 dhclient: bound to 172.16.0.115 -- renewal in 8258 seconds.
19:47:33 netconnectd[325]: 2015-07-22 19:47:33,877 - netconnectd.server - INFO - Connected to wifi [u'Type A Machines']
19:47:34 avahi-daemon[352]: Server startup complete. Host name is series1-1139.local. Local service cookie is 961968340.
DanLipsitt added a commit to DanLipsitt/netconnectd that referenced this issue Jul 23, 2015
@DanLipsitt
Workaround: restart avahi
a5edf68 
Avahi sometimes experiences a spurious hostname conflict when
netconnectd restarts. This causes the avahi hostname to be incremented.
See foosel#8 for details.
@callegar callegar mentioned this issue Apr 26, 2017
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DanLipsitt