[Desktop-packages] [Bug 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation

2018-05-03 Thread James Cobban
I had this issue yesterday on 17.10.  The IPV4 address for my Ethernet
interface vanished.  I could not find any option in the network portion
of settings to ask the DHCP for the IP address, and sudo service
network-manager restart did not recover, so I rebooted the system.  This
is obviously an extremely rare situation and I do not know how to
reproduce it.  If there is no notification that the network manager can
register for to detect this situation automatically then there should be
a reinitialize button in the network settings GUI.

-- 
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/1660574

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

Status in network-manager package in Ubuntu:
  Confirmed

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/NetworkManager
   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.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  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:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+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


[Desktop-packages] [Bug 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation

2018-05-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
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/1660574

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

Status in network-manager package in Ubuntu:
  Confirmed

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/NetworkManager
   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.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  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:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+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