View previous topic :: View next topic |
Author |
Message |
krotuss Apprentice
Joined: 01 Aug 2008 Posts: 236
|
Posted: Sat Dec 09, 2023 7:20 pm Post subject: standalone wpa_supplicant |
|
|
Hi, what is running wpa_supplicant via /etc/init.d/wpa_supplicant good for?
Reason why I am asking is that I needed to add -Dwext to its parameters, and found out that when wpa_supplicant is run from net.* init script, /etc/conf.d/wpa_supplicant is ignored . I had to use wpa_supplicant_wlan0 in /etc/conf.d/net. I find this confusing, so I would like to know what is use case for running wpa_supplicant in "standalone mode". |
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 1896
|
Posted: Sat Dec 09, 2023 9:24 pm Post subject: |
|
|
The purpose is when you do not want a networking system like netifrc and just wpa_supplicant and dhcpcd as "standalone".
Though -Dwext is ancient and eventually be removed from the kernel as 90% of all WiFi devices no longer use it. nl80211 is preferred over wext in most cases. |
|
Back to top |
|
|
krotuss Apprentice
Joined: 01 Aug 2008 Posts: 236
|
Posted: Sat Dec 09, 2023 9:30 pm Post subject: |
|
|
Its irony that new staging drivers like 8188eu require it to work. |
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 1896
|
Posted: Sun Dec 10, 2023 12:55 am Post subject: |
|
|
krotuss wrote: | Its irony that new staging drivers like 8188eu require it to work. |
Please try to use rtl8xxxu driver instead of that deleted staging driver since kernel 6.3.
By this i mean try the updated rtl8xxxu now before the device will stop working in the future. |
|
Back to top |
|
|
krotuss Apprentice
Joined: 01 Aug 2008 Posts: 236
|
Posted: Sun Dec 10, 2023 10:46 am Post subject: |
|
|
It doesn't work:
Code: | [ 144.506842] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 144.507024] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 144.507032] Loading firmware: regulatory.db
[ 144.514085] Loading firmware: regulatory.db.p7s
[ 144.561654] usbcore: registered new interface driver rtl8xxxu
/etc/init.d/net.wlan0 start
* Bringing up interface wlan0
* ERROR: interface wlan0 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.wlan0 failed to start
|
IIRC some modules used to have params to force them to bind to specific hardware. But it doesn't seem to be the case here (or I am missing it):
Code: | modinfo rtl8xxxu
...
sig_hashalgo: unknown
signature:
parm: debug:Set debug mask (int)
parm: ht40_2g:Enable HT40 support on the 2.4GHz band (bool)
parm: dma_aggregation:Enable DMA packet aggregation (bool)
parm: dma_agg_timeout:Set DMA aggregation timeout (range 1-127) (int)
parm: dma_agg_pages:Set DMA aggregation pages (range 1-127, 0 to disable) (int) |
|
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 1896
|
Posted: Mon Dec 11, 2023 5:28 pm Post subject: |
|
|
I looked into it more and the rtl8xxxu driver gained support in 6.3 for 8188eu.
Just be prepared to switch the driver in the future. -Wext can go away then as well. |
|
Back to top |
|
|
|