I’m unable to configure either of my two wired network connections (eth0 & eth1), but my wireless adapter is configured and appears to work just fine. When eth0 or eth1 are plugged in, their state is “UP.”
After running “ip a”, I noticed that no IPv4 or IPv6 addresses were assigned to either eth0 or eth1.
I ran “sudo dhclient -v eth1” and got the following output:
"Internet Systems Consortium DHCP Client 4.3.6-P1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit ISC DHCP - ISC
Listening on LPF/eth1/70:85:c2:3e:0a:7f
Sending on LPF/eth1/70:85:c2:3e:0a:7f
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17 (xid=0x1fa7e09f)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0x1fa7e09f)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
"
Good you tried dhclient -v and it shows a request is going out but no reply being received.
What to do:
Check the counters using ip stats show dev eth1, are there RX and TX bytes/packets?
Please check the cable, are there LED’s on on the Ethernet connectors? Are they blinking when you issue dhclient?
Do you know the subnet you are on? If so you could use the NetworkManager to set a static IP address and see if that works (ping the default gateway etc.)
I have two lights. One solid green and a blinking amber light. When issuing dhclient, the amber light blinks a few more times than usual over the course of the request.
I tried ip -s link show eth1 and this is what was returned:
“2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 70:85:c2:3e:0a:7f brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
662700 11045 0 1 0 0
TX: bytes packets errors dropped carrier collsns
10430953 50840 0 0 0 0
altname enp2s0”
Unfortunately, I don’t know the subnet I’m on. I’m setting this system up on my university’s network, so I suppose I’ll have to get in contact with my IT department for those details?
The Tx/Rx byte/packet counters show Ethernet frames are transmitted and received and the green/amber light also indicate Ethernet is working fine.
Yes, would be good to ask them if DHCP is enabled on the network and if so ask them if it is needed to register your MAC address. If that does not help ask them for a static address.
While they did not give me explicit details of what was wrong, my IT department confirmed that the issue was on their end. My network cards are now working fine.
In many ways this sounds like problems similar to what I am encountering,…but enough different I am not sure whether to try any of the previous suggestions.
I just built a dual-boot machine (Windows 11 Pro, Leap 15.6) and just this day installed the two OS on different NVMe drives. I went first with Windows, and subsequently downloaded the Chromium browser, LibreOffice and Acrobat Reader with no problems over my home network.
The new build is on a Gigabyte X870E Aorus Elite, has integrated graphics and an onboard LAN. During the 15.6 install, a network connection was not automatically configured during the early part of the install, but I didn’t think much of that occurrence. The install (from a USB drive) went fine, but when I subsequently went to add additional packages in Yast, I got the error that no network connection was available. I had previously gone into the administrator settings to give the new machine a name, but again, no connection was configured. However, if I go to my router, and try to set permanent addresses, it lists that machine name as a possible connection. Typing in the MAC address and assigning a local address doesn’t do anything. On the other hand, I gave the machine the same name on the Windows side, so perhaps that is confusing things here.
If I look at the ethernet port on the back of the machine, I have a green connection light and the same sporadic amber flash on the activity light.
It is probably irrelevant, but I have gone into the BIOS and successively Disabled-Saved and then Enabled-Saved, and that has not cleared the problem.