On 06/02/18 09:26, Michael D. Setzer II wrote: > 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). Thanks for the logs.... Of course this, from the logs, shows something isn't working.... 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=3D0x3602a421) Jun 02 11:03:12 amdgcc3.dyndns.org dhclient[4040]: DHCPREQUEST on enp3s0 to 255.255.255.255 port 67 (xid=3D0x3602a421) Jun 02 11:03:17 amdgcc3.dyndns.org dhclient[4040]: DHCPREQUEST on enp3s0 to 255.255.255.255 port 67 (xid=3D0x3602a421) Jun 02 11:03:31 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 5 (xid=3D0x953b7025) Jun 02 11:03:36 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7 (xid=3D0x953b7025) Jun 02 11:03:43 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=3D0x953b7025) Jun 02 11:03:52 amdgcc3.dyndns.org dhclient[4040]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 18 (xid=3D0x953b7025) Jun 02 11:03:54 amdgcc3.dyndns.org NetworkManager[681]: <warn> [1527901434.3499] dhcp4 (enp3s0): request timed out While this shows a good result with the previous kernel.... [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=3D0xf4583b1d) Jun 02 11:07:52 amdgcc3.dyndns.org dhclient[1276]: DHCPREQUEST on enp3s0 to 255.255.255.255 port 67 (xid=3D0xf4583b1d) Jun 02 11:08:11 amdgcc3.dyndns.org dhclient[1276]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7 (xid=3D0x2ecd1823) Jun 02 11:08:12 amdgcc3.dyndns.org dhclient[1276]: DHCPREQUEST on enp3s0 to 255.255.255.255 port 67 (xid=3D0x2ecd1823) 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=3D0x2ecd1823) 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 activate= d. As you may have guessed, nothing in the above points to the source of the the failure... :-( These are the following things I would do/check.... 1. You are running xfce and if you are also running lightdm as your display manager I would, based on another thread, check to see if the system has a /usr/lib64/security/pam_kwallet5.so file. 2. Go to /var/lib/NetworkManager/ and delete any *lease files and then try again. 3. Again in /var/lib/NetworkManager/ check to see if there is a difference in the dhclient-enp0s3.conf file in the working case v.s. failing case 4. Use wireshark and verify that the DHCP request is actually going out on the wire. 5. Long shot.... "systemctl stop firewalld" and try again. 6. Longer shot.... "setenforce 0" and try again. -- Conjecture is just a conclusion based on incomplete information. It isn't a fact.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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/4D6TJRB3MKW5I6NDFIWZWDIGLMNEREAJ/
