

This is rather wild guess, but something spamming your network might cause the symptoms you're describing.leyvi wrote: Tue Jun 02, 2026 8:04 pmEDIT I
By "strange behaviour" I mean everything is slow, battery-life is in the gutter, everything runs hot, network latency is high, and once I ran a traceroute that went to my ISP, then to some address registered to a European company according to whois (nondescript, couldn't find them online), then back to my ISP, then off to it's original destination. I (technically) live in Asia.
Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001
Packets going in a loop sounds implausible to me, given how many networks I use but don't control. A rouge/misconfigured program seems more likely. But how would I figure out which one? I can use packet capture tools, but I'm a lot more interested in statistics than individual packets; what tools do I use for that?Zucca wrote: Wed Jun 03, 2026 11:31 amThe something might be, for example:So, does this happen if you take some of your devices out of the network? if the symptons disappear, then I'd start to investigate your network internally for misconfigured program.
- packets going in a loop
- some rogue program spamming your local network

Finding the common denominator is getting complicated.leyvi wrote: Thu Jun 04, 2026 12:01 am What's weird is that this happens on my home network, my school network, and on my cellular network/hotspot. Maybe I've misconfigured some network-related setting on my devices. But it would have to be all of my devices. And one of them is running GrapheneOS, which has very limited network configurability, yet it has these problems even when it's kilometers away from my other devices. My laptop has these problems away from home, even when my phone is in my dormitory. And my desktop has these problems even when I access it remotely.

OK, gonna try NetHogs.NathanZachary wrote: Thu Jun 04, 2026 1:32 am You're right that it's quite peculiar to happen across both multiple devices and multiple networks (some of which are not under your direct control). You'll probably want to start with the basic network analyser tools like Wireshark. I can also recommend NetHogs (which is available in Gentoo) for another approach. Starting with a generalised packet capture and then delving into more specific findings based on that initial capture is my typical method of starting to troubleshoot network congestion or even rogue applications consuming substantial bandwidth.
Not yet. I aim to try running NetHogs, see what happens.Banana wrote: Thu Jun 04, 2026 6:14 amFinding the common denominator is getting complicated.leyvi wrote: Thu Jun 04, 2026 12:01 am What's weird is that this happens on my home network, my school network, and on my cellular network/hotspot. Maybe I've misconfigured some network-related setting on my devices. But it would have to be all of my devices. And one of them is running GrapheneOS, which has very limited network configurability, yet it has these problems even when it's kilometers away from my other devices. My laptop has these problems away from home, even when my phone is in my dormitory. And my desktop has these problems even when I access it remotely.
Do you have any "solid" errors or findings what is wrong? Looking for solution based on feelings is like looking for the needle in a haystack.
Good to know.NeddySeagoon wrote: Thu Jun 04, 2026 8:48 am leyvi,
For your battery devices, it may be worth calibrating the battery management system.
There two sources of acumulating error.
1. battery capacity falls with each charge/discarge cycle.
2. The state of charge is done by measuring charge in/and charge out. It's a dead reconning system.
Discharge the battery as far as you can.
Now charge it in one go.
Provided the discharge was far enough, you will get a new number for total capacity. That's actual, not as manufactured and the state of charge system will be recalibrated too.
If the actual capacity is less than half the manufactured capacity, the battery is end of life.
Replace it with a good quality battery from a trustworthy source. You really don't want a Lithium fire.
Can you elaborate?leyvi wrote: Fri Jun 05, 2026 10:00 amand running a ClamAV scan made my system reboot suddenly, a "data fabric flood event" that happens on my desktop sometimes.
Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001
you may be able to read battery info in /sys depending on the battery. It would have to track and expose that info (generally the devices internal BMS tracks that)leyvi wrote: Fri Jun 05, 2026 10:04 amGood to know.NeddySeagoon wrote: Thu Jun 04, 2026 8:48 am leyvi,
For your battery devices, it may be worth calibrating the battery management system.
There two sources of acumulating error.
1. battery capacity falls with each charge/discarge cycle.
2. The state of charge is done by measuring charge in/and charge out. It's a dead reconning system.
Discharge the battery as far as you can.
Now charge it in one go.
Provided the discharge was far enough, you will get a new number for total capacity. That's actual, not as manufactured and the state of charge system will be recalibrated too.
If the actual capacity is less than half the manufactured capacity, the battery is end of life.
Replace it with a good quality battery from a trustworthy source. You really don't want a Lithium fire.
I regularly run my phone down to 2% battery. The battery checker says that it's done about 350 discharge cycles over the last year and a half.
I haven't run my laptop down below 50% before, it's only a few months old. For drive health we have SMART and it's userspace tools. But what about battery health?

Nobody would fault you for considering malicious activity; it's good to be security-aware. If you need any assistance with kernel parameters, please feel free to ask.leyvi wrote: Fri Jun 05, 2026 4:00 pm It is in fact a hardware problem. There are some kernel parameters that can be used to fix it. I just only started having this problem with my laptop after using it a few months (it's only happened once though, whereas on my desktop it happens all the time). I wasn't expecting this to happen at all though.
It isn't completely illogical to speculate that it could be exploited by a hacker wishing to remain undiscovered though.