[SOLVED] Ethernet is up but does not connect to the web

RedArcher · 2020-10-01 06:30:03

3 weeks ago or so, my machine has alternately stopped to connect to Ethernet connection (device: enp24s0) and eventually this problem became permanent.

pacman and ping do manage to connect to the Ethernet device and connect to the Internet.
Web Browsers, and P2P software don't manage to connect to the Ethernet device and connect to the Internet.
Conky doesn't indicate that enp24s0 is even connected.

When connecting a cellphone with Tethering activated, everything normally connects to the Internet.
This problem occurs only with the Ethernet connection.

I'm using NetworkManager.

Last edited by RedArcher (2020-10-29 16:41:08)

solskog · 2020-10-01 08:02:10

If you can manage to install and run:

# pacman -S mtr
$ mtr 8.8.8.8
Host  Loss%   Snt   Last   Avg  Best  Wrst StDev
...

It will tell you where you have packet drop.

RedArcher · 2020-10-01 08:27:00

OUTPUT OF UNRELATED INTERFACE DELETED

Correct output:

$ mtr 8.8.8.8
mtr: udp socket connect failed: Network is unreachable

Last edited by RedArcher (2020-10-01 08:51:58)

solskog · 2020-10-01 08:35:00

9. customer-213-57-119-249.hotnet.net.il 92.6% 82 72.9 85.0 28.9 183.7 59.1
10. ae3.bkp.pt.mx-mx.con.hotnet.net.il 95.1%

The problem doesn't seems on your local network. What is your name resolver?

$ cat /etc/resolv.conf
...

Try and change to other name resolver via networkmanager.
And you can also check your ethernet status by this:

# pacman -S ethtool
# ethtool enp24s0
...

Last edited by solskog (2020-10-01 08:39:26)

RedArcher · 2020-10-01 08:41:52

Please ignore my previews post. I was connected to Ethernet interface.

Here is the proper output:

$ mtr 8.8.8.8
mtr: udp socket connect failed: Network is unreachable

Here are the couple of other outputs:

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
nameserver 192.168.42.129

# ethtool enp24s0
netlink error: No such file or directory
Settings for enp24s0:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full 
	                                     100baseT/Half 100baseT/Full 
	                                     1000baseT/Full 
	Link partner advertised pause frame use: Symmetric
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 0
	Transceiver: external
	Auto-negotiation: on
	Supports Wake-on: pumbg
	Wake-on: d
	Link detected: yes

Last edited by RedArcher (2020-10-01 08:51:06)

solskog · 2020-10-01 08:53:30

Your ethernet device is good.

nameserver 192.168.42.129

Is this your ethernet router? Try and change from your networkmanager to use another nameserver instead. e.g: 1.1.1.1 or 208.67.222.222 and remove IPV6 resolver from networkmanager pls.
the result should look like this:

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 1.1.1.1
nameserver 208.67.222.222

Then try again with "mtr archlinux.org". You don't have to show the output from mtr just let me known if you still have very high drop between your localnetwork and archlinux.org

Last edited by solskog (2020-10-01 09:07:10)

RedArcher · 2020-10-01 09:09:48

solskog wrote:

Is this your ethernet router?

Yes, some type of a regional edition :/

solskog wrote:

Try and change from your networkmanager to use another nameserver instead. e.g: 1.1.1.1 or 208.67.222.222 and remove IPV6 resolver from networkmanager pls.
the result sould look like this:
$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 1.1.1.1
nameserver 208.67.222.222

Can I change it manually?
I barely have any experience configuring it, neither CLI nor GUI.

solskog wrote:

Then try again with "mtr archlinux.org". You don't have to show the output from mtr just let me known if you still have very high drop between your localnetwork and archlinux.org

I didn't make the suggested changes, yet here's the output:

                                              My traceroute  [v0.94]
workstation (2a00:a040:188:8cbf:ca38:290c:f821:3318) -> archlinux.org                     2020-10-01T12:05:26+0300
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                          Packets               Pings
 Host                                                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2a00:a040:188:8cbf:b6ee:b4ff:fea6:b57d                               0.0%    90    4.3   4.0   3.5   5.1   0.3
 2. 2a00:a040:188:8000::1                                                0.0%    90   16.5  20.6  10.6 170.7  25.9
 3. (waiting for reply)
 4. (waiting for reply)
 5. 2a00:a040:0:1:231::115                                               0.0%    90   13.9  15.0  12.6  28.6   2.6
 6. 2a00:a040:0:1::d                                                     0.0%    90   14.6  15.4  12.5  49.8   4.1
 7. 2a00:a040:0:70::2                                                    0.0%    90   67.4  67.8  65.6  79.7   2.0
 8. hotnet.franco31.fra.seabone.net                                      0.0%    90   75.1  77.9  74.6 110.3   4.7
 9. lo0.francoforte34.fra.seabone.net                                   12.4%    90  528.4 525.1 494.7 564.9  13.5
10. ae-9.r00.frnkge13.de.bb.gin.ntt.net                                  0.0%    90   71.2  70.7  67.6  82.4   1.9
11. ae-2.r20.frnkge13.de.bb.gin.ntt.net                                 95.5%    90   72.7  74.1  72.7  76.0   1.6
12. ae-5.r01.frnkge13.de.bb.gin.ntt.net                                  0.0%    90   74.2  73.2  69.5  80.2   1.7
13. 2001:728:0:5000::f6e                                                 0.0%    90   66.1  70.0  65.6 102.3   5.2
14. core23.fsn1.hetzner.com                                              1.1%    90   73.5  76.7  70.9 113.3   7.6
15. ex9k2.dc8.fsn1.hetzner.com                                           0.0%    89   84.8  84.7  76.4  92.0   2.1
16. apollo.archlinux.org                                                 0.0%    89   84.1  85.3  82.5  92.6   1.4

Every now and then it quits the program and shows:

mtr: Address not available

Last edited by RedArcher (2020-10-01 09:33:07)

solskog · 2020-10-01 09:27:08

I think your router's dns forwarder/resolver has issue using udp packets. And this issue is more complex then changing the name resolver from networkmanager. If you change it manually, it wouldn't remain.

To stop NetworkManager from touching /etc/resolv.conf, set main.dns=none with a configuration file in /etc/NetworkManager/conf.d/.
https://wiki.archlinux.org/index.php/NetworkManager

Then you can change /etc/resolv.conf manually.

RedArcher · 2020-10-01 09:40:01

It seems to work, but I don't know for how much time.

# cat /etc/resolv.conf
# Generated by resolvconf
nameserver 1.1.1.1
nameserver 208.67.222.222

# killall dhcpcd ; sleep 2 ; killall dhcpcd ; dhcpcd enp24s0
dhcpcd: no process found
dhcpcd-9.2.0 starting
DUID 00:04:cf:a4:c8:6b:bd:cb:50:40:b2:26:3d:cb:76:78:66:6e
enp24s0: IAID 61:36:0f:45
enp24s0: soliciting an IPv6 router
enp24s0: Router Advertisement from fe80::b6ee:b4ff:fea6:b57d
enp24s0: adding address 2a00:a040:188:8cbf:ca38:290c:f821:3318/64
enp24s0: adding route to 2a00:a040:188:8cbf::/64
enp24s0: adding default route via fe80::b6ee:b4ff:fea6:b57d
forked to background, child pid 33895

No connection. Trying again with IPv4:

# killall dhcpcd ; sleep 2 ; killall dhcpcd ; dhcpcd -4 enp24s0
dhcpcd: no process found
dhcpcd-9.2.0 starting
DUID 00:04:cf:a4:c8:6b:bd:cb:50:40:b2:26:3d:cb:76:78:66:6e
enp24s0: IAID 61:36:0f:45
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: ignoring offer of 192.168.100.21 from 192.168.100.1
enp24s0: NAK: from 192.168.100.1
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: ignoring offer of 192.168.100.22 from 192.168.100.1
enp24s0: NAK: from 192.168.100.1
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: ignoring offer of 192.168.100.23 from 192.168.100.1
enp24s0: NAK: from 192.168.100.1
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: ignoring offer of 192.168.100.24 from 192.168.100.1
enp24s0: NAK: from 192.168.100.1
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: ignoring offer of 192.168.100.25 from 192.168.100.1
enp24s0: NAK: from 192.168.100.1
enp24s0: soliciting a DHCP lease
enp24s0: offered 192.168.1.16 from 192.168.1.1
enp24s0: probing address 192.168.1.16/24
enp24s0: leased 192.168.1.16 for 3600 seconds
enp24s0: adding route to 192.168.1.0/24
enp24s0: adding default route via 192.168.1.1
forked to background, child pid 34096

Last edited by RedArcher (2020-10-01 09:40:51)

solskog · 2020-10-01 09:47:13

what is your

$ ip -4 route show
$ mtr -n 192.168.42.129

RedArcher · 2020-10-01 09:49:17

$ ip -4 route show
default via 192.168.1.1 dev enp24s0 proto dhcp src 192.168.1.16 metric 202 
192.168.1.0/24 dev enp24s0 proto dhcp scope link src 192.168.1.16 metric 202

                                              My traceroute  [v0.94]
workstation (192.168.1.16) -> 192.168.42.129                                              2020-10-01T12:50:43+0300
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                          Packets               Pings
 Host                                                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.1.1                                                          0.0%    28    4.2  18.7   3.6 394.4  73.7
 2. (waiting for reply)

solskog · 2020-10-01 10:03:17

Do you have a intermediate router that forward all your packets from 192.168.1.16 to 192.168.42.129?

RedArcher · 2020-10-01 10:18:04

I guess so, yes.
I'm connected to a small (proprietary) box, which depends on a main (proprietary all-in-one) box.

More details:
Both products are branded but of very low quality and are difficult to customize, and in someway are fixed (i.e. trying to set a common WiFi channel for Mesh Networking seems to be a big challenge).

solskog · 2020-10-01 10:32:49

Your router keep offering two subnets via dhcp, only one 192.168.1.0/24 is accepted by your PC. If your routers are not reliable and you can't configure it, try use static Ip address on your pc instead.

Last edited by solskog (2020-10-01 11:10:53)

Lone_Wolf · 2020-10-01 10:47:10

Smells like your provider uses carrier-grade NAT

Try connecting directly to a ipv6 site from browser to see if that works.
example

http://[2001:9a8:0:e:1337:0:80:1]/

You should get a 408 bad request from tweakers.net (a dutch tech news site)

RedArcher · 2020-10-01 11:00:45

solskog wrote:

If your routers are not reliable, try use static Ip address instead DHCP.

What is the way to know what type of IP I should pick?

Lone_Wolf wrote:

Smells like your provider uses carrier-grade NAT
Try connecting directly to a ipv6 site from browser to see if that works.
example
http://[2001:9a8:0:e:1337:0:80:1]/
You should get a 408 bad request from tweakers.net (a dutch tech news site)

I get 400 Bad Request.
I'm still connected to the web using dhcpcd -4 enp24s0.

Last edited by RedArcher (2020-10-01 11:01:47)

solskog · 2020-10-01 11:11:39

Your router keep offering two subnets via dhcp, only one 192.168.1.0/24 is accepted by your PC.

Lone_Wolf · 2020-10-01 11:16:44

oops, should indeed be 400 bad request.

Did you see a page mentioning tweakers with dutch text ?
If yes, your browser does work when using ipv6 addresses .

That would suggest the problem is not with ip addresses or route but with name resolving .
Try setting an alternative dns-server (preferably one with ipv6 and dnssec) , https://wiki.archlinux.org/index.php/Al … S_services

RedArcher · 2020-10-01 11:27:38

Lone_Wolf wrote:

oops, should indeed be 400 bad request.
Did you see a page mentioning tweakers with dutch text ?
If yes, your browser does work when using ipv6 addresses .

Picture:

https://pix.louiz.org/o/cqyVw.png

Lone_Wolf wrote:

That would suggest the problem is not with ip addresses or route but with name resolving .
Try setting an alternative dns-server (preferably one with ipv6 and dnssec) , https://wiki.archlinux.org/index.php/Al … S_services

What should I do, then?

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2020-10-29 19:17:00)

Lone_Wolf · 2020-10-02 13:52:30

I may have interpreted the result incorrectly, time to investigate dns lookup.

run and post outputs of (drill comes with ldns package)

$ drill -4 duckduckgo.com
$ drill -4 -t duckduckgo.com
$ drill -6 duckduckgo.com
$ drill -6 -t duckduckgo.com

RedArcher · 2020-10-29 16:40:49

drill didn't work, and indicated machine is offline.
Eventually, I have switched to the main box, it seems ok now.

Thank you for your help!

Last edited by RedArcher (2020-10-29 16:41:37)

Arch Linux

#1 2020-10-01 06:30:03

[SOLVED] Ethernet is up but does not connect to the web

#2 2020-10-01 08:02:10

Re: [SOLVED] Ethernet is up but does not connect to the web

#3 2020-10-01 08:27:00

Re: [SOLVED] Ethernet is up but does not connect to the web

#4 2020-10-01 08:35:00

Re: [SOLVED] Ethernet is up but does not connect to the web

#5 2020-10-01 08:41:52

Re: [SOLVED] Ethernet is up but does not connect to the web

#6 2020-10-01 08:53:30

Re: [SOLVED] Ethernet is up but does not connect to the web

#7 2020-10-01 09:09:48

Re: [SOLVED] Ethernet is up but does not connect to the web

#8 2020-10-01 09:27:08

Re: [SOLVED] Ethernet is up but does not connect to the web

#9 2020-10-01 09:40:01

Re: [SOLVED] Ethernet is up but does not connect to the web

#10 2020-10-01 09:47:13

Re: [SOLVED] Ethernet is up but does not connect to the web

#11 2020-10-01 09:49:17

Re: [SOLVED] Ethernet is up but does not connect to the web

#12 2020-10-01 10:03:17

Re: [SOLVED] Ethernet is up but does not connect to the web

#13 2020-10-01 10:18:04

Re: [SOLVED] Ethernet is up but does not connect to the web

#14 2020-10-01 10:32:49

Re: [SOLVED] Ethernet is up but does not connect to the web

#15 2020-10-01 10:47:10

Re: [SOLVED] Ethernet is up but does not connect to the web

#16 2020-10-01 11:00:45

Re: [SOLVED] Ethernet is up but does not connect to the web

#17 2020-10-01 11:11:39

Re: [SOLVED] Ethernet is up but does not connect to the web

#18 2020-10-01 11:16:44

Re: [SOLVED] Ethernet is up but does not connect to the web

#19 2020-10-01 11:27:38

Re: [SOLVED] Ethernet is up but does not connect to the web

#20 2020-10-02 13:52:30

Re: [SOLVED] Ethernet is up but does not connect to the web

#21 2020-10-29 16:40:49

Re: [SOLVED] Ethernet is up but does not connect to the web

Board footer