This issue is not limited to Realtek as it occurs on my system with an
Intel ethernet controller (see
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/comments/9).
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V
DeviceName: Onboard LAN
Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I218-V
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 28
Region 0: Memory at dfd00000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at dfd3c000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at f080 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
I don't have a workaround but the following is what I use to help recover. It
pings my gateway periodically, and if it can't it attempts to restart
networking.
In /etc/crontab:
# check networking
*/10 * * * * root /usr/local/bin/check_reset_network.sh >>
/var/log/check_reset_network.log
/usr/local/bin/check_reset_network.sh:
---[start]-----
#!/bin/bash
echo "`date` $0 starting"
gw=192.168.1.254
echo "Trying to ping gw $gw"
out=$(ping -c 5 $gw 2>&1)
if [ $? -eq 0 ]; then
echo "Success"
else
echo "Failed to ping gw $gw"
echo "Trying again in 20s"
sleep 20
out=$(ping -c 5 $gw 2>&1)
if [ $? -ne 0 ]; then
echo "Failed to ping gw $gw"
echo "Restarting networking"
sudo service network-manager restart
echo "Waiting 20s to recheck network"
sleep 20
out=$(ping -c 5 $gw 2>&1)
if [ $? -eq 0 ]; then
echo "Success; sending mail"
echo "Restarted networking" | mail your_email_addr
else
echo "Failed. You're fucked."
fi
fi
fi
echo "Checking for default route"
out=$(/sbin/ip route | egrep '^default')
if [ $? -eq 0 ]; then
echo "Success"
else
echo "Failed to find default route. Adding it."
/sbin/route add default gw 192.168.1.254
if [ $? -eq 0 ]; then
echo "Success; sending mail"
echo "Added default route" | mail your_email_addr
else
echo "Failed. You're fucked."
fi
fi
echo "`date` $0 done"
---[end]-----
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1586528
Title:
Avahi-daemon withdraws address record
Status in avahi package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
For some reason, if I leave my Ubuntu VM up for a prolonged period of
time the machine will lose connection to the network. ip addr shows
that the nic port no longer has an address and an examination of the
syslog shows this:
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record
for 10.0.2.15 on enp0s3.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast
group on interface enp0s3.IPv4 with address 10.0.2.15.
May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no
longer relevant for mDNS.
for no known reason.
The only reliable way to get the network to come back (that I have
found) is a full reboot.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 27 15:11:34 2016
InstallationDate: Installed on 2015-10-22 (218 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: avahi
UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
