[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: avahi-daemon allow/deny interfaces question



Hi Ramesh,

Please could you post some example daemon.log entries and any surrounding entries that seem related?

Also is there anything in

/var/log/syslog


that seems to relate?

Perhaps

$ sudo cat /var/log/syslog | grep x

where x = the interface name concerned.

Thanks,
Gareth

Hi Gareth,

 This is what I find in daemon.log
Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for fe80::daeb:97ff:febf:5ad0 on enxd8eb97bf5ad0. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for 192.168.1.124 on enxd8eb97bf5ad0.

After this happens, most of my net access goes down. Firefox cannot get to google.com/youtube.com. DNS lookup also returns nothing for external hosts. I see similar messages on /var/log/syslog also


Jul 12 18:27:16 new-yoda avahi-daemon[441]: Interface enxd8eb97bf5ad0.IPv6 no longer relevant for mDNS. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Leaving mDNS multicast group on interface enxd8eb97bf5ad0.IPv6 with address fe80::daeb:97ff:febf:5ad0. Jul 12 18:27:16 new-yoda dhclient[550]: receive_packet failed on enxd8eb97bf5ad0: Network is down Jul 12 18:27:16 new-yoda avahi-daemon[441]: Interface enxd8eb97bf5ad0.IPv4 no longer relevant for mDNS. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Leaving mDNS multicast group on interface enxd8eb97bf5ad0.IPv4 with address 192.168.1.124. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for fe80::daeb:97ff:febf:5ad0 on enxd8eb97bf5ad0. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for 192.168.1.124 on enxd8eb97bf5ad0.
Jul 12 18:27:17 new-yoda kernel: [ 8560.412306] asix 1-1:1.0 eth0: register 'asix' at usb-0000:00:14.0-1, ASIX AX88772 USB 2.0 Ethernet, d8:eb:97:bf:5a:d0 Jul 12 18:27:17 new-yoda NetworkManager[448]: <info> [1657668437.0609] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/6) Jul 12 18:27:17 new-yoda systemd-udevd[1494]: Using default interface naming scheme 'v247'. Jul 12 18:27:17 new-yoda systemd-udevd[1494]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 12 18:27:17 new-yoda kernel: [ 8560.449674] asix 1-1:1.0 enxd8eb97bf5ad0: renamed from eth0 Jul 12 18:27:17 new-yoda NetworkManager[448]: <info> [1657668437.1103] device (eth0): interface index 5 renamed iface from 'eth0' to 'enxd8eb97bf5ad0' Jul 12 18:27:17 new-yoda systemd-udevd[1494]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 12 18:27:19 new-yoda ModemManager[489]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin

Looks like kernel finds usb NIC again and tries to do something? Since dhclient is not aware, it does not know how to handle. I get this from dhclient for the *next* DHCPDISCOVER/REQUEST

Jul 12 19:45:04 new-yoda dhclient[550]: DHCPREQUEST for 192.168.1.124 on enxd8eb97bf5ad0 to 192.168.1.254 port 67 Jul 12 19:45:04 new-yoda dhclient[550]: send_packet: Network is unreachable Jul 12 19:45:04 new-yoda dhclient[550]: send_packet: please consult README file regarding broadcast address.

Hope you can find something useful. For now, I simply edited avahi-daemon.conf and denied this interface as one not to be observed/managed. That fixed the part of the problem. Other issue is reported in one of my followup.

Regards
Ramesh


Reply to: