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.