The last few days have been strange. Some days the network/wifi is about as unreliable as before while others it’s almost never getting disabled. FWIW - I shut down every night, so the reboot bits shouldn’t be a factor.
I tried disabling Bluetooth via the toggle on the UI to no effect. Is that enough to properly test this or does it need to be from the BIOS or somewhere else?
I don’t have much time to post details right now, but wanted to get an update with what I’m able.
If you’d read the instructions on the link I posted, you should already know that a Udev rule is the method you want to use. The link has the command you want to use, you simply need to substitute in your hardware ID’s (which I gave you).)
Looks like I was able to successfully shut off my bluetooth following your instructions - including a reboot. Watching my network via wavemon, I saw it ‘disconnect’ again.
You can implement my earlier suggestions using Network Manager. You do not have to make the changes through your router. Although, using your router settings utility to do this is generally a bit simpler.
Rather than through your router, you can set a static IP address using Network Manager. A search should provide you with enough information on how to set up a static IP address using Network Manager.
To force Network Manager to use only the 2.4 GHz band, install nm-connection-editor (if not already installed). To open the newly installed program run nm-connection-editor in a terminal. Double-click your Wi-Fi network name. Go to your Wi-Fi tab, then set the Band drop down field to B/G (2.4 GHz). Save the new settings and reconnect.
Please post:
cat /etc/udev/rules.d/81-bluetooth-hci.rules
Just flipped the band to B/G like you said. We’ll see if that helps.
In the meantime, here’s that file’s contents (cat <file>):
# turning off bluetooth
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="8922", ATTR{authorized}="0"
I’m going to delete that file since it didn’t help. I can bring it back if I messed up it’s contents.
I’ll report back if the wifi band doesn’t fix it or in a few days if it worked. I’m assuming I don’t need to reboot for it to take effect.
You don’t need to reboot if you’re changing Network managers config, but you should at least restart network manager. It would also be a good idea to reboot your router.
The udev rule looks fine, but it’s best to always check.
I noticed I still had my wifi shut off, so I rebooted after deleting the “bluetooth off” rule file.
Things look promising now, but I’ll post again here if I notice it drop.
Just wanted to give a quick update since it’s been a few days. I haven’t noticed my wifi drop since my last update. I was using wavemon to keep an eye on things more directly and saw none of the problems I’ve been facing. Earlier today I decided it might work better if I let journalctl -fu NetworkManager run in the background in case I was just missing when/if it dropped. I let it run for a couple of ours and only had one spurt of output. It just looks like normal activity to me, but I’m not well versed in these network logs. I’m pasting it below in case there’s something I’m missing. Also, the line-break was from me after the initial output to delineate the sections of output.
> journalctl -fu NetworkManager
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.6711] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.6983] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247, acd pending
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8415] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8419] policy: set 'tell your wifi said hello' (wlp7s0) as default for IPv4 routing and DNS
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8441] device (wlp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8645] device (wlp7s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8647] device (wlp7s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8649] manager: NetworkManager state is now CONNECTED_SITE
Feb 09 09:38:20 davids-rig NetworkManager[1132]: <info> [1770651500.8652] device (wlp7s0): Activation: successful, device activated.
Feb 09 09:38:21 davids-rig NetworkManager[1132]: <info> [1770651501.2065] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.5254] device (wlp7s0): ip:dhcp4: restarting
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.5255] dhcp4 (wlp7s0): canceled DHCP transaction
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.5255] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.5255] dhcp4 (wlp7s0): state changed no lease
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.5256] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.7779] device (wlp7s0): supplicant interface state: completed -> disconnected
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.7779] device (p2p-dev-wlp7s0): supplicant management interface state: completed -> disconnected
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.9464] device (wlp7s0): supplicant interface state: disconnected -> scanning
Feb 09 15:39:37 davids-rig NetworkManager[1132]: <info> [1770673177.9464] device (p2p-dev-wlp7s0): supplicant management interface state: disconnected -> scanning
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.3565] device (wlp7s0): supplicant interface state: scanning -> authenticating
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.3565] device (p2p-dev-wlp7s0): supplicant management interface state: scanning -> authenticating
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.3694] device (wlp7s0): supplicant interface state: authenticating -> associating
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.3695] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.4920] device (wlp7s0): supplicant interface state: associating -> 4way_handshake
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.4920] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> 4way_handshake
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5307] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5307] device (wlp7s0): ip:dhcp4: restarting
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5494] dhcp4 (wlp7s0): canceled DHCP transaction
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5494] dhcp4 (wlp7s0): state changed no lease
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5495] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.5495] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.6237] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247, acd pending
Feb 09 15:39:38 davids-rig NetworkManager[1132]: <info> [1770673178.6238] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247
Feb 09 15:44:50 davids-rig NetworkManager[1132]: <info> [1770673490.7488] device (wlp7s0): ip:dhcp4: restarting
Feb 09 15:44:50 davids-rig NetworkManager[1132]: <info> [1770673490.7489] dhcp4 (wlp7s0): canceled DHCP transaction
Feb 09 15:44:50 davids-rig NetworkManager[1132]: <info> [1770673490.7489] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:44:50 davids-rig NetworkManager[1132]: <info> [1770673490.7489] dhcp4 (wlp7s0): state changed no lease
Feb 09 15:44:50 davids-rig NetworkManager[1132]: <info> [1770673490.7489] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.2578] device (wlp7s0): supplicant interface state: completed -> authenticating
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.2579] device (p2p-dev-wlp7s0): supplicant management interface state: completed -> authenticating
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.2699] device (wlp7s0): supplicant interface state: authenticating -> associating
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.2699] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3253] device (wlp7s0): ip:dhcp4: restarting
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3345] dhcp4 (wlp7s0): canceled DHCP transaction
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3345] dhcp4 (wlp7s0): state changed no lease
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3345] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3959] device (wlp7s0): supplicant interface state: associating -> 4way_handshake
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.3960] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> 4way_handshake
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4429] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4430] device (wlp7s0): ip:dhcp4: restarting
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4524] dhcp4 (wlp7s0): canceled DHCP transaction
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4525] dhcp4 (wlp7s0): state changed no lease
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4525] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4525] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4989] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247, acd pending
Feb 09 15:44:51 davids-rig NetworkManager[1132]: <info> [1770673491.4990] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.247
Some issues getting a lease in logs..
I would set your lease time in your router’s configurator to a higher number to reduce the number of times per day you need to negotiate a new lease.
I assume that’s on the router’s end. I just rifled through the settings in the app & couldn’t find anything not behind a paywall (I’ll never understand the thought process of these companies…immense greed I suppose).
I’ll keep an eye on things over the next couple of days and mark it resolved if nothing crops up.
Yes.
I had no idea before you mentioned it that this was happening.
I haven’t used a commercial router in many years, so I had no idea this kind of BS was going on.
I figured setting your lease time was such a basic feature that it should be adjustable. This type garbage is just not acceptable IMO.