From b253a712d8f1c0c78d2f26bebcc664593e9f7e33 Mon Sep 17 00:00:00 2001 From: TristanAncelet Date: Tue, 9 Feb 2021 15:22:53 -0600 Subject: [PATCH] fixed even more syntax errors --- WifiConnectivityIssues.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/WifiConnectivityIssues.md b/WifiConnectivityIssues.md index c448cb4..34db2c7 100644 --- a/WifiConnectivityIssues.md +++ b/WifiConnectivityIssues.md @@ -1,12 +1,10 @@ # Wi-Fi Connectivity Issues ## Related Posts: ------------------ - [DNS Issues](DNS_Issues.md) ## Background: --------------- After a while of using Arch I've encountered a few issues with DNS and Wireless Connectivity. The DNS Issue was solved after a while due to some competing daemon's. The Wireless Connectivity issues were small but were irritating to deal with after each reboot. @@ -15,15 +13,13 @@ I'm using Gnome as a Desktop Enviroment on my Arch install, and it comes with Ne ## Problem: ------------ + After each time I reboot my computer or it goes into standby, my computer loses connection to the wifi (I assume it's dropped to save power. After which iwd either starts off connected, or automatically connects due to the wireless interface being unused. This is an issue because without wpa_suppicant being the one holding the connection all of the apps (aside from the terminal) cannot connect to the internet to preform the duties I need them for. This is aggravating since it requres me to spam "iwctl station wlan0 disconnect" while also making sure that I go to the wifi tab and select my wifi to connect to. While I can deal with this, it is still not a nice situation to be in. - ## Process: ------------ After some searching I found [this post][Post] that details how to configure NetworkManager to use iwd as the wifi backend instead of wpa_supplicant. @@ -31,7 +27,7 @@ The steps I had to take from here were: 1. Add this line of code into my NetworkManager.conf file. -'''bash +''' [device] wifi.backend=iwd ''' @@ -40,7 +36,6 @@ wifi.backend=iwd ## Conclusion --------------- After doing this I have yet to happen upon this issue again (although it has only been a few hours).