Bug 31402

Created attachment 13643 [details]
lspci - per Martin's suggestion

Created attachment 13644 [details]
Journal from live startup with ethernet issue

Thank you for the report.

From lspci:
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1025 subd:8000) (rev: 03)
looks OK.

From the journal, there are 69 lines for 'enp2s0', including references to IPV6, as well as IPV4. The link looks to go up & down then up, not sure. Many lines:
kernel: IPv4: martian source 255.255.255.255 from 192.168.10.234, on dev enp2s0

Assigning initially to Martin as it is about a Live test ISO, but please xfer it if appropriate.

Assignee: bugsquad => mageia

$ grep -i dhcp attachment.cgi\?id\=13644 
Jan 13 10:57:26 localhost NetworkManager[763]: <info>  [1673629046.5351] dhcp: init: Using DHCP client 'internal'
Jan 13 10:57:29 localhost NetworkManager[763]: <info>  [1673629049.0322] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 13 10:58:13 localhost NetworkManager[763]: <info>  [1673629093.9934] dhcp4 (enp2s0): canceled DHCP transaction
Jan 13 10:58:13 localhost NetworkManager[763]: <info>  [1673629093.9935] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 13 10:58:13 localhost NetworkManager[763]: <info>  [1673629093.9935] dhcp4 (enp2s0): state changed no lease
Jan 13 10:58:14 localhost NetworkManager[763]: <info>  [1673629094.0163] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 13 10:58:59 localhost NetworkManager[763]: <info>  [1673629139.0064] dhcp4 (enp2s0): canceled DHCP transaction
Jan 13 10:58:59 localhost NetworkManager[763]: <info>  [1673629139.0065] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 13 10:58:59 localhost NetworkManager[763]: <info>  [1673629139.0065] dhcp4 (enp2s0): state changed no lease
Jan 13 10:58:59 localhost NetworkManager[763]: <info>  [1673629139.0245] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)

Is the router configured to run a dhcp service?

CC: (none) => davidwhodgins

AP to router.  So this router (Netgear) is passing off the work to the primary router for DHCP.  Works with classic installer and everything else I have.  You triggered an interesting thought, when I bypassed the AP it did work.  

I spent an hour checking AP then went back and reinstalled from classic and it worked.

It does seem to be a problem with the NetworkManager DHCP client and your particular hardware setup. I've just tested the Mageia-9-beta1-Live-Xfce-x86_64 on my laptop with this ethernet interface:

r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:17aa subd:5097) (rev: 10)

connecting through a TP-Link Powerline adapter to my main router, and that has no problem getting a lease:

% grep -i dhcp journal.log 
Jan 14 15:28:51 localhost NetworkManager[1580]: <info>  [1673710131.2161] dhcp: init: Using DHCP client 'internal'
Jan 14 15:28:53 localhost NetworkManager[1580]: <info>  [1673710133.8734] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 15:28:53 localhost NetworkManager[1580]: <info>  [1673710133.8960] dhcp4 (enp2s0): state changed new lease, address=192.168.1.15
Jan 14 15:28:55 localhost NetworkManager[1580]: <info>  [1673710135.2208] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 15:28:55 localhost NetworkManager[1580]: <info>  [1673710135.2362] dhcp6 (enp2s0): state changed new lease

Just to confirm I'm not missing something, could you boot the Live ISO, open a terminal window, and try

  su -
  systemctl stop NetworkManager
  systemctl start network

Does that give a working network connection?

No it failed again.

Tried a couple of different configs, still failing.

oops - yes that worked.  

  systemctl stop NetworkManager
  systemctl start network

I was redoing my office and had unplugged the ethernet AP.   Amazing how plugging ethernet cable in helps.

As this seems to be a very hardware-specific problem and you've found a workaround, I'll close this as works-for-me.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED