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)
May 31 11:52:00 amdgcc3 NetworkManager[676]: <info>
[1527731520.5582] dhcp4 (enp3s0): dhclient started with pid 17417
May 31 11:52:45 amdgcc3 NetworkManager[676]: <warn>
[1527731565.3545] dhcp4 (enp3s0): request timed out
May 31 11:52:45 amdgcc3 NetworkManager[676]: <info>
[1527731565.3545] dhcp4 (enp3s0): state changed unknown -> timeout
May 31 11:52:45 amdgcc3 NetworkManager[676]: <info>
[1527731565.3568] dhcp4 (enp3s0): canceled DHCP transaction, DHCP
client pid 17417
May 31 11:52:45 amdgcc3 NetworkManager[676]: <info>
[1527731565.3568] dhcp4 (enp3s0): state changed timeout -> done
May 31 11:52:45 amdgcc3 NetworkManager[676]: <info>
[1527731565.5538] dhcp4 (enp3s0): activation: beginning transaction
(timeout in 45 seconds)
May 31 11:52:45 amdgcc3 NetworkManager[676]: <info>
[1527731565.5625] dhcp4 (enp3s0): dhclient started with pid 3041
May 31 11:53:30 amdgcc3 NetworkManager[676]: <warn>
[1527731610.3545] dhcp4 (enp3s0): request timed out
May 31 11:53:30 amdgcc3 NetworkManager[676]: <info>
[1527731610.3548] dhcp4 (enp3s0): state changed unknown -> timeout
May 31 11:53:30 amdgcc3 NetworkManager[676]: <info>
[1527731610.3571] dhcp4 (enp3s0): canceled DHCP transaction, DHCP
client pid 3041
May 31 11:53:30 amdgcc3 NetworkManager[676]: <info>
[1527731610.3572] dhcp4 (enp3s0): state changed timeout -> done
May 31 11:53:30 amdgcc3 NetworkManager[676]: <info>
[1527731610.5552] dhcp4 (enp3s0): activation: beginning transaction
(timeout in 45 seconds)
May 31 11:53:30 amdgcc3 NetworkManager[676]: <info>
[1527731610.5616] dhcp4 (enp3s0): dhclient started with pid 22198
May 31 11:54:15 amdgcc3 NetworkManager[676]: <warn>
[1527731655.3545] dhcp4 (enp3s0): request timed out
May 31 11:54:15 amdgcc3 NetworkManager[676]: <info>
[1527731655.3545] dhcp4 (enp3s0): state changed unknown -> timeout
May 31 11:54:15 amdgcc3 NetworkManager[676]: <info>
[1527731655.3578] dhcp4 (enp3s0): canceled DHCP transaction, DHCP
client pid 22198
May 31 11:54:15 amdgcc3 NetworkManager[676]: <info>
[1527731655.3579] dhcp4 (enp3s0): state changed timeout -> done
May 31 11:54:15 amdgcc3 NetworkManager[676]: <info>
[1527731655.5571] dhcp4 (enp3s0): activation: beginning transaction
(timeout in 45 seconds)
May 31 11:54:15 amdgcc3 NetworkManager[676]: <info>
[1527731655.5619] dhcp4 (enp3s0): dhclient started with pid 6456
On 1 Jun 2018 at 22:08, Ed Greshko wrote:
From: Ed Greshko <ed.greshko(a)greshko.com>
Subject: Re: Strange issue with dhcpd and laster kernel upgrade?
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Date sent: Fri, 1 Jun 2018 22:08:50 +0800
Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org>
On 06/01/18 22:02, Michael D. Setzer II wrote:
> Since it works fine with the previous kernel, and not with the new kernel, that
> would seem to pointing to the kernel versus the other devices.
Maybe. But as I noted I'm using the most recent kernel and not having issues.
>
> With the wired devices it is a trendnet router that I've had for many years.
> With the wireless, it is a blink wireless router.
>
> In both cases, it worked before the upgrade, and rebooting to the previous
> kernel makes it work again. Just after midnight here, so will have to look into
> the things tomorrow. Have a sunrise ride, and then a funeral escort, so will
> have to wait. I'm still using Fedora 27, so perhaps it is a difference between
> the fedora 27 and Fedora 28. Will have to see if there is some kind of failure
> message.
OK.... Check the logs, of course.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
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