avahi-daemon repeatedly registers/withdraws address рекорд causing network failures

I am using Ubuntu 15.10 using an Ethernet connection to my кабель model router. I have not customized the network set up in any way after installing Ubuntu. гve noticed that after about 12 to 24 hours after booting up, Интернет Ubuntu starts to drop connections. Usually I notice this after webpages fail to похвалите images or CSS поля. When this happens I notice that the /var/syslog is filled with entries like this:

Jan  8 05:26:40 46lbs avahi-daemon[730]: Registering new address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.*.
Jan  8 05:26:40 46lbs avahi-daemon[730]: Withdrawing address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.
Jan  8 05:26:43 46lbs avahi-daemon[730]: Registering new address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.*.
Jan  8 05:26:43 46lbs avahi-daemon[730]: Withdrawing address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.
Jan  8 05:26:46 46lbs avahi-daemon[730]: Registering new address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.*.
Jan  8 05:26:46 46lbs avahi-daemon[730]: Withdrawing address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.
Jan  8 05:26:49 46lbs avahi-daemon[730]: Registering new address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.*.
Jan  8 05:26:49 46lbs avahi-daemon[730]: Withdrawing address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.
Jan  8 05:26:52 46lbs avahi-daemon[730]: Registering new address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.*.
Jan  8 05:26:52 46lbs avahi-daemon[730]: Withdrawing address record for 2605:e000:850e:8800:d9cb:5166:bac1:61d2 on eth0.

Usually I хан нормальная Интернет перекаверверсия использовал by disconnecting the wired connection using the networking icon in the Ubuntu toolbar and then reconnecting. However, this is troublesome. I would like to keep the avahi-daemon for the purposes of discovery. Does anyone know how to stop this behavior? Рекордный For the, here is the output of my ifconfig

eth0      Link encap:Ethernet  HWaddr 08:62:66:7c:ea:35  
      inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
      inet6 addr: 2605:e000:850e:8800:8729:2a19:e7c8:5738/128 Scope:Global
      inet6 addr: fe80::a62:66ff:fe7c:ea35/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:4638380 errors:0 dropped:9 overruns:0 frame:0
      TX packets:2164811 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:5378789738 (5.3 GB)  TX bytes:231746518 (231.7 MB)
      Interrupt:20 Memory:fb200000-fb220000 

lo        Link encap:Local Loopback  
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:40049332 errors:0 dropped:0 overruns:0 frame:0
      TX packets:40049332 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0 
      RX bytes:2898153546 (2.8 GB)  TX bytes:2898153546 (2.8 GB)
3
задан 8 January 2016 в 18:46

1 ответ

Я имел ту же проблему и нашел Ваш вопрос при поиске ответа. Я также нашел этот вопрос на serverfault:

, Если Ваш сервер DNS, что этот сервер использование имеет .local домен затем avahi, не будет работать. См. http://avahi.org/wiki/AvahiAndUnicastDotLocal для большего количества информации об этом.

, Когда я удалил свой .local домен из моего сервера DNS, проблема ушла. Надо надеяться, Вы имеете тот же успех.

1
ответ дан 1 December 2019 в 17:34

Другие вопросы по тегам:

Похожие вопросы: