From 366df8852f503523cc4f9046d82ba9a99dd51d7f Mon Sep 17 00:00:00 2001 From: Akshay Date: Sun, 12 Feb 2023 12:13:49 +0530 Subject: new art: lapse --- docs/posts/WPA_woes/index.html | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'docs/posts/WPA_woes') diff --git a/docs/posts/WPA_woes/index.html b/docs/posts/WPA_woes/index.html index 55b2630..0a2e44c 100644 --- a/docs/posts/WPA_woes/index.html +++ b/docs/posts/WPA_woes/index.html @@ -28,7 +28,7 @@ 12/10 — 2019
- 18.37 + 18.38 cm   @@ -42,8 +42,12 @@ WPA Woes
-

I finally got around to installing Void GNU/Linux on my main computer. Rolling release, non-systemd, need I say more?

-

As with all GNU/Linux distributions, wireless networks had me in a fix. If you can see this post, it means I’ve managed to get online. It turns out, wpa_supplicant was detecting the wrong interface by default (does it ever select the right one?). Let us fix that:

+

I finally got around to installing Void GNU/Linux on my main +computer. Rolling release, non-systemd, need I say more?

+

As with all GNU/Linux distributions, wireless networks had me in a +fix. If you can see this post, it means I’ve managed to get online. It +turns out, wpa_supplicant was detecting the wrong interface +by default (does it ever select the right one?). Let us fix that:

$ sudo rm -r /var/service/wpa_supplicant
 $ sudo killall dhcpcd

What is the right interface though?

@@ -51,7 +55,8 @@ $ sudo killall dhcpcd ... Interface wlp2s0 ... -

Aha! Let us run wpa_supplicant on that interface, as a background process:

+

Aha! Let us run wpa_supplicant on that interface, as a +background process:

$ sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
 $ sudo dhcpcd -B wlp2s0
 $ ping google.com
-- 
cgit v1.2.3