Fedora 43 - Surface Pro 7 - Wired (Ethernet) - No Internet or Activation Failed

Ask Fedora
1

I just installed Fedora 43 on my Surface Pro 7. Wifi works fine but the wired connection has no internet. I checked the wired connection with my other device and it works fine.

Kindly help…

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 84:3a:5b:7b:af:18 brd ff:ff:ff:ff:ff:ff
    altname enp0s13f0u1u4u2u1
    altname enx843a5b7baf18
    inet6 fdc3:37ed:1225:81e:fd28:5a7:dfd:7f/64 scope global dynamic noprefixroute 
       valid_lft 1474sec preferred_lft 1474sec
    inet6 fe80::809b:7c7c:c8d8:ee33/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e6:23:9f:df:2e:aa brd ff:ff:ff:ff:ff:ff permaddr e0:2b:e9:d8:43:2f
    altname wlxe02be9d8432f
    inet 192.168.86.254/24 brd 192.168.86.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 85762sec preferred_lft 85762sec
    inet6 fdc3:37ed:1225:81e:8a4:b397:a2b5:c37b/64 scope global dynamic noprefixroute 
       valid_lft 1474sec preferred_lft 1474sec
    inet6 fe80::d85:5894:3a5e:c092/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ifconfig

        inet6 fe80::809b:7c7c:c8d8:ee33  prefixlen 64  scopeid 0x20<link>
        inet6 fdc3:37ed:1225:81e:fd28:5a7:dfd:7f  prefixlen 64  scopeid 0x0<global>
        ether 84:3a:5b:7b:af:18  txqueuelen 1000  (Ethernet)
        RX packets 5440  bytes 783494 (765.1 KiB)
        RX errors 0  dropped 6  overruns 0  frame 0
        TX packets 221  bytes 63341 (61.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 1528381  bytes 49753612165 (46.3 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1528381  bytes 49753612165 (46.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s20f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.254  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fdc3:37ed:1225:81e:8a4:b397:a2b5:c37b  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::d85:5894:3a5e:c092  prefixlen 64  scopeid 0x20<link>
        ether e6:23:9f:df:2e:aa  txqueuelen 1000  (Ethernet)
        RX packets 98143  bytes 110616949 (105.4 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 20093  bytes 4881404 (4.6 MiB)
        TX errors 0  dropped 3 overruns 0  carrier 0  collisions 0

`type or paste code here`
2

It appears you have both wifi and wired connected.
The wifi has both ipv4 & ipv6 configured but the wired connection is only ipv6.

What does ip r show for routing.? I suspect that the routing is via the wifi interface.

Having 2 interfaces on the same subnet often causes problems.

What happens if you disconnect both interfaces and reboot (making certain the wifi does not reconnect automatically) then reconnect only the ethernet interface?

3

ip r

default via 192.168.86.1 dev wlp0s20f3 proto dhcp src 192.168.86.254 metric 600 
192.168.86.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.86.254 metric 600
4

As mentioned I tried making wifi not reconnect .. there is no internet connection at all, even when the wired connection shows connected for a short while..

ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::809b:7c7c:c8d8:ee33  prefixlen 64  scopeid 0x20<link>
        ether 84:3a:5b:7b:af:18  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 87  bytes 28362 (27.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 32  bytes 3563 (3.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 3563 (3.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s20f3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 1e:fe:7b:74:0a:37  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


ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 84:3a:5b:7b:af:18 brd ff:ff:ff:ff:ff:ff
    altname enp0s13f0u1u4u2u1
    altname enx843a5b7baf18
    inet6 fe80::809b:7c7c:c8d8:ee33/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 1e:fe:7b:74:0a:37 brd ff:ff:ff:ff:ff:ff permaddr e0:2b:e9:d8:43:2f
    altname wlxe02be9d8432f

ip r (no result)

Connection Failed: Activation of network connection failed.

lsmod | grep r8

r8153_ecm              12288  0
cdc_ether              24576  1 r8153_ecm
usbnet                 61440  2 r8153_ecm,cdc_ether
r8152                 176128  1 r8153_ecm
mii                    16384  2 usbnet,r8152
5

The wired connection shows inet6 only
You may have ipv4 disabled in the settings for that device and thus it cannot get an ipv4 address so cannot talk to the router.

If you are using gnome the settings for that device should allow you to confirm that it is allowed to obtain both ipv6 & ipv4 addresses. That is where I would look first.

You should also run ip r to see what the routing is when ONLY the wired interface is connected at boot time.

You also might try booting with the live media and see what happens with the wired interface connected there and not enabling wifi.

I note that your routing shows only ipv4 routed and nothing for ipv6 routing.

EDIT
This may indicate that your router cannot manage ipv6 routing.

1 Like
6

here is IP r

192.168.86.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.86.23 metric 600
7

That is on the wifi interface.

Your problem is on the wired interface and routing there can only be tested by disabling the wifi then rebooting so the system is forced to connect only by the wired interface. If the wired interface is the only one active then routing should be established there.

Note that the wired interface must be configured to allow ipv4 traffic as I mentioned above.

8

I did share all the details you are asking for when I disabled wifi earlier in previous communication. kindly tell me exactly steps on how you want me to gather data you need and I will do so. apologies, I am little no wise.

9

Please provide the output of inxi -Fzxx. That should provide a lot of information that would require asking multiple questions.

The info above with the results you have shown to date seem to indicate that the router/AP may be only capable of routing with ipv4. We need to confirm that, which is why it is important to

  1. ensure the ethernet interface is configured to allow ipv4 traffic
  2. use only the wired interface when booting (ip a should show the connections)
  3. verify the routing after booting and without enabling wifi (ip r will show the current routing (if any))

You provided the info above but there are still questions about the config particularly item 1.

If the router will not provide an ipv4 address and routing to the wired interface then it would appear the problem lies at the router and not with fedora. Note that I am assuming your router is also the gateway / AP that provides internet access. I also assume that addresses are received by DHCP. If this is incorrect please add details of the network to clear up any misunderstanding.

Some routers do not support ipv6 routing. Some have ipv6 routing disabled by default but can be enabled, Some are connected to the ISP by an ipv4 network only and ipv6 routing cannot be used.

What I see in the detail above is that the wired interface has received an ipv6 address, local link only, and no routing. The wifi was down at the time. What is missing is confirmation that ipv4 was enabled on that interface.

In the previous postings you showed the routing with wifi enabled and it received ipv4 routing info only. At that time both interfaces had an ipv6 address assigned as well. (The ipv6 addresses that begin with ‘fe80’ are local link addresses and the ones that begin with ‘fdc3’ are actual inet addresses)

Another place to look for possible problems is in the files located under /etc/NetworkManager/system-connections and see what is contained in files there. It is possible that something in one of those files is restricting the wired interface to ipv6 only. If so then removing the file with the restriction would allow a new connection to be created with normal reception of both ipv4 & ipv6 addresses to the interface.

A final though that may work would be to disable ipv6 on both interfaces and force the system to only use ipv4.

You have not said which f43 version you are using. This is the gnome wired network interface in the system settings.

image
image804×547 28.3 KB

Similarly for ipv4 and for the wifi interface.

1 Like
10 
System:
  Kernel: 6.18.5-200.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 43 (Workstation Edition)
Machine:
  Type: Laptop System: Microsoft product: Surface Pro 7
    v: 124I:00046T:000M:0100000D:0B:07F:0C:05P:48S:1E:0Y:0K:0U:06R:5
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Microsoft model: Surface Pro 7 serial: <superuser required>
    part-nu: Surface_Pro_7_1866 Firmware: UEFI vendor: Microsoft v: 24.109.140
    date: 07/21/2025
Battery:
  ID-1: BAT1 charge: 13.6 Wh (37.6%) condition: 36.3/43.2 Wh (84%) volts: 8.19
    min: 7.57 model: DYN M1109597 serial: <filter> charging: status: charging
    cycles: 848
  Device-1: hidpp_battery_1 model: Logitech Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i5-1035G4 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 6 MiB
  Speed (MHz): avg: 400 min/max: 400/3700 cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 bogomips: 23961
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G4 vendor: Microsoft driver: i915
    v: kernel arch: Gen-11 ports: active: DP-6 off: eDP-1 empty: DP-1, DP-2,
    DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:8a5a
  Device-2: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-4.4.2.3:18 chip-ID: 046d:0843
  Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
    driver: gpu: i915 display-ID: 0
  Monitor-1: DP-6 model: Dell P3424WE res: 3440x1440 dpi: 109
    diag: 867mm (34.1")
  Monitor-2: eDP-1 model: LG Display 0x0555 res: 2736x1824 dpi: 267
    diag: 312mm (12.3")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.2.7 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Iris Plus Graphics (ICL GT1.5)
    device-ID: 8086:8a5a display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Image Signal Processor driver: N/A bus-ID: 00:05.0
    chip-ID: 8086:8a19
  Device-2: Intel Ice Lake-LP Smart Sound Audio driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:34c8
  Device-3: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-4.4.2.3:18 chip-ID: 046d:0843
  API: ALSA v: k6.18.5-200.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:34f0
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 bus-ID: 2-1.4.2.1:12 chip-ID: 0bda:8153
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:3 chip-ID: 8087:0026
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 238.47 GiB used: 14.87 GiB (6.2%)
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZPZ256G BG4A KIOXIA
    size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 24.9 C
Partition:
  ID-1: / size: 235.89 GiB used: 14.44 GiB (6.1%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 1.9 GiB used: 421 MiB (21.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 235.89 GiB used: 14.44 GiB (6.1%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 7.34 GiB used: 4 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.34 GiB used: 3.51 GiB (47.9%)
  Processes: 447 Power: uptime: 1d 4h 32m wakeups: 3 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 18
    Compilers: N/A Shell: Bash v: 5.3.0 running-in: ptyxis-agent inxi: 3.3.40
11

image
image762×504 29.2 KB

12

contents of /etc/NetworkManager/system-connections

image
image681×467 10.8 KB

13

System Details:# System Details Report

Report details

  • Date generated: 2026-01-24 01:38:23

Hardware Information:

  • Hardware Model: Microsoft Corporation Surface Pro 7
  • Memory: 8.0 GiB
  • Processor: Intel® Core™ i5-1035G4 × 8
  • Graphics: Intel® Iris® Plus Graphics (ICL GT1.5)
  • Disk Capacity: 256.1 GB

Software Information:

  • Firmware Version: 24.109.140
  • OS Name: Fedora Linux 43 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 49
  • Windowing System: Wayland
  • Kernel Version: Linux 6.18.5-200.fc43.x86_64
14

Speaking about L3 connectivity, IPv4 and IPv6 are entirely independent.
You don’t really need to disable one to make the other work.

BTW, why do you have multiple wired connection profiles?
Remove them all and restart NetworkManager to create a new one with default settings.

Issues like this are usually related to:

  • Incorrect power-saving implementation resulting in packet loss or some other regression in the kernel or firmware.
  • Incorrectly operating DHCP server due to misconfiguration or a bug in the router’s firmware, try restarting the router or better test a different one to rule the possibility.
  • Damaged or incorrectly wired Ethernet cable or port, so try different ones if possible.

If the problem persists, try collecting the connection log:

journalctl --no-pager -b -u NetworkManager.service
15

Here is the info for $ journalctl --no-pager -b -u NetworkManager.service
Also deleted all connection profiles from that directory.

$ journalctl --no-pager -b -u NetworkManager.service
Jan 24 15:53:30 fedora systemd[1]: Starting NetworkManager.service - Network Manager...
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9684] NetworkManager (version 1.54.3-2.fc43) is starting... (boot:45614174-15ba-46c9-9c84-54d9a2eb9aed)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9686] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{20-connectivity-fedora.conf,22-wifi-mac-addr.conf,99-nvme-nbft-no-ignore-carrier.conf}
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9728] manager[0x55ee11f512b0]: monitoring kernel firmware directory '/lib/firmware'.
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9745] hostname: hostname: using hostnamed
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9753] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9767] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill0) (driver iwlwifi)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9769] manager[0x55ee11f512b0]: rfkill: Wi-Fi hardware radio set enabled
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9769] manager[0x55ee11f512b0]: rfkill: WWAN hardware radio set enabled
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9791] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.54.3-2.fc43/libnm-device-plugin-wifi.so)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9815] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.54.3-2.fc43/libnm-device-plugin-bluetooth.so)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9818] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.54.3-2.fc43/libnm-device-plugin-adsl.so)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9828] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.54.3-2.fc43/libnm-device-plugin-team.so)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9831] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.54.3-2.fc43/libnm-device-plugin-wwan.so)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9833] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9833] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9833] manager: Networking is enabled by state file
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9836] settings: Loaded settings plugin: keyfile (internal)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9856] dhcp: init: Using DHCP client 'internal'
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9857] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9865] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9867] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9870] device (lo): Activation: starting connection 'lo' (65c91442-5923-42a3-a17b-3ac2f7f29c13)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9880] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9882] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9929] device (wlp0s20f3): driver supports Access Point (AP) mode
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9932] manager: (wlp0s20f3): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jan 24 15:53:30 fedora NetworkManager[1039]: <info>  [1769288010.9933] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.2057] device (wlp0s20f3): set-hw-addr: set MAC address to 36:AD:C5:33:11:D3 (scanning)
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.3995] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4001] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4002] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4003] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora systemd[1]: Started NetworkManager.service - Network Manager.
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4006] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4017] modem-manager: ModemManager available
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4020] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4021] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4024] device (lo): Activation: successful, device activated.
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4483] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4484] Wi-Fi P2P device controlled by interface wlp0s20f3 created
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4486] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4487] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 24 15:53:31 fedora NetworkManager[1039]: <warn>  [1769288011.4488] device (p2p-dev-wlp0s20f3): error setting IPv4 forwarding to '0': Success
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4491] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.4496] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6589] device (eth0): carrier: link connected
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6594] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6599] policy: auto-activating connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6601] device (eth0): Activation: starting connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6602] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6603] manager: NetworkManager state is now CONNECTING
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.6604] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.7017] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 15:53:31 fedora NetworkManager[1039]: <info>  [1769288011.7021] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7272] policy: auto-activating connection 'NetLink' (b1dbddf5-4614-4a16-9527-f01a2e941cb1)
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7275] device (wlp0s20f3): Activation: starting connection 'NetLink' (b1dbddf5-4614-4a16-9527-f01a2e941cb1)
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7276] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7394] device (wlp0s20f3): set-hw-addr: set-cloned MAC address to 76:5E:08:81:F8:4C (stable-ssid)
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7420] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7422] device (wlp0s20f3): Activation: (wifi) access point 'NetLink' has security, but secrets are required.
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7422] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7429] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7431] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7432] device (wlp0s20f3): Activation: (wifi) connection 'NetLink' has security, and secrets exist.  No new secrets needed.
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7432] Config: added 'ssid' value 'NetLink'
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7433] Config: added 'scan_ssid' value '1'
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7433] Config: added 'bgscan' value 'simple:30:-65:300'
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7433] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7433] Config: added 'psk' value '<hidden>'
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7597] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7597] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7691] device (wlp0s20f3): supplicant interface state: inactive -> authenticating
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7692] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> authenticating
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7985] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.7986] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8501] device (wlp0s20f3): supplicant interface state: associating -> completed
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8502] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NetLink"
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8502] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> completed
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8614] device (wlp0s20f3): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8618] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Jan 24 15:53:34 fedora NetworkManager[1039]: <info>  [1769288014.8691] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.80.120, acd pending
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0525] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.80.120
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0550] policy: set 'NetLink' (wlp0s20f3) as default for IPv4 routing and DNS
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0626] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0637] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0638] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0640] manager: NetworkManager state is now CONNECTED_SITE
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.0647] device (wlp0s20f3): Activation: successful, device activated.
Jan 24 15:53:35 fedora NetworkManager[1039]: <info>  [1769288015.1671] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5812] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:54:09 fedora NetworkManager[1039]: <warn>  [1769306049.5815] device (eth0): Activation: failed for connection 'Wired connection 2'
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5817] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5981] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5982] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5982] dhcp4 (eth0): state changed no lease
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5992] policy: auto-activating connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5995] device (eth0): Activation: starting connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5995] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.5996] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.6103] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:54:09 fedora NetworkManager[1039]: <info>  [1769306049.6106] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:54:26 fedora NetworkManager[1039]: <info>  [1769306066.7684] agent-manager: agent[e32cb9d84dbae10b,:1.45/org.gnome.Shell.NetworkAgent/60578]: agent registered
Jan 24 20:54:45 fedora NetworkManager[1039]: <info>  [1769306085.0364] agent-manager: agent[abf34a677330bd0b,:1.95/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5800] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:54:54 fedora NetworkManager[1039]: <warn>  [1769306094.5804] device (eth0): Activation: failed for connection 'Wired connection 2'
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5806] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5924] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5925] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5925] dhcp4 (eth0): state changed no lease
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5976] policy: auto-activating connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5986] device (eth0): Activation: starting connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5987] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.5991] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.6362] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:54:54 fedora NetworkManager[1039]: <info>  [1769306094.6395] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5854] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:55:39 fedora NetworkManager[1039]: <warn>  [1769306139.5861] device (eth0): Activation: failed for connection 'Wired connection 2'
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5863] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5939] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5940] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5940] dhcp4 (eth0): state changed no lease
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5956] policy: auto-activating connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5960] device (eth0): Activation: starting connection 'Wired connection 2' (70ef8950-bec3-31b7-9c2e-f3934a8ca62e)
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5961] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.5963] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.6117] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:55:39 fedora NetworkManager[1039]: <info>  [1769306139.6125] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5810] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:56:24 fedora NetworkManager[1039]: <warn>  [1769306184.5814] device (eth0): Activation: failed for connection 'Wired connection 2'
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5816] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5939] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5940] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5940] dhcp4 (eth0): state changed no lease
Jan 24 20:56:24 fedora NetworkManager[1039]: <info>  [1769306184.5950] manager: startup complete
Jan 24 20:56:25 fedora NetworkManager[1039]: <info>  [1769306185.6830] audit: op="connection-delete" uuid="70ef8950-bec3-31b7-9c2e-f3934a8ca62e" name="Wired connection 2" pid=5108 uid=1000 result="success"
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6043] audit: op="connection-add" uuid="9b6a65b2-54a2-455e-a6b5-19467ca1bc08" name="Profile 1" pid=5108 uid=1000 result="success"
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6047] policy: auto-activating connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6057] device (eth0): Activation: starting connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6058] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6060] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6193] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6202] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:56:42 fedora NetworkManager[1039]: <info>  [1769306202.6297] audit: op="device-reapply" interface="eth0" ifindex=2 pid=5108 uid=1000 result="success"
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5801] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:57:27 fedora NetworkManager[1039]: <warn>  [1769306247.5806] device (eth0): Activation: failed for connection 'Profile 1'
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5808] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5890] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5890] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5890] dhcp4 (eth0): state changed no lease
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5901] policy: auto-activating connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5907] device (eth0): Activation: starting connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5907] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.5911] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.6134] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:57:27 fedora NetworkManager[1039]: <info>  [1769306247.6141] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5809] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:58:12 fedora NetworkManager[1039]: <warn>  [1769306292.5815] device (eth0): Activation: failed for connection 'Profile 1'
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5818] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5929] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5930] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5930] dhcp4 (eth0): state changed no lease
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5942] policy: auto-activating connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5946] device (eth0): Activation: starting connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5946] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.5948] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.6069] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:58:12 fedora NetworkManager[1039]: <info>  [1769306292.6077] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5854] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:58:57 fedora NetworkManager[1039]: <warn>  [1769306337.5859] device (eth0): Activation: failed for connection 'Profile 1'
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5861] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5960] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5960] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5960] dhcp4 (eth0): state changed no lease
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5973] policy: auto-activating connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5977] device (eth0): Activation: starting connection 'Profile 1' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5977] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.5979] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.6111] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:58:57 fedora NetworkManager[1039]: <info>  [1769306337.6120] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:59:33 fedora NetworkManager[1039]: <info>  [1769306373.7684] audit: op="connection-update" uuid="9b6a65b2-54a2-455e-a6b5-19467ca1bc08" name="Eth0" args="connection.id" pid=5108 uid=1000 result="success"
Jan 24 20:59:33 fedora NetworkManager[1039]: <info>  [1769306373.7880] audit: op="device-reapply" interface="eth0" ifindex=2 args="connection.id" pid=5108 uid=1000 result="success"
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5801] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 20:59:42 fedora NetworkManager[1039]: <warn>  [1769306382.5804] device (eth0): Activation: failed for connection 'Eth0'
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5806] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5821] dhcp4 (eth0): canceled DHCP transaction
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5822] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5822] dhcp4 (eth0): state changed no lease
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5851] policy: auto-activating connection 'Eth0' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5855] device (eth0): Activation: starting connection 'Eth0' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5856] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.5857] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.6068] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 20:59:42 fedora NetworkManager[1039]: <info>  [1769306382.6075] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5788] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jan 24 21:00:27 fedora NetworkManager[1039]: <warn>  [1769306427.5793] device (eth0): Activation: failed for connection 'Eth0'
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5795] device (eth0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5869] dhcp4 (eth0): canceled DHCP transaction
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5870] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5870] dhcp4 (eth0): state changed no lease
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5882] policy: auto-activating connection 'Eth0' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5886] device (eth0): Activation: starting connection 'Eth0' (9b6a65b2-54a2-455e-a6b5-19467ca1bc08)
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5887] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.5889] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.6064] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 24 21:00:27 fedora NetworkManager[1039]: <info>  [1769306427.6076] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
16

Try using a static configuration to rule out DHCP related issues:

18

Manually setting ipv4 also didn’t help..

Is it the issue with drivers r8153/8152?

19

You apparently did not have wifi disabled when you got that log.
The interface eth0 appears to have automatically tried with different settings, named ‘Wired connection 2’ and ‘Profile 1’
That log section appears to show that the files in /etd/NetworkManager/system-connections may have still existed when the boot was performed. It also shows ```
device (eth0): state change: prepare → config (reason ‘none’, managed-type: ‘full’)
device (eth0): state change: config → ip-config (reason ‘none’, managed-type: ‘full’)