You are not logged in.
Hi,
After booting my system it takes around 1 minute to connect to wired network (ping not responding). It was working correctly, instant connect, but around 2 months ago something changed, I was not changing anything in configuration nor router settings. I have configured static ip address by dhcpcd.
cat /etc/dhcpcd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu
# Most distributions have NTP support.
#option ntp_servers
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private
noipv4ll
interface eno1
static ip_address=192.168.0.25/24
static routers=192.168.0.1
static domain_name_servers=8.8.8.8 8.8.4.4ip route show
default via 192.168.0.1 dev eno1 src 192.168.0.25 metric 1002
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-311ed84a26bf proto kernel scope link src 172.18.0.1 linkdown
192.168.0.0/24 dev eno1 proto dhcp scope link src 192.168.0.25 metric 1002any thoughts what could happened?
Last edited by bartoszw (2023-01-26 10:13:15)
Offline
Have you checked the journal for clues?
Jin, Jîyan, Azadî
Offline
As I understand network getting connected under one second?
boot on:
Jan 26 08:05:56 bb kernel: Linux version 6.1.5-arch2-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Thu, 12 Jan 2023 22:42:33 +0000
journalctl -b | grep dhcpcd
Jan 26 08:05:56 bb systemd[1]: Created slice Slice /system/dhcpcd.
Jan 26 08:05:57 bb systemd[1]: Starting dhcpcd on eno1...
Jan 26 08:05:57 bb dhcpcd[673]: dhcpcd-9.4.1 starting
Jan 26 08:05:57 bb dhcpcd[678]: DUID 00:04:3e:da:xx:8c:42:e9:xx:c1:8f:4a:xx:d4:c4:54:cc:ae
Jan 26 08:05:58 bb systemd[1]: Started dhcpcd on eno1.
Jan 26 08:05:58 bb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@eno1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 26 08:05:58 bb dhcpcd[678]: eno1: waiting for carrier
Jan 26 08:06:19 bb dhcpcd[678]: eno1: carrier acquired
Jan 26 08:06:19 bb dhcpcd[678]: eno1: IAID c4:54:xx:ae
Jan 26 08:06:19 bb dhcpcd[678]: eno1: adding address fe80::xxxx:xxxx:36b8:7cef
Jan 26 08:06:19 bb dhcpcd[678]: eno1: probing address 192.168.0.25/24
Jan 26 08:06:20 bb dhcpcd[678]: eno1: soliciting an IPv6 router
Jan 26 08:06:25 bb dhcpcd[678]: eno1: using static address 192.168.0.25/24
Jan 26 08:06:25 bb dhcpcd[678]: eno1: adding route to 192.168.0.0/24
Jan 26 08:06:25 bb dhcpcd[678]: eno1: adding default route via 192.168.0.1
Jan 26 08:06:33 bb dhcpcd[678]: eno1: no IPv6 Routers availableSo it should be ok?
Last edited by bartoszw (2023-01-26 08:28:52)
Offline
journalctl -b | grep dhcpcd
tells us what dhcpcd does and when, it won't explain any issues w/ your network stack that are not directly caused by dhcpcd bugs.
=> Post the entire journal.
Your grep shows that dhcpcd acts on eno1 at 08:05:58, then waits for 21 seconds for a carrier (until the NIC recognizes that a cable is plugged) and 6 seconds later has a lease.
Sanity check: is there a parallel windows installation?
Also check the cable. Plugs are part of the cable and they exist on both sides.
Offline
I can't believe, I have changed cable and everything connecting instantly. It should the first thing to check. Thanks for help!
Offline
I can.
Rule #1 - it's always the cable.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline