IPv4 Address Lost 8 Days After Previous DHCP Allocation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired ethernet connection to my office's network. This happened this morning and previously happened 8 days ago.
The network uses a Windows Small Business Server as its main Active Domain Domain Controller which includes a DHCP service. There are several other Ubuntu 16.04 machines on the network that do not seem to experience this issue. This is an IPv4 only network, no IPv6 services are configures and IPv6 is disabled on most machines.
My PC has two wired network ports. One connects to the office network and uses DHCP to get an IPv4 address. The other connects to a switch on my desk that has test equipment connected to it and uses a static IPv4 address.
I have the output from:
ll /var/lib/
nmcli -p c
nmcli -p c show TN\ Wired
Taken; after the renewal of the address eight days ago, this morning before I "Disconnect"ed the connection from the drop down menu and after I reconnected and an IPv4 address was re-acquired. If any of this would be helpful, please let me know and I shall post it.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 31 09:55:10 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-03-12 (690 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
default via 172.16.20.21 dev eth0 proto static metric 100
169.254.0.0/16 dev eth1 scope link metric 1000
172.16.20.0/24 dev eth0 proto kernel scope link src 172.16.20.67 metric 100
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.10 metric 100
IwConfig:
lo no wireless extensions.
eth1 no wireless extensions.
eth0 no wireless extensions.
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
RfKill:
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
eth0 ethernet connected /org/freedeskto
eth1 ethernet connected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.2 connected started full enabled enabled enabled enabled enabled
Status changed to 'Confirmed' because the bug affects multiple users.