Wifi stops working untill disconnected

Support Network
1

Whenever I am downloading big files through browser or torrent client, my wifi will stop working showing question mark(no internet) and works again after disconnecting and connecting only to have same issue again within 10 minutes.
I have gone through at least hundred posts and creating these files really helped.

.
/etc/modprobe.d/iwlwifi.conf
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

After these files issues does not happen as usual but still occurs. Also, my wifi stops woking when I leave my system ideals for few minutes, same does when I am using my system but issue is guaranteed to occur with ideal system.

I had also turned off auto suspend,sleep in setting. I think it is related to wifi powersave and above 2 tips reallt helped.

1 Like
2

You might find better performance and stability using a direct cable connection to your router, if that is an option.

Especially when using Torrent applications.

1 Like
3

Try also disabling Mac randomization.

https://wiki.archlinux.org/title/NetworkManager#Configuring_MAC_address_randomization

1 Like
4 
printf 'options iwlmvm power_scheme=1' | sudo tee /etc/modprobe.d/iwlmvm.conf

https://wiki.archlinux.org/title/Network_configuration/Wireless#Cause_#6

But thats just a guess because you didnt provide us with anything like the devices involved.

Generally for troubleshooting basic system information is a good start;

inxi -Farz
1 Like
5

Well, I did not knew commands to provide details about hardware, thanks for letting me know.
I will try both the recommendations and report about same.
Output of command is

Blockquote
System:
Kernel: 6.9.12-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.9-x86_64
root=UUID=524f46a8-24bd-4ffd-92af-f8768bba4016 rw quiet splash apparmor=1
security=apparmor udev.log_priority=3
Desktop: GNOME v: 46.4 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 46.2 Distro: Manjaro
base: Arch Linux
Machine:
Type: Laptop System: HP product: HP Laptop 15q-ds0xxx
v: Type1ProductConfigId serial: Chassis: type: 10
serial:
Mobo: HP model: 84A6 v: 80.50 serial:
part-nu: 6AF82PA#ACJ uuid: UEFI: Insyde v: F.48
date: 04/26/2024
Battery:
ID-1: BAT1 charge: 13.3 Wh (100.0%) condition: 13.3/41.9 Wh (31.7%)
volts: 12.8 min: 11.6 model: Hewlett-Packard PABAS0241231 type: Li-ion
serial: status: full
CPU:
Info: model: Intel Core i3-7020U bits: 64 type: MT MCP arch: Amber/Kaby Lake
note: check gen: core 7 level: v3 note: check built: 2017
process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 9
microcode: 0xF6
Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 400 min/max: 400/2300 scaling: driver: intel_pstate
governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 bogomips: 18406
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow 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: IBRS; IBPB: conditional; STIBP: conditional;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:5916 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP TrueVision HD Camera
driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
bus-ID: 1-5:4 chip-ID: 05c8:03d2 class-ID: 0e02
Display: wayland server: v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: gnome-shell driver: gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x0671 built: 2016 res: 1366x768
dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
ratio: 16:9 modes: 1366x768
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.1.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
device-ID: 8086:5916 memory: 3.74 GiB unified: yes display-ID: :0.0
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_soc_avs
bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
API: ALSA v: k6.9.12-3-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac:
Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter
vendor: Hewlett-Packard driver: rtw_8723de v: N/A modules: rtw88_8723de
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:d723 class-ID: 0280
IF: wlo1 state: up mac:
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:5 chip-ID: 0bda:b009
class-ID: e001 serial:
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 5060 bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
Local Storage: total: 988.82 GiB used: 85.42 GiB (8.6%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ04ABF100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: fw-rev: 4C scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: Ultra size: 57.3 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: fw-rev: 1.00 scheme: MBR
Partition:
ID-1: / raw-size: 259.32 GiB size: 254.19 GiB (98.02%)
used: 44.48 GiB (17.5%) fs: ext4 dev: /dev/sda3 maj-min: 8:3
ID-2: /boot/efi raw-size: 301 MiB size: 300.4 MiB (99.79%)
used: 296 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 54.0 C pch: 53.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1229 libs: 340 tools: gnome-software,pamac
pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
Info:
Memory: total: 8 GiB available: 7.66 GiB used: 1.98 GiB (25.8%)
Processes: 249 Power: uptime: 4m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.05 GiB services: gsd-power,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Compilers: N/A Shell: Zsh v: 5.9 running-in: gnome-terminal inxi: 3.3.36

I have tried many linux distro ,so far my wifi works perfectly without any modifications in void linux only and window. I could use void linux but its little difficult for me and its support for troubleshooting isn’t as robust as arch.

6

This is the network devices

This is the wireless we are talking about.

Hm. I wonder what module is in use there.
You could check and report back with the output of something like inxi -Naz.

I also see rtl8723de-dkms-git in the AUR … but it hasnt had any movement in 4 years, aside from the attached github page being archived.

7

Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter
vendor: Hewlett-Packard driver: rtw_8723de v: N/A modules: rtw88_8723de
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:d723 class-ID: 0280

Same modules,I wonder what could be making difference, download speed is also constant in void and not fluctuating like in other distros after applying above powersave .conf

8

It’s also possible the WiFi card is getting a little too warm and going out-of-spec when doing such sustained transfers; I’ve been having something like these symptoms happening with mine.

In my case it seems to be stable with the latest LTS Kernel (linux66 series) and linux61, but I have had to resort to a hibernate and resume cycle to get it back online again on a regular basis until recently; prior to a few months back, a full reboot was required, so it might still be driver related.

If you are not hammering it, does it still drop the connection (assuming powersave, standby etc. is turned off)?

… Also:

Potential interference? Is your router set to the same channel as nearby routers, or on a strong overlapping one? If so: Change it! I suggest linssid for checking this. Plenty of routers in my experience seem to select a busy channel when set to auto-configure.

And probably the best solution:

:100: — especially if things like torrents are involved.

9

I had a similar problem. I started using a python 3 script I found on Github called

stabilizer.py

It stabilizes internet connections.

Note: I commented out the lines that make it run only as root. I can now run it in my autostart as a user. I has really helped my connection.

Just run /usr/bin/python 3 stabilizer.py (You may need to add appropriate directories.

10

… but … what does it do ?

… and what project are you referring to ?

Searching around I found this one:

But I dont really suggest it … it pings google constantly, and if it fails to do so, then restarts NetworkManager service (yes using sudo, and ubuntu aliases). Thats it. Oh and it uses slow python for some reason. It stabilizes nothing really. The name is a misnomer. It would be better titled ‘inefficient_restarter.py’.

2 Likes
11

You might also try raising your connection priority. The default is 0. Try 1 or 2 if you feel like testing that.

12

I could have done with something similar to this back in the days of dial-up, to re-dial when the connection dropped, because the software I had at the time often didn’t. But now? :3rd_place_medal:

What I’d suggest is getting a WiFi dongle and seeing if that performs any better in terms of maintaining connectivity.

13

You don’t have to use the script. Ping is pretty useful all by itself.

You could just do a ping to your router to test it. Try a

ping -l 3 198.168.1.1

See if your router accepts that ping. Make sure discovery is on.
Hit ctr z to temporarily stop it, then type bg to send it to the background and run that way.

Use journalctl -f to monitor when your router goes offline.

14

Usually the IP range starts with 192. Also some are set to xxx.xxx.0.x rather than 1 (not as common though).

15

I’m guessing the 198 was a typo.

In fact, the IP used will depend on whatever the router manufacturer allows by default. See the following list as an example; albeit a few years old by now:

Typical router IP Addresses...
Manufacturer Default IP Address
2Wire 192.168.1.1, 192.168.0.1,192.168.1.254, 10.0.0.138
3Com 192.168.1.1, 192.168.1.10.1
Actiontec 192.168.0.1, 192.168.1.1, 192.168.2.1, 192.168.254.254
Airlink 192.168.1.1, 192.168.2.1, 192.168.1.250
Airlive 192.168.2.1, 192.168.1.254
Airties 192.168.2.1
Apple 10.0.1.1
Amped Wireless 192.168.3.1
Asus 192.168.1.1, 192.168.2.1, 10.10.1.1, 10.0.0.1
Aztech 192.168.1.1, 192.168.2.1, 192.168.1.254, 192.168.254.254
Belkin 192.168.1.1, 192.168.2.1, 10.0.0.2, 10.1.1.1
Billion 192.168.1.254, 10.0.0.2
Buffalo 192.168.1.1, 192.168.11.1
Card King 192.168.0.1
Cisco 192.168.1.1, 192.168.0.30, 192.168.0.50, 10.0.0.1, 10.0.0.2
Dell 192.168.1.1
D-Link 192.168.1.1, 192.168.0.1, 192.168.0.10, 192.168.0.101, 192.168.0.30, 192.168.0.50, 192.168.1.254, 192.168.15.1, 192.168.254.254, 10.0.0.1, 10.0.0.2, 10.1.1.1, 10.90.90.90
Edimax 192.168.2.1
Eero 192.168.0.1
Eminent 192.168.1.1, 192.168.0.1, 192.168.8.1
Gigabyte 192.168.1.254
Google 192.168.86.0, 192.168.86.1, 192.168.0.1
Hawking 192.168.1.200, 192.168.1.254
Huawei 192.168.1.1, 192.168.0.1, 192.168.3.1, 192.168.8.1, 192.168.100.1, 10.0.0.138
LevelOne 192.168.0.1, 192.168.123.254
Linksys 192.168.1.1, 192.168.0.1, 192.168.1.10, 192.168.1.210, 192.168.1.254, 192.168.1.99, 192.168.15.1, 192.168.16.1, 192.168.2.1
Microsoft 192.168.2.1
Motorola 192.168.0.1, 192.168.10.1, 192.168.15.1, 192.168.20.1, 192.168.30.1, 192.168.62.1, 192.168.100.1, 192.168.102.1, 192.168.1.254
MSI 192.168.1.254
Netgear 192.168.1.1, 192.168.0.1, 192.168.0.227
NetComm 192.168.1.1, 192.168.10.50, 192.168.20.1, 10.0.0.138
Netopia 192.168.0.1, 192.168.1.254
Planet 192.168.1.1, 192.168.0.1, 192.168.1.254
Repotec 192.168.1.1, 192.168.10.1, 192.168.16.1, 192.168.123.254
Senao 192.168.0.1
Siemens 192.168.1.1, 192.168.0.1, 192.168.1.254, 192.168.2.1, 192.168.254.254, 10.0.0.138, 10.0.0.2
Sitecom 192.168.0.1, 192.168.1.254, 192.168.123.254, 10.0.0.1
SMC Networks 192.168.1.1, 192.168.0.1, 192.168.2.1, 10.0.0.1, 10.1.10.1
Sonicwall 192.168.1.254, 192.168.0.3, 192.168.168.168
SpeedTouch 10.0.0.138, 192.168.1.254
Synology 192.168.1.1
Sweex 192.168.32.1, 192.168.15.1, 192.168.50.1, 192.168.55.1, 192.168.251.1
Tenda 192.168.1.1, 192.168.0.1
Thomson 192.168.0.1, 192.168.1.254, 192.168.100.1
TP-Link 192.168.1.1, 192.168.0.1, 192.168.0.254
Trendnet 192.168.1.1, 192.168.0.1, 192.168.0.30, 192.168.0.100, 192.168.1.100, 192.168.1.254, 192.168.10.1, 192.168.10.10, 192.168.10.100, 192.168.2.1, 192.168.223.100, 200.200.200.5
Ubiquiti 192.168.1.1, 192.168.1.20
U.S. Robotics 192.168.1.1, 192.168.2.1, 192.168.123.254
Zoom 192.168.1.1, 192.168.2.1, 192.168.4.1, 192.168.10.1, 192.168.1.254, 10.0.0.2, 10.0.0.138
ZTE 192.168.1.1, 192.168.0.1, 192.168.100.100, 192.168.1.254, 192.168.2.1, 192.168.2.254
Zyxel 192.168.1.1, 192.168.0.1, 192.168.2.1, 192.168.4.1, 192.168.10.1, 192.168.1.254, 192.168.254.254, 10.0.0.2, 10.0.0.138

Of course, it’s much easier to ask your system:

ip r | grep default

…or…

ip route
1 Like
16

Forehead smack. The typo king strikes again. Thanks for catching that. :slight_smile:

1 Like
17

I’ve traditionally done ip addr show | grep 192 which it seems from your list, will work for pretty much everything except Crapple™ (and maybe Speedtouch, if it is using the first address).

1 Like
18

On a similar note, if you are a kcmshell6 fan, there are a number of network related arguments you can use with it. For example,

kcmshell6 kcm_nic

gives similar information plus local loopback info.

1 Like
19

The 10.x.x.x addresses are not that uncommon either.
Also … those are just the defaults. People dont have to keep them those.
But many do - making certain ‘jobs’ easier depending on your vocational inclination…

Anyhoo a better command would be

ip route

Which it seems soundofthunder mentioned already.
If you must isolate it then maybe something like

ip route get 1 | head -1 | awk '{print $3}'

But I dont think the OP ever needed a way to ping the router.

We still dont know what the issue is or even how it manifests for sure really.

If anything, given the description, it would appear that the wireless card continues ‘working’ but that it cannot access the public internet.

(emphasis added by me)

All of this other stuff was in relation to a random script that would not even function as currently written.

1 Like
20

The list is a guide, at best; but, even from that we can deduce that some manufacturers allow several ip addresses for the purpose.

Using grep 192 will only be useful if the ip address in question was actually set. Though, I suppose one could argue it would be conspicuous by it’s absence.

In a Mac, I’d use something like netstat -nt | grep default.

Now, back on topic.

@Piku

Are you using any kind of VPN or similar while using the torrent client? If so, that’s generally not recommended, and I know of some who have experienced similar interruptions using a wired network.

Using Wifi would only compound the issue, I imagine; particularly if it’s not a stable connection to begin with. Environmental issues could certainly come into play.

2 Likes