[SOLVED] Issues Connecting to Ethernet | Arch Linux Community | Page 1

strong cape Feb 25, 2026, 12:14 AM

#

Hey guys.
I just bought this new ethernet cable and plugged it into my PC. However, when selecting "Wired connection 1" in the network settings, it just keeps saying "Connecting" and never fully connects. Is there a fix for this? TIA

#

I'm not sure if this matters. But there are lights on each end of this Cat6 cable. The end that's connected to my router has a green light, and the other end that's in my PC is red.

low anchor Feb 25, 2026, 12:48 AM

#

strong cape I'm not sure if this matters. But there are lights on each end of this Cat6 cabl...

What is the output of ip link?

strong cape Feb 25, 2026, 1:09 AM

#

low anchor What is the output of `ip link`?

Hmm...it seems to be working now. However, the end that's plugged into my PC is still red. What does that mean?

low anchor Feb 25, 2026, 1:13 AM

#

strong cape Hmm...it seems to be working now. However, the end that's plugged into my PC is ...

The red light on the Ethernet port is usually not a problem. The LEDs on Ethernet ports just indicate link status and speed/activity, and the colors differ by manufacturer.

low anchor Feb 25, 2026, 1:13 AM

#

strong cape Hmm...it seems to be working now. However, the end that's plugged into my PC is ...

Check ethtool $(ip route | awk '/default/ {print $5}')

strong cape Feb 25, 2026, 1:18 AM

#

low anchor Check `ethtool $(ip route | awk '/default/ {print $5}')`

        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 Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        master-slave cfg: preferred slave
        master-slave status: slave
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        MDI-X: Unknown
netlink error: Operation not permitted
        Link detected: yes

low anchor Feb 25, 2026, 1:19 AM

#

strong cape ```Settings for enp5s0: Supported ports: [ TP MII ] Supported...

Everything is normal.

strong cape Feb 25, 2026, 1:20 AM

#

low anchor Everything is normal.

Hmmm. Just a few minutes ago I was getting some good speeds on speedtest.net. Now it's becoming a wee bit unstable and slow.

#

now it's back to high speeds....isn't ethernet supposed to make this stable tho?

low anchor Feb 25, 2026, 1:21 AM

#

strong cape Hmmm. Just a few minutes ago I was getting some good speeds on speedtest.net. No...

Show me a pic of the cable!

low anchor Feb 25, 2026, 1:21 AM

#

strong cape now it's back to high speeds....isn't ethernet supposed to make this stable tho?

Yeah, it should be stable. Unless something else is going on.

strong cape Feb 25, 2026, 1:21 AM

#

low anchor Show me a pic of the cable!

https://a.co/d/0bYYWmQk

#

I had to buy it this long due to where my router is.

low anchor Feb 25, 2026, 1:22 AM

#

strong cape https://a.co/d/0bYYWmQk

Is it 35ft long?

strong cape Feb 25, 2026, 1:22 AM

#

Yes

#

See now the speeds are looking normal.

low anchor Feb 25, 2026, 1:23 AM

#

strong cape Yes

That's why.

strong cape Feb 25, 2026, 1:23 AM

#

low anchor That's why.

Even if it's a Cat6?

#

#

I mean it gets stable when it wants to.

#

the meter is holding these positions solid.

#

download jitters a wee bit tho

compact quartz Feb 25, 2026, 1:25 AM

#

i need some help guys

low anchor Feb 25, 2026, 1:25 AM

#

strong cape Even if it's a Cat6?

Long Cat6 cable should still be stable. Length alone usually isn’t the problem unless it’s extremely long or the cable quality is poor.
Run ping -c 50 1.1.1.1

compact quartz Feb 25, 2026, 1:26 AM

#

im using an old pc i7 3770s 16gb ddr3 and rx 580 8gb, im on an windows right now and i want to switch on linux, but idk witch linux is better for games on garuda linux i have 50-90 fps on cs2 and on windows 190-200, wich linux i need to use for better gaming?

low anchor Feb 25, 2026, 1:26 AM

#

compact quartz i need some help guys

Make #1006743093120352338 ticket about it.

compact quartz Feb 25, 2026, 1:26 AM

#

ok

low anchor Feb 25, 2026, 1:26 AM

#

compact quartz im using an old pc i7 3770s 16gb ddr3 and rx 580 8gb, im on an windows right now...

Try CachyOS.

strong cape Feb 25, 2026, 1:26 AM

#

low anchor Long Cat6 cable should still be stable. Length alone usually isn’t the problem u...

64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=19.1 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=19.1 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=20.0 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=24.6 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=22.4 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=58 time=24.0 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=58 time=21.1 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=58 time=19.7 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=58 time=24.3 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=58 time=18.5 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=58 time=20.6 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=58 time=22.2 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=58 time=22.1 ms
64 bytes from 1.1.1.1: icmp_seq=14 ttl=58 time=19.0 ms
64 bytes from 1.1.1.1: icmp_seq=15 ttl=58 time=19.4 ms
64 bytes from 1.1.1.1: icmp_seq=16 ttl=58 time=17.7 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=58 time=13.7 ms
64 bytes from 1.1.1.1: icmp_seq=18 ttl=58 time=16.8 ms
64 bytes from 1.1.1.1: icmp_seq=19 ttl=58 time=19.8 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=58 time=19.6 ms

low anchor Feb 25, 2026, 1:27 AM

#

strong cape ```PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=...

It looks good.

strong cape Feb 25, 2026, 1:28 AM

#

Welp. Sounds good to me. Then again I do use a VPN so ofc it could affect the speeds, but so long as it gets a little bit more stable, we good.

compact quartz Feb 25, 2026, 1:28 AM

#

low anchor Try CachyOS.

how good it is?

low anchor Feb 25, 2026, 1:28 AM

#

strong cape Welp. Sounds good to me. Then again I do use a VPN so ofc it could affect the sp...

Run ping 1.1.1.1 and keep it running for 3min.

strong cape Feb 25, 2026, 1:29 AM

#

low anchor Run `ping 1.1.1.1` and keep it running for 3min.

with or without the VPN?

low anchor Feb 25, 2026, 1:30 AM

#

strong cape with or without the VPN?

With and without.

strong cape Feb 25, 2026, 1:30 AM

#

Alr. One moment.

#

📎 message.txt

#

without the VPN....

low anchor Feb 25, 2026, 1:39 AM

#

strong cape

I only need to see the last line before you ctrl+c.

strong cape Feb 25, 2026, 1:40 AM

#

That's the list

#

Oh, you mean the last bit?

low anchor Feb 25, 2026, 1:41 AM

#

strong cape Oh, you mean the last bit?

Yeah.

strong cape Feb 25, 2026, 1:41 AM

#

low anchor Yeah.

Ah okay, one sec...

#

With VPN:

64 bytes from 1.1.1.1: icmp_seq=37 ttl=59 time=37.3 ms
64 bytes from 1.1.1.1: icmp_seq=38 ttl=59 time=33.2 ms
64 bytes from 1.1.1.1: icmp_seq=39 ttl=59 time=35.3 ms
64 bytes from 1.1.1.1: icmp_seq=40 ttl=59 time=38.0 ms
64 bytes from 1.1.1.1: icmp_seq=41 ttl=59 time=34.2 ms
64 bytes from 1.1.1.1: icmp_seq=42 ttl=59 time=34.1 ms
64 bytes from 1.1.1.1: icmp_seq=43 ttl=59 time=37.2 ms
64 bytes from 1.1.1.1: icmp_seq=44 ttl=59 time=40.3 ms
64 bytes from 1.1.1.1: icmp_seq=45 ttl=59 time=34.9 ms
64 bytes from 1.1.1.1: icmp_seq=46 ttl=59 time=34.5 ms
64 bytes from 1.1.1.1: icmp_seq=47 ttl=59 time=40.3 ms
64 bytes from 1.1.1.1: icmp_seq=48 ttl=59 time=38.8 ms
64 bytes from 1.1.1.1: icmp_seq=49 ttl=59 time=35.1 ms
64 bytes from 1.1.1.1: icmp_seq=50 ttl=59 time=36.3 ms
64 bytes from 1.1.1.1: icmp_seq=51 ttl=59 time=38.5 ms
64 bytes from 1.1.1.1: icmp_seq=52 ttl=59 time=35.2 ms
64 bytes from 1.1.1.1: icmp_seq=53 ttl=59 time=38.5 ms
64 bytes from 1.1.1.1: icmp_seq=54 ttl=59 time=32.2 ms
64 bytes from 1.1.1.1: icmp_seq=55 ttl=59 time=37.9 ms
64 bytes from 1.1.1.1: icmp_seq=56 ttl=59 time=65.3 ms
64 bytes from 1.1.1.1: icmp_seq=57 ttl=59 time=40.6 ms
64 bytes from 1.1.1.1: icmp_seq=58 ttl=59 time=31.8 ms
64 bytes from 1.1.1.1: icmp_seq=59 ttl=59 time=36.4 ms
64 bytes from 1.1.1.1: icmp_seq=60 ttl=59 time=37.2 ms
64 bytes from 1.1.1.1: icmp_seq=61 ttl=59 time=41.9 ms
64 bytes from 1.1.1.1: icmp_seq=62 ttl=59 time=35.3 ms
64 bytes from 1.1.1.1: icmp_seq=63 ttl=59 time=36.8 ms
64 bytes from 1.1.1.1: icmp_seq=64 ttl=59 time=36.7 ms
64 bytes from 1.1.1.1: icmp_seq=65 ttl=59 time=38.8 ms
64 bytes from 1.1.1.1: icmp_seq=66 ttl=59 time=38.1 ms
64 bytes from 1.1.1.1: icmp_seq=67 ttl=59 time=32.2 ms
64 bytes from 1.1.1.1: icmp_seq=68 ttl=59 time=57.1 ms
64 bytes from 1.1.1.1: icmp_seq=69 ttl=59 time=32.9 ms
64 bytes from 1.1.1.1: icmp_seq=70 ttl=59 time=36.9 ms
64 bytes from 1.1.1.1: icmp_seq=71 ttl=59 time=56.3 ms```

#

Without VPN:

64 bytes from 1.1.1.1: icmp_seq=185 ttl=58 time=22.4 ms
64 bytes from 1.1.1.1: icmp_seq=186 ttl=58 time=18.4 ms
64 bytes from 1.1.1.1: icmp_seq=187 ttl=58 time=20.5 ms
64 bytes from 1.1.1.1: icmp_seq=188 ttl=58 time=15.3 ms
64 bytes from 1.1.1.1: icmp_seq=189 ttl=58 time=22.4 ms
64 bytes from 1.1.1.1: icmp_seq=190 ttl=58 time=20.8 ms
64 bytes from 1.1.1.1: icmp_seq=191 ttl=58 time=18.3 ms
64 bytes from 1.1.1.1: icmp_seq=192 ttl=58 time=17.4 ms
64 bytes from 1.1.1.1: icmp_seq=193 ttl=58 time=17.3 ms
64 bytes from 1.1.1.1: icmp_seq=194 ttl=58 time=16.9 ms
64 bytes from 1.1.1.1: icmp_seq=195 ttl=58 time=19.0 ms
64 bytes from 1.1.1.1: icmp_seq=196 ttl=58 time=17.9 ms
64 bytes from 1.1.1.1: icmp_seq=197 ttl=58 time=15.2 ms
64 bytes from 1.1.1.1: icmp_seq=198 ttl=58 time=18.9 ms
64 bytes from 1.1.1.1: icmp_seq=199 ttl=58 time=23.9 ms
64 bytes from 1.1.1.1: icmp_seq=200 ttl=58 time=13.9 ms
64 bytes from 1.1.1.1: icmp_seq=201 ttl=58 time=19.2 ms
64 bytes from 1.1.1.1: icmp_seq=202 ttl=58 time=18.3 ms
64 bytes from 1.1.1.1: icmp_seq=203 ttl=58 time=17.0 ms
64 bytes from 1.1.1.1: icmp_seq=204 ttl=58 time=18.8 ms
64 bytes from 1.1.1.1: icmp_seq=205 ttl=58 time=18.8 ms
64 bytes from 1.1.1.1: icmp_seq=206 ttl=58 time=16.6 ms
64 bytes from 1.1.1.1: icmp_seq=207 ttl=58 time=17.0 ms
64 bytes from 1.1.1.1: icmp_seq=208 ttl=58 time=18.1 ms
64 bytes from 1.1.1.1: icmp_seq=209 ttl=58 time=20.0 ms
64 bytes from 1.1.1.1: icmp_seq=210 ttl=58 time=19.4 ms

low anchor Feb 25, 2026, 1:43 AM

#

strong cape Without VPN: ```64 bytes from 1.1.1.1: icmp_seq=184 ttl=58 time=25.5 ms 64 bytes...

I mean the last bit when you stop it.

strong cape Feb 25, 2026, 1:44 AM

#

Oooooooooh

#

I just saw that

#

With VPN:

71 packets transmitted, 70 received, 1.40845% packet loss, time 70124ms
rtt min/avg/max/mdev = 31.811/37.934/65.329/5.308 ms

Without VPN:

210 packets transmitted, 210 received, 0% packet loss, time 209280ms
rtt min/avg/max/mdev = 13.485/18.580/32.649/2.818 ms

low anchor Feb 25, 2026, 1:46 AM

#

strong cape With VPN: ```--- 1.1.1.1 ping statistics --- 71 packets transmitted, 70 received...

Your Ethernet and cable are working perfectly. The instability is coming from the VPN, not the network cable or your PC.

strong cape Feb 25, 2026, 1:46 AM

#

Figured

#

Welp! At least I got it fixed. Earlier it wasn't working at all

low anchor Feb 25, 2026, 1:47 AM

#

strong cape Figured

If you want the VPN to be more stable. Switching to a closer VPN server or change protocol (WireGuard is usually the most stable).

strong cape Feb 25, 2026, 1:48 AM

#

Yeah I got Wireguard port 443 running. Not the closest city though, I may have to try that....

strong cape Feb 25, 2026, 1:51 AM

#

low anchor If you want the VPN to be more stable. Switching to a closer VPN server or chang...

This the closest city with Wireguard Port: 443 enabled:

128 packets transmitted, 128 received, 0% packet loss, time 127164ms
rtt min/avg/max/mdev = 35.553/40.822/58.052/3.601 ms

low anchor Feb 25, 2026, 1:51 AM

#

strong cape This the closest city with Wireguard Port: 443 enabled: ```--- 1.1.1.1 ping sta...

Looks better.

strong cape Feb 25, 2026, 1:52 AM

#

Sweeet

low anchor Feb 25, 2026, 1:55 AM

#

strong cape Sweeet

... solved

stiff loomBOT Feb 25, 2026, 1:55 AM

#

#17680 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: http://0x0.st/8Rt9.png
Thank you

strong cape Feb 25, 2026, 1:58 AM

#

[SOLVED] Issues Connecting to Ethernet

strong cape Feb 25, 2026, 1:58 AM

#

low anchor ... solved

Thanks man!

#[SOLVED] Issues Connecting to Ethernet