Re: Strange issue with dhcpd and laster kernel upgrade?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Booted machine with latest kernel and hardcoded (Works) 
Changed it back to Automatic, and doesn't Work.
Reboot machine with the same auto setting, with previous kernel (Works).

====== hard coded results ifconfig and long journalctl output ===
ifconfig output
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.106  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::373a:37f3:ca88:ab02  prefixlen 64  scopeid 0x20<link>
        ether 00:19:21:e9:4d:0e  txqueuelen 1000  (Ethernet)
        RX packets 66  bytes 37983 (37.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 169  bytes 20160 (19.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 120  bytes 10892 (10.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 120  bytes 10892 (10.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.124.1  netmask 255.255.255.0  broadcast 192.168.124.255
        ether 52:54:00:8e:b1:b3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

-- Logs begin at Thu 2017-05-25 15:19:59 ChST, end at Sat 2018-06-02 
11:02:01 ChST. --
Jun 02 10:57:10 amdgcc3.dyndns.org systemd[1]: Starting Network 
Manager...
Jun 02 10:57:10 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901030.9932] NetworkManager (version 1.8.6-1.fc27) is starting... (for 
the first time)
Jun 02 10:57:10 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901030.9983] Read config: 
/etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
Jun 02 10:57:11 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901031.0961] manager[0x55bdeae2e140]: monitoring kernel firmware 
directory '/lib/firmware'.
Jun 02 10:57:11 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901031.1168] policy: hostname management mode: default
Jun 02 10:57:11 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901031.1181] dns-mgr[0x55bdeae3a970]: init: dns=default, 
rc-manager=symlink
Jun 02 10:57:11 amdgcc3.dyndns.org systemd[1]: Started Network Manager.
Jun 02 10:57:12 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901032.6291] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list. 
(/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
Jun 02 10:57:12 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901032.6485] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To 
report bugs please use the NetworkManager mailing list. 
(/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so)
Jun 02 10:57:12 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901032.6487] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list.
Jun 02 10:57:12 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901032.6511] ifcfg-rh: new connection 
/etc/sysconfig/network-scripts/ifcfg-Wired_connection_1 
(f596494f-e725-375c-ae81-ca016ce88e49,"Wired connection 1")
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4076] settings: hostname: using hostnamed
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4109] settings: hostname changed from (none) to 
"amdgcc3.dyndns.org"
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4527] dhcp-init: Using DHCP client 'dhclient'
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4528] manager: rfkill: WiFi enabled by radio killswitch; enabled 
by state file
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4529] manager: rfkill: WWAN enabled by radio killswitch; 
enabled by state file
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4531] manager: Networking is enabled by state file
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4723] Loaded device plugin: NMBondDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4723] Loaded device plugin: NMBridgeDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4724] Loaded device plugin: NMDummyDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4724] Loaded device plugin: NMEthernetDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4725] Loaded device plugin: NMInfinibandDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4725] Loaded device plugin: NMIPTunnelDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4726] Loaded device plugin: NMMacsecDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4796] Loaded device plugin: NMMacvlanDeviceFactory 
(internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4798] Loaded device plugin: NMTunDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4798] Loaded device plugin: NMVethDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4799] Loaded device plugin: NMVlanDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.4800] Loaded device plugin: NMVxlanDeviceFactory (internal)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.5376] Loaded device plugin: NMAtmManager 
(/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.7609] Loaded device plugin: NMBluezManager 
(/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.8532] Loaded device plugin: NMTeamFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Jun 02 10:57:15 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901035.9446] Loaded device plugin: NMWifiFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.0246] Loaded device plugin: NMWwanFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.0448] device (lo): link connected
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.0492] manager: (lo): new Generic device 
(/org/freedesktop/NetworkManager/Devices/1)
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.0544] manager: (enp3s0): new Ethernet device 
(/org/freedesktop/NetworkManager/Devices/2)
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.0611] device (enp3s0): state change: unmanaged -> 
unavailable (reason 'managed', internal state 'external')
Jun 02 10:57:16 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901036.5872] ModemManager available in the bus
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5444] device (enp3s0): link connected
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5558] device (enp3s0): state change: unavailable -> 
disconnected (reason 'carrier-changed', internal state 'managed')
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5638] policy: auto-activating connection 'Wired connection 1'
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5698] device (enp3s0): Activation: starting connection 'Wired 
connection 1' (f596494f-e725-375c-ae81-ca016ce88e49)
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5738] device (enp3s0): state change: disconnected -> prepare 
(reason 'none', internal state 'managed')
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5768] manager: NetworkManager state is now CONNECTING
Jun 02 10:57:18 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901038.5869] device (enp3s0): state change: prepare -> config (reason 
'none', internal state 'managed')
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <warn>  
[1527901048.5906] firewall: [0x55bdeaf07c80,change:"enp3s0"]: complete: 
request failed (Timeout was reached)
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.5913] device (enp3s0): state change: config -> ip-config 
(reason 'none', internal state 'managed')
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.7192] device (enp3s0): state change: ip-config -> ip-check 
(reason 'none', internal state 'managed')
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8028] device (enp3s0): state change: ip-check -> secondaries 
(reason 'none', internal state 'managed')
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8033] device (enp3s0): state change: secondaries -> activated 
(reason 'none', internal state 'managed')
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8071] manager: NetworkManager state is now 
CONNECTED_LOCAL
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8638] manager: NetworkManager state is now 
CONNECTED_SITE
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8641] policy: set 'Wired connection 1' (enp3s0) as default for 
IPv4 routing and DNS
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8829] device (enp3s0): Activation: successful, device activated.
Jun 02 10:57:28 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901048.8952] manager: startup complete
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.2123] manager: (virbr0): new Bridge device 
(/org/freedesktop/NetworkManager/Devices/3)
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.2829] manager: (virbr0-nic): new Tun device 
(/org/freedesktop/NetworkManager/Devices/4)
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.3800] device (virbr0-nic): state change: unmanaged -> 
unavailable (reason 'connection-assumed', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.3828] device (virbr0-nic): state change: unavailable -> 
disconnected (reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8050] device (virbr0): state change: unmanaged -> unavailable 
(reason 'connection-assumed', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8196] ifcfg-rh: add connection in-memory 
(006f8d67-200c-4925-a652-c67ec85d74ac,"virbr0")
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8253] device (virbr0): state change: unavailable -> 
disconnected (reason 'connection-assumed', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8322] device (virbr0): Activation: starting connection 'virbr0' 
(006f8d67-200c-4925-a652-c67ec85d74ac)
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8358] device (virbr0): state change: disconnected -> prepare 
(reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8404] device (virbr0): state change: prepare -> config (reason 
'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8490] keyfile: add connection in-memory 
(eeb3729e-e2b5-4f82-8572-233fca4a9692,"virbr0-nic")
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8549] device (virbr0-nic): Activation: starting connection 
'virbr0-nic' (eeb3729e-e2b5-4f82-8572-233fca4a9692)
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8550] device (virbr0): state change: config -> ip-config (reason 
'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8622] device (virbr0-nic): state change: disconnected -> 
prepare (reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8755] device (virbr0): state change: ip-config -> ip-check 
(reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8919] device (virbr0-nic): state change: prepare -> config 
(reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8949] device (virbr0-nic): state change: config -> ip-config 
(reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.8998] device (virbr0): bridge port virbr0-nic was attached
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9007] device (virbr0-nic): Activation: connection 'virbr0-nic' 
enslaved, continuing activation
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9075] device (virbr0-nic): state change: ip-config -> 
secondaries (reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9138] device (virbr0-nic): state change: secondaries -> 
activated (reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9543] device (virbr0-nic): Activation: successful, device 
activated.
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9621] device (virbr0): state change: ip-check -> secondaries 
(reason 'none', internal state 'external')
Jun 02 10:57:31 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901051.9744] device (virbr0): state change: secondaries -> activated 
(reason 'none', internal state 'external')
Jun 02 10:57:32 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901052.0206] device (virbr0): Activation: successful, device activated.
Jun 02 10:57:32 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901052.0300] device (virbr0-nic): state change: activated -> 
unmanaged (reason 'connection-assumed', internal state 'external')
Jun 02 10:57:32 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901052.0314] device (virbr0): bridge port virbr0-nic was detached
Jun 02 10:57:32 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901052.0314] device (virbr0-nic): released from master device virbr0
===== End ====

After Changing the settings to automatic
Doesn't get an IPv4 address??

=== ifconfig can journalctl output  Not Working ====
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::373a:37f3:ca88:ab02  prefixlen 64  scopeid 0x20<link>
        ether 00:19:21:e9:4d:0e  txqueuelen 1000  (Ethernet)
        RX packets 163  bytes 71980 (70.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 375  bytes 51022 (49.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 138  bytes 12686 (12.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 138  bytes 12686 (12.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.124.1  netmask 255.255.255.0  broadcast 192.168.124.255
        ether 52:54:00:8e:b1:b3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

-- Logs begin at Thu 2017-05-25 15:19:59 ChST, end at Sat 2018-06-02 
11:05:22 ChST. --

Deleted lines from earlier access

Jun 02 11:02:23 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901343.8348] manager: NetworkManager state is now 
CONNECTED_GLOBAL
Jun 02 11:03:00 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901380.9013] audit: op="connection-update" 
uuid="f596494f-e725-375c-ae81-ca016ce88e49" name="Wired connection 1" 
args="connection.timestamp,ipv4.gateway,ipv4.addresses,ipv4.ignore-auto-d
ns,ipv4.method" pid=3799 uid=1000 result="success"
Jun 02 11:03:05 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901385.5979] device (enp3s0): state change: activated -> deactivating 
(reason 'user-requested', internal state 'managed')
Jun 02 11:03:05 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901385.7166] manager: NetworkManager state is now 
CONNECTED_LOCAL
Jun 02 11:03:05 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901385.7233] audit: op="device-disconnect" interface="enp3s0" 
ifindex=2 pid=3799 uid=1000 result="success"
Jun 02 11:03:05 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901385.7412] device (enp3s0): state change: deactivating -> 
disconnected (reason 'user-requested', internal state 'managed')
Jun 02 11:03:08 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901388.9759] device (enp3s0): Activation: starting connection 'Wired 
connection 1' (f596494f-e725-375c-ae81-ca016ce88e49)
Jun 02 11:03:08 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901388.9830] audit: op="connection-activate" 
uuid="f596494f-e725-375c-ae81-ca016ce88e49" name="Wired connection 1" 
pid=3799 uid=1000 result="success"
Jun 02 11:03:08 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901388.9851] device (enp3s0): state change: disconnected -> prepare 
(reason 'none', internal state 'managed')
Jun 02 11:03:08 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901388.9877] manager: NetworkManager state is now CONNECTING
Jun 02 11:03:08 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901388.9923] device (enp3s0): state change: prepare -> config (reason 
'none', internal state 'managed')
Jun 02 11:03:09 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901389.1974] device (enp3s0): state change: config -> ip-config 
(reason 'none', internal state 'managed')
Jun 02 11:03:09 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901389.2029] dhcp4 (enp3s0): activation: beginning transaction 
(timeout in 45 seconds)
Jun 02 11:03:09 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901389.2772] dhcp4 (enp3s0): dhclient started with pid 4040
Jun 02 11:03:09 amdgcc3.dyndns.org dhclient[4040]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x3602a421)
Jun 02 11:03:12 amdgcc3.dyndns.org dhclient[4040]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x3602a421)
Jun 02 11:03:17 amdgcc3.dyndns.org dhclient[4040]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x3602a421)
Jun 02 11:03:31 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x953b7025)
Jun 02 11:03:36 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 7 (xid=0x953b7025)
Jun 02 11:03:43 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x953b7025)
Jun 02 11:03:52 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 18 (xid=0x953b7025)
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <warn>  
[1527901434.3499] dhcp4 (enp3s0): request timed out
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3501] dhcp4 (enp3s0): state changed unknown -> timeout
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3526] dhcp4 (enp3s0): canceled DHCP transaction, DHCP 
client pid 4040
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3526] dhcp4 (enp3s0): state changed timeout -> done
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3581] device (enp3s0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3587] manager: NetworkManager state is now 
CONNECTED_LOCAL
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <warn>  
[1527901434.3671] device (enp3s0): Activation: failed for connection 'Wired 
connection 1'
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.3724] device (enp3s0): state change: failed -> disconnected 
(reason 'none', internal state 'managed')
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.4155] policy: auto-activating connection 'Wired connection 1'
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.4328] device (enp3s0): Activation: starting connection 'Wired 
connection 1' (f596494f-e725-375c-ae81-ca016ce88e49)
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.4395] device (enp3s0): state change: disconnected -> prepare 
(reason 'none', internal state 'managed')
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.4453] manager: NetworkManager state is now CONNECTING
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.4580] device (enp3s0): state change: prepare -> config (reason 
'none', internal state 'managed')
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.8339] device (enp3s0): state change: config -> ip-config 
(reason 'none', internal state 'managed')
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.8347] dhcp4 (enp3s0): activation: beginning transaction 
(timeout in 45 seconds)
Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901434.8519] dhcp4 (enp3s0): dhclient started with pid 5539
Jun 02 11:03:54 amdgcc3.dyndns.org dhclient[5539]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x724f5c7b)
Jun 02 11:03:57 amdgcc3.dyndns.org dhclient[5539]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x724f5c7b)
Jun 02 11:04:01 amdgcc3.dyndns.org dhclient[5539]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x724f5c7b)
Jun 02 11:04:11 amdgcc3.dyndns.org dhclient[5539]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0xf790ed35)
Jun 02 11:04:15 amdgcc3.dyndns.org dhclient[5539]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0xf790ed35)
Jun 02 11:04:24 amdgcc3.dyndns.org dhclient[5539]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 10 (xid=0xf790ed35)
Jun 02 11:04:34 amdgcc3.dyndns.org dhclient[5539]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 7 (xid=0xf790ed35)
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <warn>  
[1527901480.3538] dhcp4 (enp3s0): request timed out
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3541] dhcp4 (enp3s0): state changed unknown -> timeout
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3575] dhcp4 (enp3s0): canceled DHCP transaction, DHCP 
client pid 5539
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3575] dhcp4 (enp3s0): state changed timeout -> done
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3648] device (enp3s0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3705] manager: NetworkManager state is now 
CONNECTED_LOCAL
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <warn>  
[1527901480.3710] device (enp3s0): Activation: failed for connection 'Wired 
connection 1'
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.3892] device (enp3s0): state change: failed -> disconnected 
(reason 'none', internal state 'managed')
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.4324] policy: auto-activating connection 'Wired connection 1'
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.4553] device (enp3s0): Activation: starting connection 'Wired 
connection 1' (f596494f-e725-375c-ae81-ca016ce88e49)
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.4593] device (enp3s0): state change: disconnected -> prepare 
(reason 'none', internal state 'managed')
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.4605] manager: NetworkManager state is now CONNECTING
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.4638] device (enp3s0): state change: prepare -> config (reason 
'none', internal state 'managed')
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.8317] device (enp3s0): state change: config -> ip-config 
(reason 'none', internal state 'managed')
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.8325] dhcp4 (enp3s0): activation: beginning transaction 
(timeout in 45 seconds)
Jun 02 11:04:40 amdgcc3.dyndns.org NetworkManager[681]: <info>  
[1527901480.8446] dhcp4 (enp3s0): dhclient started with pid 9763
Jun 02 11:04:40 amdgcc3.dyndns.org dhclient[9763]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x70bb8765)
Jun 02 11:04:46 amdgcc3.dyndns.org dhclient[9763]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x70bb8765)
Jun 02 11:04:59 amdgcc3.dyndns.org dhclient[9763]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0xdf166879)
Jun 02 11:05:02 amdgcc3.dyndns.org dhclient[9763]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 5 (xid=0xdf166879)
Jun 02 11:05:07 amdgcc3.dyndns.org dhclient[9763]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 8 (xid=0xdf166879)
Jun 02 11:05:15 amdgcc3.dyndns.org dhclient[9763]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 8 (xid=0xdf166879)
=== end ====

Result after reboot with the previous kernel
(This goes back to the same original IP it was getting from the dhcpd server 
of the router).
===== ifconfig and journalctl ==== 
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.115  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::373a:37f3:ca88:ab02  prefixlen 64  scopeid 0x20<link>
        ether 00:19:21:e9:4d:0e  txqueuelen 1000  (Ethernet)
        RX packets 108  bytes 35730 (34.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 144  bytes 24269 (23.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 108  bytes 9096 (8.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 108  bytes 9096 (8.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.124.1  netmask 255.255.255.0  broadcast 192.168.124.255
        ether 52:54:00:8e:b1:b3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

-- Logs begin at Thu 2017-05-25 15:19:59 ChST, end at Sat 2018-06-02 
11:11:41 ChST. --
Jun 02 11:07:23 amdgcc3.dyndns.org systemd[1]: Starting Network 
Manager...
Jun 02 11:07:23 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901643.5005] NetworkManager (version 1.8.6-1.fc27) is starting... (for 
the first time)
Jun 02 11:07:23 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901643.5072] Read config: 
/etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
Jun 02 11:07:23 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901643.5996] manager[0x5605176ce140]: monitoring kernel firmware 
directory '/lib/firmware'.
Jun 02 11:07:23 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901643.7012] policy: hostname management mode: default
Jun 02 11:07:23 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901643.7026] dns-mgr[0x5605176d9970]: init: dns=default, 
rc-manager=symlink
Jun 02 11:07:23 amdgcc3.dyndns.org systemd[1]: Started Network Manager.
Jun 02 11:07:26 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901646.3079] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list. 
(/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
Jun 02 11:07:26 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901646.3435] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To 
report bugs please use the NetworkManager mailing list. 
(/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so)
Jun 02 11:07:26 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901646.3437] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list.
Jun 02 11:07:26 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901646.3463] ifcfg-rh: new connection 
/etc/sysconfig/network-scripts/ifcfg-Wired_connection_1 
(f596494f-e725-375c-ae81-ca016ce88e49,"Wired connection 1")
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.2511] settings: hostname: using hostnamed
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.2568] settings: hostname changed from (none) to 
"amdgcc3.dyndns.org"
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5286] dhcp-init: Using DHCP client 'dhclient'
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5288] manager: rfkill: WiFi enabled by radio killswitch; enabled 
by state file
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5289] manager: rfkill: WWAN enabled by radio killswitch; 
enabled by state file
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5290] manager: Networking is enabled by state file
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5566] Loaded device plugin: NMBondDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5575] Loaded device plugin: NMBridgeDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5576] Loaded device plugin: NMDummyDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5577] Loaded device plugin: NMEthernetDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5578] Loaded device plugin: NMInfinibandDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5578] Loaded device plugin: NMIPTunnelDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.5579] Loaded device plugin: NMMacsecDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.6410] Loaded device plugin: NMMacvlanDeviceFactory 
(internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.6411] Loaded device plugin: NMTunDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.6412] Loaded device plugin: NMVethDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.6413] Loaded device plugin: NMVlanDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.6414] Loaded device plugin: NMVxlanDeviceFactory (internal)
Jun 02 11:07:29 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901649.7654] Loaded device plugin: NMAtmManager 
(/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.0922] Loaded device plugin: NMBluezManager 
(/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.2717] Loaded device plugin: NMTeamFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6209] Loaded device plugin: NMWifiFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6584] Loaded device plugin: NMWwanFactory 
(/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6754] device (lo): link connected
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6799] manager: (lo): new Generic device 
(/org/freedesktop/NetworkManager/Devices/1)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6896] manager: (enp3s0): new Ethernet device 
(/org/freedesktop/NetworkManager/Devices/2)
Jun 02 11:07:30 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901650.6954] device (enp3s0): state change: unmanaged -> 
unavailable (reason 'managed', internal state 'external')
Jun 02 11:07:31 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901651.4203] ModemManager available in the bus
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1751] device (enp3s0): link connected
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1796] device (enp3s0): state change: unavailable -> 
disconnected (reason 'carrier-changed', internal state 'managed')
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1855] policy: auto-activating connection 'Wired connection 1'
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1899] device (enp3s0): Activation: starting connection 'Wired 
connection 1' (f596494f-e725-375c-ae81-ca016ce88e49)
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1922] device (enp3s0): state change: disconnected -> prepare 
(reason 'none', internal state 'managed')
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1937] manager: NetworkManager state is now CONNECTING
Jun 02 11:07:33 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901653.1984] device (enp3s0): state change: prepare -> config (reason 
'none', internal state 'managed')
Jun 02 11:07:43 amdgcc3.dyndns.org NetworkManager[693]: <warn>  
[1527901663.2012] firewall: [0x5605177a6c80,change:"enp3s0"]: complete: 
request failed (Timeout was reached)
Jun 02 11:07:43 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901663.2019] device (enp3s0): state change: config -> ip-config 
(reason 'none', internal state 'managed')
Jun 02 11:07:43 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901663.2202] dhcp4 (enp3s0): activation: beginning transaction 
(timeout in 45 seconds)
Jun 02 11:07:44 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901664.4792] dhcp4 (enp3s0): dhclient started with pid 1276
Jun 02 11:07:44 amdgcc3.dyndns.org dhclient[1276]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0xf4583b1d)
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.1531] manager: (virbr0): new Bridge device 
(/org/freedesktop/NetworkManager/Devices/3)
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.2214] manager: (virbr0-nic): new Tun device 
(/org/freedesktop/NetworkManager/Devices/4)
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.2985] device (virbr0-nic): state change: unmanaged -> 
unavailable (reason 'connection-assumed', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.3037] device (virbr0-nic): state change: unavailable -> 
disconnected (reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.7762] device (virbr0): state change: unmanaged -> unavailable 
(reason 'connection-assumed', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.7933] ifcfg-rh: add connection in-memory 
(a1948cab-c96f-4dbe-8859-5740831177e8,"virbr0")
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8002] device (virbr0): state change: unavailable -> 
disconnected (reason 'connection-assumed', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8100] device (virbr0): Activation: starting connection 'virbr0' 
(a1948cab-c96f-4dbe-8859-5740831177e8)
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8329] device (virbr0): state change: disconnected -> prepare 
(reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8426] device (virbr0): state change: prepare -> config (reason 
'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8576] keyfile: add connection in-memory 
(afb07c25-eab4-476c-9f36-a5a58bcf4eb1,"virbr0-nic")
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8710] device (virbr0-nic): Activation: starting connection 
'virbr0-nic' (afb07c25-eab4-476c-9f36-a5a58bcf4eb1)
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8728] device (virbr0): state change: config -> ip-config (reason 
'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.8940] device (virbr0-nic): state change: disconnected -> 
prepare (reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9319] device (virbr0): state change: ip-config -> ip-check 
(reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9488] device (virbr0-nic): state change: prepare -> config 
(reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9738] device (virbr0-nic): state change: config -> ip-config 
(reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9799] device (virbr0): bridge port virbr0-nic was attached
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9811] device (virbr0-nic): Activation: connection 'virbr0-nic' 
enslaved, continuing activation
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9900] device (virbr0-nic): state change: ip-config -> 
secondaries (reason 'none', internal state 'external')
Jun 02 11:07:45 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901665.9933] device (virbr0-nic): state change: secondaries -> 
activated (reason 'none', internal state 'external')
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.0621] device (virbr0-nic): Activation: successful, device 
activated.
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.0700] device (virbr0): state change: ip-check -> secondaries 
(reason 'none', internal state 'external')
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.0809] device (virbr0): state change: secondaries -> activated 
(reason 'none', internal state 'external')
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.1542] device (virbr0): Activation: successful, device activated.
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.1731] device (virbr0-nic): state change: activated -> 
unmanaged (reason 'connection-assumed', internal state 'external')
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.1749] device (virbr0): bridge port virbr0-nic was detached
Jun 02 11:07:46 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901666.1749] device (virbr0-nic): released from master device virbr0
Jun 02 11:07:52 amdgcc3.dyndns.org dhclient[1276]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0xf4583b1d)
Jun 02 11:08:11 amdgcc3.dyndns.org dhclient[1276]: DHCPDISCOVER on 
enp3s0 to 255.255.255.255 port 67 interval 7 (xid=0x2ecd1823)
Jun 02 11:08:12 amdgcc3.dyndns.org dhclient[1276]: DHCPREQUEST on 
enp3s0 to 255.255.255.255 port 67 (xid=0x2ecd1823)
Jun 02 11:08:12 amdgcc3.dyndns.org dhclient[1276]: DHCPOFFER from 
192.168.0.1
Jun 02 11:08:12 amdgcc3.dyndns.org dhclient[1276]: DHCPACK from 
192.168.0.1 (xid=0x2ecd1823)
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8513] dhcp4 (enp3s0):   address 192.168.0.115
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8572] dhcp4 (enp3s0):   plen 24 (255.255.255.0)
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8579] dhcp4 (enp3s0):   gateway 192.168.0.1
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8584] dhcp4 (enp3s0):   lease time 315360000
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8606] dhcp4 (enp3s0):   nameserver '192.168.0.1'
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8614] dhcp4 (enp3s0): state changed unknown -> bound
Jun 02 11:08:12 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901692.8880] device (enp3s0): state change: ip-config -> ip-check 
(reason 'none', internal state 'managed')
Jun 02 11:08:13 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901693.1266] device (enp3s0): state change: ip-check -> secondaries 
(reason 'none', internal state 'managed')
Jun 02 11:08:13 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901693.1286] device (enp3s0): state change: secondaries -> activated 
(reason 'none', internal state 'managed')
Jun 02 11:08:13 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901693.1307] manager: NetworkManager state is now 
CONNECTED_LOCAL
Jun 02 11:08:14 amdgcc3.dyndns.org dhclient[1276]: bound to 
192.168.0.115 -- renewal in 151506569 seconds.
Jun 02 11:08:14 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901694.8517] manager: NetworkManager state is now 
CONNECTED_SITE
Jun 02 11:08:14 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901694.8543] policy: set 'Wired connection 1' (enp3s0) as default for 
IPv4 routing and DNS
Jun 02 11:08:14 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901694.8583] device (enp3s0): Activation: successful, device activated.
Jun 02 11:08:14 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901694.8702] manager: startup complete
Jun 02 11:08:27 amdgcc3.dyndns.org NetworkManager[693]: <info>  
[1527901707.2724] manager: NetworkManager state is now 
CONNECTED_GLOBAL

=== end ===

On 2 Jun 2018 at 5:55, Ed Greshko wrote:

From:	Ed Greshko <ed.greshko@xxxxxxxxxxx>
Subject:	Re: Strange issue with dhcpd and laster kernel upgrade?
To:	Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>
Date sent:	Sat, 2 Jun 2018 05:55:19 +0800
Send reply to:	Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>

> On 06/02/18 03:02, Michael D. Setzer II wrote:
> > Didn't get anything from journalctl option, but ip is hard coded at moment.
> > Looked at message log, and it had over 1200 lines like these.
> > May 31 11:52:00 amdgcc3 NetworkManager[676]: <info>  
> > [1527731520.5500] dhcp4 (enp3s0): activation: beginning transaction 
> > (timeout in 45 seconds)
>  
> I think you are saying that DHCP is also failing to set the address on your wired
> connection? 
> 
> If that is the case I would set it back to "Automatic" in the GUI and then
> disconnect.  Wait for the time to advance to the next minute and then reconnect.
> 
> After that I would do "journalctl -b -u NetworkManager" and look at the entries for
> the time when you issued the reconnect.
> 
> It should look something like....
> 
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.4312]
> device (enp0s3): Activation: starting connection 'enp0s3'
> (1b2b5cc8-6343-3f4b-9f76-0fc63b685359)
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.4314]
> audit: op="connection-activate" uuid="1b2b5cc8-6343-3f4b-9f76-0fc63b685359"
> name="enp0s3" pid=2596 uid=1029 result="success"
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.4393]
> device (enp0s3): state change: disconnected -> prepare (reason 'none',
> sys-iface-state: 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.4396]
> manager: NetworkManager state is now CONNECTING
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.4493]
> device (enp0s3): state change: prepare -> config (reason 'none', sys-iface-state:
> 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.5546]
> device (enp0s3): state change: config -> ip-config (reason 'none', sys-iface-state:
> 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.5551]
> dhcp4 (enp0s3): activation: beginning transaction (timeout in 45 seconds)
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.5780]
> dhcp4 (enp0s3): dhclient started with pid 2664
> Jun 02 05:07:04 f28k-b1.greshko.com dhclient[2664]: DHCPREQUEST on enp0s3 to
> 255.255.255.255 port 67 (xid=0xbe018b02)
> Jun 02 05:07:04 f28k-b1.greshko.com dhclient[2664]: DHCPACK from 192.168.1.1
> (xid=0xbe018b02)
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7347]
> dhcp4 (enp0s3):   address 192.168.1.80
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7350]
> dhcp4 (enp0s3):   plen 24 (255.255.255.0)
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7352]
> dhcp4 (enp0s3):   gateway 192.168.1.1
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7354]
> dhcp4 (enp0s3):   lease time 86400
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7355]
> dhcp4 (enp0s3):   hostname 'f28k-b1'
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7357]
> dhcp4 (enp0s3):   nameserver '192.168.1.1'
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7359]
> dhcp4 (enp0s3): state changed unknown -> bound
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.7519]
> device (enp0s3): state change: ip-config -> ip-check (reason 'none', sys-iface-state:
> 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com dhclient[2664]: bound to 192.168.1.80 -- renewal
> in 36907 seconds.
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9404]
> device (enp0s3): state change: ip-check -> secondaries (reason 'none',
> sys-iface-state: 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9408]
> device (enp0s3): state change: secondaries -> activated (reason 'none',
> sys-iface-state: 'managed')
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9410]
> manager: NetworkManager state is now CONNECTED_LOCAL
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9459]
> manager: NetworkManager state is now CONNECTED_SITE
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9462]
> policy: set 'enp0s3' (enp0s3) as default for IPv4 routing and DNS
> Jun 02 05:07:04 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887224.9541]
> device (enp0s3): Activation: successful, device activated.
> Jun 02 05:07:05 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887225.8972]
> manager: NetworkManager state is now CONNECTED_GLOBAL
> Jun 02 05:07:07 f28k-b1.greshko.com NetworkManager[635]: <info>  [1527887227.1206]
> policy: set 'enp0s3' (enp0s3) as default for IPv6 routing and DNS
> 
> 
> -- 
> Conjecture is just a conclusion based on incomplete information. It isn't a fact.
> 
> 


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:mikes@xxxxxxxx                            
 mailto:msetzerii@xxxxxxxxx
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS

ROSETTA      65563610.075728 | ABC          16613838.513356
SETI        109375858.605587 | EINSTEIN    141133906.999240
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/4QUWG4R3S3SHIA3YGV2JMNTNL4RFG4XY/




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux