please update to a kernel that’s not EOL, for example 6.1.4 LTS or some newer one before any changes are made and make sure that your system is up-to-date.
from the inxi posted:
Kernel: 6.1.38-1-MANJARO
When looking for netstat however, there was an update. I updated.
current uname -a output:
6.1.41-1-MANJARO #1 SMP PREEMPT_DYNAMIC Tue Jul 25 09:17:30 UTC 2023 x86_64 GNU/Linux
my systemtray network now shows 2 loopback connections and the ethernet connection. neither show connected and look identical. i can screenshot if needed but don’t know how to copy text from it.
updated inxi:
[lattrommi@taichi ~]$ inxi -Fazy
System:
Kernel: 6.1.41-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
root=UUID=35f92074-9c31-464e-b7d5-e75abd70ee8d rw splash
resume=UUID=c0e7051a-efdd-4e71-8f6c-e35b57ff86ac
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: X670E Taichi serial: <superuser required>
UEFI: American Megatrends LLC. v: 1.21 date: 04/26/2023
CPU:
Info: model: AMD Ryzen 9 7950X bits: 64 type: MT MCP arch: Zen 4 gen: 5
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601203
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB desc: 16x1024 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3339 high: 4500 min/max: 3000/5880 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3599 2: 3000
3: 3000 4: 3000 5: 3000 6: 3000 7: 2878 8: 3000 9: 2880 10: 3000 11: 3000
12: 4500 13: 3000 14: 4500 15: 4500 16: 3000 17: 3000 18: 3000 19: 4500
20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 25: 3000 26: 4500 27: 4500
28: 3000 29: 3000 30: 3000 31: 3000 32: 4500 bogomips: 288098
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6950 XT] vendor: ASRock driver: amdgpu
v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1
empty: DP-1,DP-2 bus-ID: 03:00.0 chip-ID: 1002:73a5 class-ID: 0300
Device-2: AMD Raphael driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: HDMI-A-2 empty: DP-4,DP-5,DP-6 bus-ID: 59:00.0
chip-ID: 1002:164e class-ID: 0300 temp: 63.0 C
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x2160 s-dpi: 96 s-size: 1182x570mm (46.54x22.44")
s-diag: 1312mm (51.66")
Monitor-1: DP-3 mapped: DisplayPort-2 pos: primary,bottom-l
model: LG (GoldStar) ULTRAWIDE serial: <filter> built: 2022 res: 2560x1080
dpi: 81 gamma: 1.2 size: 800x335mm (31.5x13.19") diag: 867mm (34.1") modes:
max: 2560x1080 min: 640x480
Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: top-center model: Samsung
serial: <filter> built: 2008 res: 1920x1080 hz: 60 dpi: 305 gamma: 1.2
size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-3: HDMI-A-2 mapped: HDMI-A-1-1 pos: bottom-r model: AOC 2060W3
serial: <filter> built: 2015 res: 1920x1080 hz: 60 dpi: 112 gamma: 1.2
size: 435x239mm (17.13x9.41") diag: 496mm (19.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.0.4 renderer: AMD Radeon RX 6950 XT (navi21
LLVM 15.0.7 DRM 3.49 6.1.41-1-MANJARO) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 59:00.1
chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 59:00.6 chip-ID: 1022:15e3
class-ID: 0403
Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-5: Generic USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-8:3
chip-ID: 26ce:0a06 class-ID: 0300
API: ALSA v: k6.1.41-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 0.3.75 status: off with: wireplumber status: active
tools: pw-cli,wpctl
Server-4: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
type: plugin tools: pacat,pactl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz vendor: Rivet Networks
driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 49:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlp73s0 state: down mac: <filter>
Device-2: Realtek Killer E3000 2.5GbE vendor: ASRock driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: a000 bus-ID: 4a:00.0
chip-ID: 10ec:3000 class-ID: 0200
IF: enp74s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-7:6 chip-ID: 8087:0032
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 1.75 TiB used: 345.85 GiB (19.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS1311 240GB SSD
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1122 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD5002ABYS-02B1B0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 3B03 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WDS120G2G0A-00JH30 size: 111.8 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 0000
scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WD1002FBYS-02A6B0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 0C06 scheme: MBR
ID-5: /dev/sde maj-min: 8:64 vendor: A-Data model: USB Flash Drive
size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.0
spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-6: /dev/sdf maj-min: 8:80 vendor: A-Data model: USB Flash Drive
size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.0
spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 102.7 GiB size: 100.53 GiB (97.89%) used: 41.86 GiB (41.6%)
fs: ext4 dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 25.6 MiB (8.6%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdc3 maj-min: 8:35
Sensors:
System Temperatures: cpu: 68.9 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 64.0 C device: amdgpu temp: 55.0 C mem: 58.0 C
fan: 855 watts: 43.00
Info:
Processes: 551 Uptime: 4m wakeups: 0 Memory: total: 128 GiB
available: 124.93 GiB used: 3.31 GiB (2.6%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
Packages: pm: pacman pkgs: 1375 libs: 377 tools: pamac pm: flatpak pkgs: 0
Shell: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.28
can you check if the file /etc/modprobe.d/blacklist.conf exists ?
also check if the dkms package is installed
pacman -Qi dkms
and pls. post the output of ‘ifconfig’ and ‘route’ (or ‘ip link show’)
/etc/modprobe.d/ exists and is empty
[lattrommi@taichi ~]$ pacman -Qi dkms
Name : dkms
Version : 3.0.11-2
Description : Dynamic Kernel Modules System
Architecture : any
URL : https://github.com/dell/dkms
Licenses : GPL2
Groups : None
Provides : None
Depends On : coreutils bash gawk sed kmod gcc make patch
Optional Deps : linux-headers: build modules against the Manjaro kernel
Required By : v4l2loopback-dkms
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 114.43 KiB
Packager : Mark Wagie <mark@manjaro.org>
Build Date : Sat 20 May 2023 12:24:21 PM EDT
Install Date : Mon 10 Jul 2023 03:40:46 AM EDT
Install Reason : Installed as a dependency for another package
Install Script : Yes
Validated By : Signature
ifconfig and route are not found.
[lattrommi@taichi ~]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp74s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 9c:6b:00:00:ac:89 brd ff:ff:ff:ff:ff:ff
3: wlp73s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether be:bf:1a:3d:0c:96 brd ff:ff:ff:ff:ff:ff permaddr a4:6b:b6:2f:be:0d
edit: the issue happened again while trying to post the previous two comments. resetting the NetworkManager worked to get internet working again for now.
the ip link show command above is AFTER i reset and things are working.
[lattrommi@taichi ~]$ sudo iptables -L
[sudo] password for lattrommi:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source
[lattrommi@taichi ~]$ nmcli device show
GENERAL.DEVICE: enp74s0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 9C:6B:00:00:AC:89
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: New 802-3-ethernet connection
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/2
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 107.11.230.54/20
IP4.GATEWAY: 107.11.224.1
IP4.ROUTE[1]: dst = 107.11.224.0/20, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 107.11.224.1, mt = 100
IP4.DNS[1]: 209.18.47.62
IP4.DNS[2]: 209.18.47.63
IP4.DOMAIN[1]: woh.rr.com
IP6.GATEWAY: --
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 100 (connected (externally))
GENERAL.CONNECTION: lo
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: --
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: --
GENERAL.DEVICE: wlp73s0
GENERAL.TYPE: wifi
GENERAL.HWADDR: BE:BF:1A:3D:0C:96
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.GATEWAY: --
IP6.GATEWAY: --
okay, open the graphical package manager, search for “r8168-dkms” and install it.
open the blacklist-conf file and add
blacklist r8169
open a konsole and remove the actual r8169 module.
sudo modprobe -r r8169
and reboot. the new module should be recognized with the reboot. if not, no problem but try this first and report.
i worded my previous comment poorly, the directory /etc/modprobe.d/ exists but the file /etc/modprobe.d/blacklist.conf does not exist.
i searched for “r8168-dkms” (without the quotes) but no package was found.
i searched “r8168” and see what looks like packages for each of the current kernels. i’m guessing the “linux61-r8168” might be what i need to try this.
i also saw in another forum post the command
echo "blacklist r8169" | sudo tee /etc/modprobe.d/r8169.conf
which looks like it would work the same way. i still plan on following the given instructions but if it does work both ways, that might be useful to someone in the future maybe.
a small concern, these packages all have a link on the info page to “www.realtek.com.tw” which is a broken link. looking into it, i think the site is supposed to have .zh-tw for the TLD. perhaps if the people in charge of the build server see this, maybe that could be fixed, if it needs to be.
I installed the r8168, ran the sudo modprobe -r r8169 command and retarted. i was no longer able to connect to the internet. i looked at the settings and saw there is now 3 lo loopbacks in the network widget in the system tray. i did not change any settings for these loopbacks or the ethernet connection.
I tethered my phone internet with USB. it did not work either. i reset the network manager again and it did not work. then i created a new ethernet connection, kept the default settings and my phone tethering was found and that’s what i’m connected with now.
edit: i forgot to mention, the default settings did not work, i disabled ipv6 and then it started working.
ethernet did not work at all after blacklisting r8169 and adding the r8168 mod. .
i undid the changes by removing the blacklist file, removing the linux61_r8168 package and reloading the r8169 with modprobe.
just in case, i untethered and disconnected my phone, deleted all ethernet connections from the networking GUI, then rebooted.
a new ethernet connection was automatically created on startup and seems to be working fine so far. it’s been 3 hours since i rebooted and the problem still has not returned. normally by now it has.
i’m not exactly sure what fixed it and not sure if it will come back or not. i’m still seeing a constant small amount of traffic on the network system tray widget but seeing it while speedtests were running i noticed it’s inaccurate anyways and shows roughly ¼ the speed the speedtests show. i might be misunderstanding some fundamental thing.
i’m not sure if i should mark this as solved because while it is currently not a problem, i’m not sure if blacklisting then unblacklisting a mod was the fix. maybe i simply needed to restart a couple times. maybe it was solar radiation.
thanks to those who offered assistance.
well i was wrong, the issue has returned. it’s less frequent but definitely appears to be the same thing occurring.
i’d love any additional advice to troubleshoot. better yet, a way to reset everyting network related back to when first installed if that’s even possible. maybe a linux desktop home networking guide for people who are more than beginner level but not intermediate level yet? i can dream.
here is my journal. i used
journalctl -b0 -p7
dmesg
inxi using
inxi -Fazy
if anyone happens to see anything off or knows a fix or any tips at all for anything, it’s greatly appreciated. not trying to put a shopping list out for others to take care of for me but I also feel like i’m doing things wrong.
Going through the journal, there seems to be nothing logged before the restarts of NetworkManager, the links stay’s up.
This seems to indicate that the machine with hw adres 00:01:5c:78:42:46 does not respond properly.
For reference on my system ip -r monitor goes through a STALE - > PROBE - > REACHABLE cycle for hosts. iirc this is normal behavior, the ethernet protocol keeps a list on what is connected and refreshes the list periodically.
ip neigh will show the adress of the machine, I guess the gateway 107.11.224.1 in the previous post
Does pinging the gateway or something a bit further away (google.com?) show any drops or high latency in traffic when the network degrades?
Idea:
Using something like portmaster-stub could give some insight into the various applications and traffic they generate. Manjaro has this application in the repository: Portmaster and SPN by Safing.io
1 Like
Thank you for responding first of all.
i’m not sure what machine 00:01:5c:78:42:46 is or how i would go about finding that out. right now it looks like my ethernet is 9c:6b:00:00:ac:89 although i’ve never really looked into these numbers before. something i’ll be researching today.
this portmaster seems helpful, thanks!
these pings of the gateway and google are while internet is working as expected, as a reference point. i’ll edit in ping results if/when it happens.
[lattrommi@taichi ~]$ ping -c 3 107.11.224.1
PING 107.11.224.1 (107.11.224.1) 56(84) bytes of data.
64 bytes from 107.11.224.1: icmp_seq=1 ttl=255 time=6.69 ms
64 bytes from 107.11.224.1: icmp_seq=2 ttl=255 time=8.66 ms
64 bytes from 107.11.224.1: icmp_seq=3 ttl=255 time=15.4 ms
--- 107.11.224.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 6.690/10.255/15.414/3.735 ms
[lattrommi@taichi ~]$ ping -c 3 google.com
PING google.com(ord38s19-in-x0e.1e100.net (2607:f8b0:4009:807::200e)) 56 data bytes
64 bytes from ord08s13-in-x0e.1e100.net (2607:f8b0:4009:807::200e): icmp_seq=1 ttl=115 time=26.0 ms
64 bytes from ord08s13-in-x0e.1e100.net (2607:f8b0:4009:807::200e): icmp_seq=2 ttl=115 time=25.9 ms
64 bytes from ord08s13-in-x0e.1e100.net (2607:f8b0:4009:807::200e): icmp_seq=3 ttl=115 time=26.4 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 25.907/26.087/26.370/0.202 ms
i understand these results at a basic level. interpreting them i do not know how do do, not well. i have a better idea what to search for though. it has been happening less frequently today i’ve noticed.
thanks again for taking the time to look!
EDIT
it happened faster than expected, how convenient.
[lattrommi@taichi ~]$ ping -c 3 107.11.224.1
PING 107.11.224.1 (107.11.224.1) 56(84) bytes of data.
--- 107.11.224.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
[lattrommi@taichi ~]$ ping -c 3 google.com
PING google.com(ord38s30-in-x0e.1e100.net (2607:f8b0:4009:819::200e)) 56 data bytes
64 bytes from ord38s30-in-x0e.1e100.net (2607:f8b0:4009:819::200e): icmp_seq=1 ttl=115 time=25.8 ms
64 bytes from ord38s30-in-x0e.1e100.net (2607:f8b0:4009:819::200e): icmp_seq=2 ttl=115 time=25.3 ms
64 bytes from 2607:f8b0:4009:819::200e: icmp_seq=3 ttl=115 time=25.9 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 16100ms
rtt min/avg/max/mdev = 25.263/25.644/25.881/0.272 ms
i was confused that my gateway timed out but google still went through. i know google can be invasive but that seemed impossible. so i try again.
[lattrommi@taichi ~]$ ping -c 3 107.11.224.1
PING 107.11.224.1 (107.11.224.1) 56(84) bytes of data.
--- 107.11.224.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2031ms
i think: do i have my gateway wrong? i used the gateway listed by the system tray network widget. i try to remember another way to look that up.
[lattrommi@taichi ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp74s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 9c:6b:00:00:ac:89 brd ff:ff:ff:ff:ff:ff
inet 107.11.230.54/20 brd 107.11.239.255 scope global dynamic noprefixroute enp74s0
valid_lft 69143sec preferred_lft 69143sec
inet6 2605:a000:dfc0:6:4c30:b8a:74f8:87cf/128 scope global dynamic noprefixroute
valid_lft 601407sec preferred_lft 601407sec
inet6 fe80::4aa7:45b5:2399:cb60/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp73s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 2e:c4:ea:6d:0e:9e brd ff:ff:ff:ff:ff:ff permaddr a4:6b:b6:2f:be:0d
i don’t think that’s it. does not show numbers matching what i thought my gateway was. i also am not sure if those numbers are supposed to show that. i ping them too in case it matters.
[lattrommi@taichi ~]$ ping -c 3 107.11.230.54
PING 107.11.230.54 (107.11.230.54) 56(84) bytes of data.
64 bytes from 107.11.230.54: icmp_seq=1 ttl=64 time=0.015 ms
64 bytes from 107.11.230.54: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 107.11.230.54: icmp_seq=3 ttl=64 time=0.018 ms
--- 107.11.230.54 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2020ms
rtt min/avg/max/mdev = 0.015/0.019/0.025/0.004 ms
i don’t understand the parts in parenthesis for the above. i feel i might be closer to understanding the issue though.
i check the route.
[lattrommi@taichi ~]$ ip r
default via 107.11.224.1 dev enp74s0 proto dhcp src 107.11.230.54 metric 20100
107.11.224.0/20 dev enp74s0 proto kernel scope link src 107.11.230.54 metric 100
I’m not sure the difference in numbers here. 107.11.224.1 and 107.11.230.54, one maybe is my computer and the other the modem? i see 107.11.224.0/20 too, that took a minute to see.
looking at a lot of numbers are very difficult for me. my brain tries to read them as letters. i have to focus on them and sort of force them to become numbers. if i look away for more then a few seconds, my brain forgets and i have to start over. there might be a duplicate in here.
[lattrommi@taichi ~]$ ping -c 3 107.11.230.54
PING 107.11.230.54 (107.11.230.54) 56(84) bytes of data.
64 bytes from 107.11.230.54: icmp_seq=1 ttl=64 time=0.016 ms
64 bytes from 107.11.230.54: icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from 107.11.230.54: icmp_seq=3 ttl=64 time=0.026 ms
--- 107.11.230.54 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2021ms
rtt min/avg/max/mdev = 0.016/0.023/0.029/0.005 ms
[lattrommi@taichi ~]$ ping -c 3 107.11.230.54
PING 107.11.230.54 (107.11.230.54) 56(84) bytes of data.
64 bytes from 107.11.230.54: icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from 107.11.230.54: icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from 107.11.230.54: icmp_seq=3 ttl=64 time=0.027 ms
--- 107.11.230.54 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2033ms
rtt min/avg/max/mdev = 0.017/0.024/0.029/0.005 ms
[lattrommi@taichi ~]$ ping -c 3 107.11.224.1
PING 107.11.224.1 (107.11.224.1) 56(84) bytes of data.
--- 107.11.224.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2027ms
[lattrommi@taichi ~]$ ping -c 3 107.11.224.0/20
ping: 107.11.224.0/20: Name or service not known
[lattrommi@taichi ~]$ ping -c 3 107.11.224.0
PING 107.11.224.0 (107.11.224.0) 56(84) bytes of data.
From 107.11.230.54 icmp_seq=1 Destination Host Unreachable
From 107.11.230.54 icmp_seq=2 Destination Host Unreachable
From 107.11.230.54 icmp_seq=3 Destination Host Unreachable
--- 107.11.224.0 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2019ms
pipe 3
i’m unsure how to proceed.
1 Like
Ping uses the ICMP protocol and is used for diagnostics. The important field in this case is time=xxx & status messages
example
$ ping google.com
PING google.com (142.250.179.142) 56(84) bytes of data.
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=1 ttl=119 time=5.21 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=2 ttl=119 time=5.30 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=3 ttl=119 time=5.30 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=4 ttl=119 time=5.29 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=5 ttl=119 time=5.20 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=6 ttl=119 time=5.34 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=7 ttl=119 time=5.40 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=8 ttl=119 time=5.23 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=9 ttl=119 time=5.16 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=10 ttl=119 time=5.19 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=11 ttl=119 time=5.31 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=12 ttl=119 time=5.38 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=13 ttl=119 time=5.47 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=14 ttl=119 time=5.33 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=15 ttl=119 time=5.27 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=16 ttl=119 time=5.30 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=17 ttl=119 time=5.29 ms
^C
--- google.com ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16023ms
rtt min/avg/max/mdev = 5.164/5.292/5.468/0.076 ms
If packets are lost, malformed or take a long time this could indicate congestion or some other problem. Let the ping run in a window to the gateway & google and check the values when the degradation occurs.
portmaster ultimately was what i needed I think. Before it finished setting up it sent a notification:
Portmaster has detected that websites may load slower because DNS queries are currently slower than expected. You may want to switch your DNS provider or enable using expired DNS cache entries for better performance.
I’ve never changed DNS provider before but that with other things I’ve read both here and online lead me to believe the modem change might have changed my DNS. I’m not sure but at least I have a better idea.
This Portmaster application seems really great and is quickly answering questions I’ve had for awhile that I didn’t know how to ask. Something I needed, so thank you for that suggestion especially.
1 Like
Modems (or rather, usually Routers) have the ability to set DNS.
And, if you have never actively set your DNS on your computer system … thats likely the DNS it is using.
I generally encourage people to set it to something other than whatever the ISP provides.
For speed and security reasons.
There are a number of factors when deciding what DNS to use, and a number of ways to implement that decision.
For now I will assume you can and will use your router to do this …
but if you are interested I wrote a quick setup of how I use systemd-resolved here:
After laptop resumes from Standby I lose DNS - #2 by cscs
Anyways moving on … heres a little script to test and rank some popular DNS providers:
(Edit - added in link to dedicated thread)
Old pasted script
#!/usr/bin/env bash
#
# dns speed test
#
if [[ -z "$DOMAIN" ]]; then
DOMAIN=wikipedia.org
fi;
CURRENTDNS=$(dig "$DOMAIN" | grep SERVER | awk -F'[)(]' '{print $2}')
if [[ -z "$SKIP" ]]; then
echo
echo " Test common resolvers by calculating average response times of 3 queries."
echo
annc() {
echo
echo " DNS Primary Secondary"
echo
echo " Adguard 94.140.14.14 94.140.15.15"
echo " CleanBrowsing 185.228.168.9 185.228.169.9"
echo " Comodo 8.26.56.26 8.20.247.20"
echo " Control-D 76.76.2.2 76.76.10.2"
echo " Cloudflare 1.1.1.1 1.0.0.1"
echo " Google 8.8.8.8 8.8.4.4"
echo " Neustar 156.154.70.2 156.154.71.2"
echo " NextDNS 45.90.28.97 45.90.30.97"
echo " OpenDNS 208.67.222.222 208.67.220.220"
echo " Quad9 9.9.9.9 149.112.112.112"
echo
}
printf '%*s\n' "${COLUMNS:-$(tput cols)}" '' | tr ' ' -
annc | column -tL
fi;
if [[ -n "$TESTDNS" ]]; then
echo "Custom Test DNS $TESTDNS"
fi
printf '%*s\n' "${COLUMNS:-$(tput cols)}" '' | tr ' ' -
echo
while true; do
read -p " Do you wish to flush the DNS cache? " yn
case $yn in
[Yy]* ) resolvectl flush-caches; break ;;
[Nn]* ) break ;;
* ) echo -e "\n Please answer yes or no.\n" ;;
esac
done
echo
echo "Current DNS $CURRENTDNS"
for reps in {1..3}
do
dig "$DOMAIN" | awk '/time/ {print $4 " ms"}'
sleep 1
done | awk '/ms/ {sum+=$1} END {print "Avg time: ",sum/3, " ms"}'
echo
if [[ -z "$SKIP" ]]; then
rank() {
for resolver in "Adguard 94.140.14.14" "CleanBrowsing 185.228.168.9" "Comodo 8.26.56.26" "Control-D 76.76.2.2" "Cloudflare 1.1.1.1" "Google 8.8.8.8" "Neustar 156.154.70.2" "NextDNS 45.90.28.97" "OpenDNS 208.67.222.222" "Quad9 9.9.9.9";
do
echo "$resolver"
for reps in {1..3}
do
dig "$DOMAIN" "@${resolver#* }" | awk '/time/ {print $4 " ms"}'
sleep 1
done | awk '/ms/ {sum+=$1} END {print "Avg time: ",sum/3, " ms"}'
echo
done
}
rank;
fi;
if [[ -n "$TESTDNS" ]]; then
echo "Custom Test DNS $TESTDNS"
for reps in {1..3}
do
dig "$DOMAIN" "@$TESTDNS" | awk '/time/ {print $4 " ms"}'
sleep 1
done | awk '/ms/ {sum+=$1} END {print "Avg time: ",sum/3, " ms"}'
echo
fi
exit
(save, mark executable, run … it will give you an average response time for each)
Note: It uses dig which is provided by the package bind.
2 Likes
The from field lists the source, in this case your computer, it has rapid response times because it is local.
The first line tells us that the default route to the rest of the network (eg internet) is 107.11.224.1 and that is is the first one to try. The second line lists the network your machine is in. It is the way the machine can tell what is local to it and what it needs to be sent to the gateway. The /20 on the end means that there is a maximum of 4096 hosts that can exist in that network.
Your experience pinging the gateway and it responding on one moment en then won’t respond at all is valuable data. Since the ping to google seems to always work this could be a indicator that the gateway/infrastructure of the ISP has some difficulty responding to the requests.
[lattrommi@taichi ~]$ ping -c 3 107.11.224.0/20
ping: 107.11.224.0/20: Name or service not known
This fails because ping command expects a specific address and the value is a network.
This is the correct response of the command used and not relevant.
[lattrommi@taichi ~]$ ping -c 3 107.11.224.0
PING 107.11.224.0 (107.11.224.0) 56(84) bytes of data.
From 107.11.230.54 icmp_seq=1 Destination Host Unreachable
This fails because the host is not valid, eg your computer cannot reach it, this is the correct response and not relevant in this case.
Changing the DNS server is a valid option. Since the ISP assigns a default value through DHCP & sets their own DNS servers as the default and your experience (portmaster hinting at this to) is not stellar there are a few way’s to check / change / test.
In Firefox there is a option to use DNS over HTTPS. Using this option is easy to turn on, accept the default, restart browser and test. The rollback is easy to, just change the option.
In the KDE network settings for the connection there is a option to set the DNS resolver yourself instead of accepting the default one your ISP assigns. If inputting numbers is hard this can be the more difficult option to get right and to fix if this does not work. Using the script above will give insight into what is possible for replacements DNS servers.
1 Like
thanks to both of you for all the information, I appreciate it more than I can say!
things have not worked out well for me unfortunately. i have nor had decently working internet on the computer since I last commented.
I tried changing my DNS but could not seem to get rid of the ISP DNS. any changes I made would not take effect on rebooting or any other way.
I factory reset the modem and still nothing.
I’m not using a router right now and was not able to do anything with the modem beyond power cycling and the factory reset. I tried reconnecting my obselete router but couldn’t login into it, I think it might have stopped working too.
I was able to USB tether my phone for internet, which helped me research more easily for awhile. the phone service company, Verizon, uses throttling deprioritization for lower class customers after their data caps are met, which drops the speed of the connection to 600kbps (they say, much lower in reality) and is just as useless as the internet in my initial problem. I found other articles likely related. I may add them if I can before the post gets auto-closed. not easy to share from PC to phone, not with my circumstances and this budget phone at least.
I did re-learn that the Realtek Ethernet device is buggy, as was mentioned. (I can’t see who said it while replying on my phone) and looking into it more, I found a 2 year old Reddit thread with people having the same problems, with the same equipment, in a windows environment and it was still getting comments as of last week. my current working theory is that the ethernet NIC is junk and i need to return my motherboard.
oddly enough I was able to log on to with windows again, something I haven’t been able to do inover a month. I read that occasionally, logging into windows and updating the driver there is sometimes a fix but not in my case. despite the specs of my PC, windows was slow and too painful to to use for anything, even moreso than it usually is. it took a minute and a half to open the task manager with ctrl+shift+escape because of all the background stuff happening for updates and telemetry or whatever.
i blacklisted r8169 and installed r8168 again, undid that, tried the reverse, undid that. wandered around the systemd labyrinth pointlessly to see if anything looked wrong, tried reinstalling all network related things I could, created a new user and tested with that, took an SSD from another (older) system with manjaro on it and ran it in CSM mode and still no connection nothing.
I’ve messed with so many settings at this point, I doubt anything can be fixed because of some setting I’d changed and forgot to revert.
I’m going to try one more thing and see if I can connect from from a live USB. if that doesn’t help I’ll reinstall manjaro. next option is to RMA the board.
thanks again for taking a look and all the tips and suggestions!
This has been resolved. The modem provided by my ISP had an internal battery, not accessible to the end user in a simple way, was steadily failing. It was replaced a little over 24 hours ago and since then I have had no issues. If you are reading this and having similar problems, remember: don’t trust your ISP.
Those who offered support, I have learned a lot from you and feel I now have better direction towards learning more. I cannot thank you enough.
3 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.