Timeline for AP and client mode on Pi0W Raspbian Buster
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 16:27 | comment | added | Ingo | @BasslineSoup If there are still questions open, please create a new question. | |
| Jun 15, 2020 at 14:15 | comment | added | Bassline Soup |
Thanks Ingo. I think I have worked out how to manipulate both client mode and ap mode dynamically using a combination of wpa_cli, and to disable the AP I am running sudo hostapd_cli disable, then editing the hostapd-conf file if required and then restarting with systemctl restart hostapd.service. This seems to allow client mode to only be down very temporarily when hostapd restarts. The only thing I can't work out is how to make hostapd initially load as if sudo hostapd_cli disable has been run? Basically when rpi boots I want the ssid disabled until I manually restart hostapd?
|
|
| Jun 13, 2020 at 7:41 | comment | added | Ingo |
@BasslineSoup sudo systemctl stop hostapd.service, modify /etc/hostapd.conf, sudo systemctl start hostapd.service.
|
|
| Jun 12, 2020 at 18:53 | comment | added | Bassline Soup | I mean changing the ap SSID/PSK dynamically without rebooting. (Btw I wasn’t blaming your tutorial for the quote issue, that was completely my fault!) | |
| Jun 12, 2020 at 18:12 | comment | added | Ingo |
@BasslineSoup For changing the WLAN without rebooting you can use wpa_cli --help | less. What do you mean with "dynamically creating AP"?. You can use the commands ip, iw and systemctl to create an AP by hand.
|
|
| Jun 12, 2020 at 17:59 | comment | added | Bassline Soup |
Thanks Ingo! systemctl status [email protected] gave me a few errors. It turns out I was using the wrong type of double quotes! I didn't even know there were different types! I knew there was a backtick vs inverted comma but not curly double quotes vs straight! Might be worth adding a small note to your other tutorial as it could be an easy trip-up. Cool, back to where I was this morning! Now any ida the best approach for dynamically changing the WLAN without rebooting? And for dynamically creating AP? Thanks again!
|
|
| Jun 12, 2020 at 16:58 | comment | added | Ingo |
@BasslineSoup Look for possible error messages with systemctl status systemd-networkd.service, systemctl status [email protected] and journalctl -b -e. You can also start wpa_supplicant in debug mode. Look at the end of this answer: How to correctly restart wpa_supplicant debug with networkd-systemd?.
|
|
| Jun 12, 2020 at 15:58 | comment | added | Bassline Soup | What is very strange is I was playing around with various settings and decided to start from scratch so re-flashed OS and did everything again. I have since tried about 8 times both with Lite and Desktop just to do client connection without AP and just can't get it to work! I'm following everything to the letter and it doesn't make sense why it worked first time and now I have no luck | |
| Jun 12, 2020 at 11:04 | vote | accept | Bassline Soup | ||
| Jun 12, 2020 at 11:04 | comment | added | Bassline Soup | Thanks Ingo. I have tried again with my version of Raspbian and it didn't work but worked with both lite and desktop of the current Pi OS versions. I think that because my image had connected to the WLAN previously (presumably using dhcpcd) that this created an issue. Can you recommend the best way to dynamically scan and connect to SSID's with this config? And to dynamically create AP? Thanks for your help! | |
| Jun 11, 2020 at 19:30 | history | answered | Ingo | CC BY-SA 4.0 |