While I cannot specifically answer that part, I did some digging on the update_config option that arch refers to.
It turns out, on a default Slack install you would not know if that option is available or not.
So what I did was download the source tarball:
http://slackware.osuosl.org/slackwar...pa_supplicant/
Then I reviewed the contents of:
wpa_supplicant-0.6.9/wpa_supplicant/wpa_supplicant.conf
Which is a default file that comes with the source and is different than the one that Slackware ships.
The following is the notes from the source on that option:
Quote:
# Whether to allow wpa_supplicant to update (overwrite) configuration
#
# This option can be used to allow wpa_supplicant to overwrite configuration
# file whenever configuration is changed (e.g., new network block is added with
# wpa_cli or wpa_gui, or a password is changed). This is required for
# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove the comments from
# it.
#update_config=1
|
So my though is on this is; our wpa is similar enough to the arch wiki tutorial. So if we assume they're correct, it should work for you if what they're describing is what you want.
Just be sure to backup any files before you go making changes and forget what you did, so you can revert back to clean config's if need be.
Hope that helps even tho it doesn't completely answer your question, as I don't have that many routers here to do a test like that here
- Fogie