Network is Super Buggy

[SaltSouls]

I am having frequent issue with whatever networking system that this is using. It is constantly dropping connection, resulting in things like discord calls disconnecting and then reconnecting me. Whenever the system goes into sleep mode, there is a over 50% chance that it completely breaks my ability to connect to my network with the only way to fix it being to completely restart my system. All of this makes for a very frustrating experience when trying to use my own system as it feels like at every turn it is trying to fight me.

The connection issues are likely due to roaming being enabled by default, resulting in frequent disconnects when on networks like mine where there are multiple access points that may occasionally change in frequency strength. This could be caused by a bug with NMs built-in DHCP, which still seems to be open. The network not starting again after sleep may be linked to a driver issue, or the system failing to wake up the network card when exiting sleep.

[Anduin2017]

Is this issue can be reproduced in other OS like Ubuntu?

[Anduin2017]

By the way I guess it might be a device\driver specific problem. Because not all devices in my home are suffering from this. I also have two laptops running fine and I frequently cary those between rooms.

[SaltSouls]

Potentially. I have had issues in the past with my network card, though never really from the wifi portion of it. It is usually only the Bluetooth that has problems. Though on here that seems to not be the case funnily enough. How the turns have tabled apparently.

[SaltSouls]

Also, after having looked into some alternatives myself last night, Conman seems like it could be a good alternative to NM going forward. Might be a little more complicated to set up, but a combination of that and iwd could provide a more modern and stable basis for networking going forward. I will see if I can manage to make it work with the current system, and if so, I can send the configurations for you to maybe play around with.

[SaltSouls]

So after looking more into and experimenting with connman, it seems like it has some issues and can be pretty rough to configure. So I opted to stick to NM, but switched over to iwd. Had to fix dnsmasq/resolved as it was saying that something was already loading on 127.0.0.1. When I managed to get that fixed, it seems the network is now stable. Haven't gotten any disconnects/loss of ipv4 and my network card hasn't been shut off.

Luckily the setup for this is relatively easy. Literally just involves installing iwd and network-manager-iwd, then making sure wpa_supplicant is disabled. There are some minor configs that need to be setup to ensure things all play nicely with eachother. The dnsmasq config can, mostly(I don't think I have anything set that would break things if you didn't have it), be whatever settings you feel work best; just so long as the route is 127.0.0.1, and it is located in /etc/NetworkManager/dnsmasq.d/dnsmasq.conf.

#File: /etc/iwd/main.conf

[General]
EnableNetworkConfiguration=false

[Network]
#NameResolvingService=systemd  <-- (this can be either commented or set to systemd)
EnableIPv6=true

#File: /etc/NetworkManager/conf.d/iwd.conf

[device]
wifi.backend=iwd

#File: /etc/NetworkManager/conf.d/dhcp-client.conf

[main]
dhcp=dhcpcd

#File /etc/NetworkManager/NetworkManager.conf

[main]
rc-manager=resolvconf
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false

My dnsmasq config incase you wanted to take a closer look at it or maybe offer any suggestions to make it better: dnsmasq.conf