You are not logged in.
Pages: 1
Hi,
been trying to investigate this for around a week. I now surrender not to break things.
I have recently changed router, and two linux machines have stopped working wired.
On this arch linux machine I am writing from, wirelessly, at power on and while boot-up network card led blinks green but then on completion of bootup process will stay dead.
I do not understand whether it is a dhcp issue, local or remote. Once when I was able to bring enp3s0 up, I saw three (!) different IPs router side against the same mac address.
Thanks.
EDIT
LSB_VERSION=1.4
DISTRIB_ID=Arch
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="Arch Linux"
NAME="Arch Linux"
ID=arch
PRETTY_NAME="Arch Linux"
Last edited by ferrvittorio (2016-06-27 06:56:59)
Offline
Details of your network management tool, card, driver and the relevant journal output would be a start.
Please see How To Ask Questions The Smart Way
Moving to NC...
Offline
From the last days logs (but not from today's?) seems thah enp3s0 stopped negotiating ipv4 (?) only trying to negotiate ipv6 (??)
$ journalctl --priority 2..3 |grep enp3s0
giu 20 20:17:51 evo ntpd[396]: unable to create socket on enp3s0 (20) for fe80::61d5:4fd5:7539:2760%2#123
giu 20 20:18:37 evo ntpd[396]: unable to create socket on enp3s0 (24) for fe80::61d5:4fd5:7539:2760%2#123
giu 20 20:18:40 evo dhcpcd[4682]: enp3s0: hardware address 60:02:b4:f9:79:5c claims 0.0.0.0
giu 20 20:18:42 evo dhcpcd[4682]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 0.0.0.0
giu 20 20:18:43 evo dhcpcd[4682]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 0.0.0.0
giu 21 09:04:06 evo ntpd[393]: unable to create socket on enp3s0 (6) for fe80::61d5:4fd5:7539:2760%2#123
giu 21 09:04:11 evo dhcpcd[324]: enp3s0: DHCP lease expired
giu 21 09:04:35 evo ntpd[393]: unable to create socket on enp3s0 (8) for fe80::61d5:4fd5:7539:2760%2#123
giu 21 09:04:52 evo ntpd[393]: unable to create socket on enp3s0 (11) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:12:35 evo ntpd[380]: unable to create socket on enp3s0 (8) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:13:25 evo ntpd[380]: unable to create socket on enp3s0 (12) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:14:21 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:21 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:21 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:21 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:21 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:22 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:14:22 evo dhcpcd[322]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 192.168.0.4
giu 24 10:18:41 evo dhcpcd[322]: enp3s0: DHCP lease expired
giu 24 10:19:17 evo ntpd[380]: unable to create socket on enp3s0 (20) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:19:34 evo ntpd[380]: unable to create socket on enp3s0 (22) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:35:59 evo dhcpcd[322]: enp3s0: DHCP lease expired
giu 24 10:36:35 evo ntpd[380]: unable to create socket on enp3s0 (31) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 10:36:52 evo ntpd[380]: unable to create socket on enp3s0 (33) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 14:57:41 evo ntpd[370]: unable to create socket on enp3s0 (6) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 14:57:46 evo dhcpcd[316]: enp3s0: DHCP lease expired
giu 24 14:58:11 evo ntpd[370]: unable to create socket on enp3s0 (8) for fe80::61d5:4fd5:7539:2760%2#123
giu 24 14:58:28 evo ntpd[370]: unable to create socket on enp3s0 (11) for fe80::61d5:4fd5:7539:2760%2#123
Offline
Details of your network management tool, card, driver and the relevant journal output would be a start.
Please see How To Ask Questions The Smart Way
Moving to NC...
Hi,
I have these
systemctl --type=service |grep Network
NetworkManager.service loaded active running Network Manager
ntpd.service loaded active running Network Time Service
lspci -k | grep Ethernet
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
dmesg | grep 'Ethernet driver'
[ 9.689049] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Offline
'ntpd' synchronizes your system's time, and is, for this problem, irrelevant.
This line
giu 20 20:18:43 evo dhcpcd[4682]: enp3s0: hardware address a4:67:06:a6:40:e0 claims 0.0.0.0
is reminiscent of https://bbs.archlinux.org/viewtopic.php?id=213326. What version of dhcpcd do you have?
Are you using a static IP? If so, does anyone else on your network use 192.168.0.4?
Edit: is ''a4:67:06:a6:40:e0" tha MAC address of your ethernet card, or another device on the network?
Last edited by \hbar (2016-06-27 13:10:56)
Offline
Hi, great!
Think we are going in the right direction, why is eth claiming 4?
A4:67:06:A6:40:E0 ip#4 has always been an ipad, no duplicate MACs in subnet, and this client should not have a static ip
Offline
dhcpcd --version
dhcpcd 6.11.1
Copyright (c) 2006-2016 Roy Marples
... and now seems to work correctly?
Offline
... and now seems to work correctly?
Are you saying it works, or are you asking?
So, if I'm getting this straight, a4:67:06:a6:40:e0 is an iPad whose IP address is 192.168.0.4? If so, what happens if you ask for a static IP that is not 192.168.0.4?
Offline
Hi,
I meant I got assigned and IP thru eth card
ip addr show dev enp3s0
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 40:16:7e:29:3d:64 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 brd 192.168.0.255 scope global dynamic enp3s0
valid_lft 83897sec preferred_lft 83897sec
inet6 fe80::61d5:4fd5:7539:2760/64 scope link
valid_lft forever preferred_lft forever
thanking you Hbar for all the above, basically I solved wiring with a spare better cable.
Due to a firmware bug, I assume that router "does not like" distant connections with realtek low power cards.
Moreover I add that router will not allow me to reserve this IP ("The IP address should be within the DHCP range.")
I will probably have to investigate with windows/ explorer.
Offline
Pages: 1