[Resolved: faulty interface/cables] Cannot get IP address on Linux

cipone23 · 2023-04-06 18:57:54

Hi, first of all, there is something wrong with my ethernet outlet. But I am using a cable from that outlet in a different Mac computer, and I get 10Mbs instead of the regular 1000Mbs which is fine. Using another ethernet outlet works fine, and I can connect to 1000 MB, so there is no problem with the driver.

So I planned to use it for a home server running Arch Linux. The problem is that on Linux, it doesn't work at all. For some reason, it cannot get an IP

pr 06 14:48:11 um690-arch NetworkManager[9703]: <info>  [1680781691.1034] device (eno1): Activation: starting connection 'Wired connection 1' (b2838917-21c0-32a3-99af-657603b713f4)
Apr 06 14:48:11 um690-arch NetworkManager[9703]: <info>  [1680781691.1035] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 06 14:48:11 um690-arch NetworkManager[9703]: <info>  [1680781691.1038] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 06 14:48:11 um690-arch NetworkManager[9703]: <info>  [1680781691.1045] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 06 14:48:11 um690-arch NetworkManager[9703]: <info>  [1680781691.1048] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <info>  [1680781736.0771] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <warn>  [1680781736.0775] device (eno1): Activation: failed for connection 'Wired connection 1'
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <info>  [1680781736.0777] device (eno1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <info>  [1680781736.1153] dhcp4 (eno1): canceled DHCP transaction
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <info>  [1680781736.1153] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Apr 06 14:48:56 um690-arch NetworkManager[9703]: <info>  [1680781736.1153] dhcp4 (eno1): state changed no lease

My ethernet driver is Intel Corporation Ethernet Controller I225-V (rev 03).

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether d6:ef:33:6f:03:56  txqueuelen 1000  (Ethernet)
        RX packets 55847  bytes 76599885 (73.0 MiB)
        RX errors 6  dropped 0  overruns 0  frame 6
        TX packets 8321  bytes 1432503 (1.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 9
        device memory 0xdc900000-dc9fffff

Could anybody please give me some pointers on how to make it laxer, connect to 100Mbs, and ignore the errors?

[UPDATE]
A guy from the ISP company came and found out that one of the main wires of the network cable (the orange one) was interrupted. Since I could not change the cable because of some poor decisions I made when installing the flooring, he switched some wires between them (2 & 4), and now, at least, I can connect at 100Mb properly.

Last edited by cipone23 (2023-04-09 11:45:57)

seth · 2023-04-06 19:39:04

running Windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I get 100Mbs instead of the regular 1000Mbs

Cable is broken or undergraded.

For some reason, it cannot get an IP

Reason #1 is the cable (always and also in this case)
Reason #2 might be windows (see above)

Otherwise (since you've quite some RX and the error rate isn't /that/ horrible)
Please post the outputs of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
ethtool eno1

cipone23 · 2023-04-06 20:26:46

Thanks for helping out. I should've explained it better. I know the ethernet outline is faulty (probably the connection from the router to it got interrupted).; I tested it with different cables, and I can do nothing about it other than take out all my flooring. So, for the moment, I have to live with it. I am trying to find a solution to make it work on Linux.

Here's the output of the command that you pasted. I am going to do the windows section next.

ethtool eno1
bluetooth.service                        | bluetooth.target.wants
cpupower-gui.service                     | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.rnd2.cpupower_gui.helper.service | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants
Settings for eno1:
	Supported ports: [  ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	                        2500baseT/Full
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  100baseT/Half 100baseT/Full
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	MDI-X: off (auto)
netlink error: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
	Link detected: yes

But depending on the time I am running it, I might also get a

Settings for eno1:
	Supported ports: [  ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	                        2500baseT/Full
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  100baseT/Half 100baseT/Full
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: Unknown!
	Duplex: Unknown! (255)
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	MDI-X: off (auto)
netlink error: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
	Link detected: no

So I think it keeps on trying to reconnect.

cipone23 · 2023-04-06 20:41:53

I just tested fast startup in Windows. It is not enabled.

seth · 2023-04-06 20:46:18

I understood that the cable is known to be bad, but not that you can't easily replace it (what would the the bestmostsmart approach)
If it's not down to the dhcp server ignoring you because windows already got a lease, consider dhcpcd [-K] or dhclient instead of NM (stop/disable the latter)

You can also try "ethtool -s eno1 speed 100 autoneg off duplex full"

cipone23 · 2023-04-06 21:14:58

For some reason, I can set it to 100Mb but I can't turn off auto-negotiation. It might be related to the gigabit standard.

Running dhcpd manually didn't work either:

eno1: waiting for carrier
eno1: carrier acquired
eno1: IAID ca:70:66:4c
eno1: adding address fe80::f050:1636:ad8f:6d11
ipv6_addaddr1: Permission denied
eno1: soliciting an IPv6 router
eno1: soliciting a DHCP lease
eno1: carrier lost

I'll look into advertising only 100 Mb

cipone23 · 2023-04-06 21:34:11

I managed to advertise only 10/100 Mbs with

ethtool -s eno1 advertise 0x0f

, but it still wouldn't connect. So I think Mac and Windows are doing something different.

cipone23 · 2023-04-06 21:56:13

Ok, actually the speed at which Mac connects is

 media: autoselect (10baseT/UTP <full-duplex>)

> but that media type seems to not exist in Linux.

ifconfig eno1 media  10baseT/UTP
Unknown media type.

seth · 2023-04-07 05:17:02

ethtool -s eno1 speed 10

But that won't help you if the carrier drops out all the time.

Running dhcpd manually didn't work either:

eno1: carrier lost

Running *how* exactly?

So I think Mac and Windows are doing something different.

Yes, they ignore the carrier loss…

My ethernet driver is Intel Corporation Ethernet Controller I225-V

No, it's not, you're most likely using the igc module.

cipone23 · 2023-04-07 06:45:51

I just turned off NetworkManager, and did a

sudo dhcpcd

.
Anyway, I gave up on the idea, I think I will also use the Linux mini PC as a router, add connect my laptop to it. 10 MB is too low.

seth · 2023-04-07 07:31:39

Ftr, https://man.archlinux.org/man/core/dhcpcd/dhcpcd.8.en#K

cipone23 · 2023-04-07 11:03:28

Thanks, I also tried that, but I got the same thing, a 45-second transaction timeout.

The weird part is that when I tried connecting my raspberry pi running Raspbian, I got assigned a strange IP address: 169.254.188.110

-thc · 2023-04-07 12:13:04

This is an "APIPA" or link-local IPv4 address (https://en.wikipedia.org/wiki/Link-local_address#IPv4) and shows that raspian doesn't get a DHCP reply either.

cipone23 · 2023-04-07 12:36:05

ok, thanks.

seth · 2023-04-07 12:50:38

dhcpcd -K -t 0 eno1

You could also try to assign a static IP and see whether you get a somewhat usable communication.

Are you sure that windows still gets a lease right now (and doesn't just re-use a cached one)?

cipone23 · 2023-04-07 14:32:25

You know what, sorry I was wrong.

It looks like Windows was on WIFI; sorry about that. The cable works for another Mac computer (probably because of the USB-C network adapter), but it looks like my ethernet card can't handle it. I will edit the title.

I also tried the static IP, it wouldn't work.

Last edited by cipone23 (2023-04-07 14:37:43)

Arch Linux

#1 2023-04-06 18:57:54

[Resolved: faulty interface/cables] Cannot get IP address on Linux

#2 2023-04-06 19:39:04

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#3 2023-04-06 20:26:46

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#4 2023-04-06 20:41:53

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#5 2023-04-06 20:46:18

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#6 2023-04-06 21:14:58

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#7 2023-04-06 21:34:11

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#8 2023-04-06 21:56:13

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#9 2023-04-07 05:17:02

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#10 2023-04-07 06:45:51

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#11 2023-04-07 07:31:39

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#12 2023-04-07 11:03:28

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#13 2023-04-07 12:13:04

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#14 2023-04-07 12:36:05

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#15 2023-04-07 12:50:38

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

#16 2023-04-07 14:32:25

Re: [Resolved: faulty interface/cables] Cannot get IP address on Linux

Board footer