Also, startlingly, I seem to have thousands of ipv6 addresses assigned
to enp0s8:
ip addr
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 08:00:27:47:xx:xx brd ff:ff:ff:ff:ff:ff
inet 10.169.110.168/21 brd 10.169.111.255 scope global dynamic
noprefixroute enp0s8
valid_lft 6027sec preferred_lft 6027sec
inet6 2606:b400:818:61:c70:xxxx:xxxx:xxxx/64 scope global temporary dynamic
valid_lft 604796sec preferred_lft 86280sec
inet6 2606:b400:818:61:eece:xxxx:xxxx:xxxx/64 scope global dynamic
mngtmpaddr noprefixroute
valid_lft 2591939sec preferred_lft 604739sec
inet6 2606:b400:818:64:c70:xxxx:xxxx:xxxx/64 scope global temporary dynamic
valid_lft 604796sec preferred_lft 86280sec
inet6 2606:b400:818:64:6745:xxxx:xxxx:xxxx/64 scope global dynamic
mngtmpaddr noprefixroute
valid_lft 2591996sec preferred_lft 604796sec
inet6 2606:b400:818:64:d7:xxxx:xxxx:xxxx0/64 scope global temporary dynamic
valid_lft 604740sec preferred_lft 86224sec
....
....
# ip addr | grep inet6 | cat -n
6294 inet6 2606:b400:818:64:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6295 inet6 2606:b400:818:61:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6296 inet6 2606:b400:818:61:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6297 inet6 2606:b400:818:64:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6298 inet6 2606:b400:818:64:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6299 inet6 2606:b400:818:61:XXXX:XXXX:XXXX:XXXXc/64 scope global
temporary deprecated dynamic
6300 inet6 2606:b400:818:61:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6301 inet6 2606:b400:818:64:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6302 inet6 2606:b400:818:64:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6303 inet6 2606:b400:818:61:XXXX:XXXX:XXXX:XXXX/64 scope global
temporary deprecated dynamic
6304 inet6 fe80::4721:XXXX:XXXX:XXXX/64 scope link noprefixroute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1799265
Title:
avahi-daemon high cpu, unusable networking
Status in Avahi:
New
Status in avahi package in Ubuntu:
Triaged
Bug description:
Currently running Kubuntu 18.10, Dell XPS 13 9350
Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
consistently hampering network performance and using CPU for long
periods of time.
When booting machine from off state, avahi-daemon uses an entire CPU
at max load for approx 10 minutes. During this time, internet
connectivity via wifi is essentially unusable. The wifi connection is
good, but it seems that http transactions are cutoff mid-way so no
webpage is able to load.
When waking from sleep, the avahi-daemon causes similar symptoms, but
with less than 1 full cpu usage, and with somewhat less degraded
network performance, but still quite unusable.
I have never had issues with avahi prior to the 18.10 upgrade, so I am
fairly confident the issue is rooted in that change.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: avahi-daemon 0.7-4ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct 22 10:00:34 2018
InstallationDate: Installed on 2017-07-24 (455 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
LD_PRELOAD=<set>
SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1799265/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
