[SOLVED] IPv4 does not work at boot, but it starts working after

vpch1 · 2025-02-15 00:30:00

Hi, I recently installed Arch for the first time but I've been having an issue with ethernet.

After boot, while using Firefox, I noticed some websites weren't loading, but others were. After some time using my PC (10-30 mins), everything starts working as expected.
I tried using curl and these were the outputs:

curl -v duckduckgo.com
* Host duckduckgo.com:80 was resolved.
* IPv6: (none)
* IPv4: 52.149.246.39
*   Trying 52.149.246.39:80...
* connect to 52.149.246.39 port 80 from 192.168.0.11 port 46806 failed: Network is unreachable
* Failed to connect to duckduckgo.com port 80 after 16 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to duckduckgo.com port 80 after 16 ms: Could not connect to server

curl -v google.com
* Host google.com:80 was resolved.
* IPv6: 2607:f8b0:4008:80b::200e
* IPv4: 142.250.217.206
*   Trying [2607:f8b0:4008:80b::200e]:80...
* Connected to google.com (2607:f8b0:4008:80b::200e) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: google.com
> User-Agent: curl/8.12.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Location: http://www.google.com/
< Content-Type: text/html; charset=UTF-8
< Content-Security-Policy-Report-Only: object-src 'none';base-uri 'self';script-src 'nonce-7WM1hzfXzCKISa8QgEkDTA' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp
< Date: Fri, 14 Feb 2025 23:43:10 GMT
< Expires: Sun, 16 Mar 2025 23:43:10 GMT
< Cache-Control: public, max-age=2592000
< Server: gws
< Content-Length: 219
< X-XSS-Protection: 0
< X-Frame-Options: SAMEORIGIN
<
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
* Connection #0 to host google.com left intact

So I think it is an IPv4 issue, but I don't know how to fix it. Also, I'm using NetworkManager.

Last edited by vpch1 (2025-03-15 07:05:24)

impossibleveins23 · 2025-02-17 15:03:46

If you don't do anything, and it starts working, it might take a considerable time for the Ethernet link to stabilize or the DHCP to assign you address.

* Check what's the interface status when you boot and networking does not work: ip addr show <INT>. Does it have link and IP address? Can you reach the default gateway? The DNS IP?
* Upload journal: journalctl -b | curl -F 'file=@-' 0x0.st
*Did you try a different cable? Port?

vpch1 · 2025-02-20 21:32:53

Yes, I can reach the default gateway and DNS IP at boot:

ip addr show enp5s0
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 24:4b:fe:8e:df:7a brd ff:ff:ff:ff:ff:ff
    altname enx244bfe8edf7a
    inet 192.168.0.11/24 brd 192.168.0.255 scope global dynamic noprefixroute enp5s0
       valid_lft 3565sec preferred_lft 3565sec
    inet6 2803:d100:e080:37b:25dc:2101:ee57:6f33/64 scope global dynamic noprefixroute
       valid_lft 3599sec preferred_lft 3599sec
    inet6 fe80::8ac6:d01:e774:9618/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

This is the journal right after everything started working: http://0x0.st/8TrJ.txt

And yes, I have tried a different cable and it didn't work either.

impossibleveins23 · 2025-02-20 22:05:29

I reread your posts and now understand only parts of the websites are not loading.

* Did you try a different browser? CURL request?
* Try changing the DNS to 1.1.1.1 for instance and check if it helps

vpch1 · 2025-02-20 22:41:09

Oh no, the websites do not load at all.
For example, YouTube works as expected, but Firefox shows an error screen when trying to go to Reddit.

Also, no other browser works and I already have 1.1.1.1 as my primary nameserver.

impossibleveins23 · 2025-02-21 09:52:40

From your 1st post, seems that you do have DNS resolution but can't reach the site with curl. So probably not a DNS or browser problem.

Perhaps something with the router (restarting it help?). Can you try with the WiFi interface (make sure it is the primary)? With Different internet connection?

kalavan · 2025-02-21 10:50:08

Feb 20 14:49:06 arch NetworkManager[587]: <info> [1740084546.2496] dhcp4 (enp5s0): state changed new lease, address=192.168.0.11
Feb 20 14:49:06 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 20 14:49:06 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 20 14:49:16 arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

It seems that your ipv4 lease was renewed. It might change some DNS settings or routing maybe?

Your start sequence in this log is:
* get ipv4 lease
* get ipv6 lease
* renew ipv4 after some time

You might check routing settings after reboot. Force ipv4 lease renewal and check if something changed.
You could disable ipv6 at all

I will leave smarter comments to others

vpch1 · 2025-03-01 07:00:56

I tried forcing a lease renewal using nmcli con down & nmcli con up, but nothing changed as far as I could tell.
Disabling IPv6 didn't help either, it only gave me a "limited connectivity warning".

After boot, restarting the router worked. I turned it off and on, and after that, everything started working. I tried two times and they both worked.
Also, WiFi works perfectly even when ethernet doesn't.

impossibleveins23 · 2025-03-01 08:50:00

So the router's switch is the culprit?

vpch1 · 2025-03-15 07:04:01

Sorry for the late reply.
Yes, it was an issue with the router and I finally managed to fix it.

Thank you for your help!

Arch Linux

#1 2025-02-15 00:30:00

[SOLVED] IPv4 does not work at boot, but it starts working after

#2 2025-02-17 15:03:46

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#3 2025-02-20 21:32:53

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#4 2025-02-20 22:05:29

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#5 2025-02-20 22:41:09

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#6 2025-02-21 09:52:40

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#7 2025-02-21 10:50:08

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#8 2025-03-01 07:00:56

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#9 2025-03-01 08:50:00

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

#10 2025-03-15 07:04:01

Re: [SOLVED] IPv4 does not work at boot, but it starts working after

Board footer