December 8, 20178 yr I was looking through my syslog and saw a bunch of records that seem to indicate IPv6 being on. In my settings I have it set to IPv4 only, so I was wondering whats causing those messages to come up. Diags attached example of messages Dec 8 16:37:58 Tower avahi-daemon[17573]: Interface vethcf88fad.IPv6 no longer relevant for mDNS. Dec 8 16:37:58 Tower avahi-daemon[17573]: Leaving mDNS multicast group on interface vethcf88fad.IPv6 with address fe80::1848:5eff:fe94:4be2. Dec 8 16:37:58 Tower kernel: docker0: port 2(vethcf88fad) entered disabled state Dec 8 16:37:58 Tower kernel: device vethcf88fad left promiscuous mode Dec 8 16:37:58 Tower kernel: docker0: port 2(vethcf88fad) entered disabled state Dec 8 16:37:58 Tower avahi-daemon[17573]: Withdrawing address record for fe80::1848:5eff:fe94:4be2 on vethcf88fad. Dec 8 16:38:00 Tower kernel: docker0: port 2(veth631ea02) entered blocking state Dec 8 16:38:00 Tower kernel: docker0: port 2(veth631ea02) entered disabled state Dec 8 16:38:00 Tower kernel: device veth631ea02 entered promiscuous mode Dec 8 16:38:00 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth631ea02: link is not ready Dec 8 16:38:00 Tower kernel: docker0: port 2(veth631ea02) entered blocking state Dec 8 16:38:00 Tower kernel: docker0: port 2(veth631ea02) entered forwarding state Dec 8 16:38:00 Tower kernel: eth0: renamed from veth1cdc40a Dec 8 16:38:00 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth631ea02: link becomes ready Dec 8 16:38:01 Tower avahi-daemon[17573]: Joining mDNS multicast group on interface veth631ea02.IPv6 with address fe80::2c15:63ff:fe58:2a29. Dec 8 16:38:01 Tower avahi-daemon[17573]: New relevant interface veth631ea02.IPv6 for mDNS. Dec 8 16:38:01 Tower avahi-daemon[17573]: Registering new address record for fe80::2c15:63ff:fe58:2a29 on veth631ea02.*. tower-diagnostics-20171208-1759.zip
December 9, 20178 yr That's normal. All interfaces get an IPv6 link local address, even when not used.
Archived
This topic is now archived and is closed to further replies.