Timeline for Swapping between wifi client and access point?
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2019 at 19:02 | history | edited | Ingo | CC BY-SA 4.0 |
Deleted option "ap_scan=2" in wpa_supplicant.conf
|
| Jan 21, 2019 at 2:08 | history | edited | Ingo | CC BY-SA 4.0 |
Added link to the new answer.
|
| Jan 5, 2019 at 0:32 | history | edited | Ingo | CC BY-SA 4.0 |
Added DNS-server for DHCP-server delivery on access point
|
| Sep 29, 2018 at 11:09 | comment | added | dazz | raspberrypi.stackexchange.com/questions/89484/… | |
| Sep 29, 2018 at 10:58 | comment | added | Ingo | @dazz Make a new question with this. | |
| Sep 29, 2018 at 10:56 | comment | added | dazz | I finished the setup to get ap and client wifi running together. On bootup, wlan0 works perfectly. Journalctl didn't report any attempt to run ap0. The status command reported ap0 loaded but not active. I then ran "systemctl start [email protected]. Journal reported "systemd[1]: sys-subsystem-net-devices-ap0.device: Job sys-subsystem-net-devices-ap0.device/start timed out" | |
| Sep 29, 2018 at 10:54 | comment | added | Ingo |
@dazz I have clarified that part in the answer. hostapd is needed if you want to run access point AND wifi client connection together. wpa_supplicant has problems with wifi driver doing both at the same time. This is on switching the connection as shown here not the case. But we get problems with the comments here. It's to much. Because of your restriction I would open a new question with reference to Raspberry Pi Zero W as a WiFi repeater if there are some more questions. Then you are free to comment to your own question like here.
|
|
| Sep 29, 2018 at 9:31 | comment | added | dazz | I have a question on the link above. This should be in the comments at the link but I can't put a comment there without 50 credits. I don't seem to be able to chat to you. The sentence beginning "We do not need this because..." is not clear to me. If something is not needed, can it be removed from your answer? | |
| Sep 29, 2018 at 9:24 | comment | added | dazz | Yes, I am working through it now, on a fresh Raspian build. By following those instructions, I have installed hostapd. I didn't do that following the above instructions and the ones before that. I suspect that was my problem. | |
| Sep 29, 2018 at 6:57 | comment | added | Ingo | @dazz But there IS a solution, do you follow the link above? | |
| Sep 29, 2018 at 4:55 | comment | added | dazz | Running client and ap at the same time is what I really need/want but I didn't think it would be possible until I stumbled onto a solution. Thanks for your help. :-) | |
| Sep 28, 2018 at 20:38 | comment | added | Ingo | @dazz Ah.. you want to run an access point together with client connection at the same time. No problem. You can find it at Raspberry Pi Zero W as a WiFi repeater. If something is unclear you can comment there. | |
| Sep 28, 2018 at 19:30 | comment | added | dazz | I went through all the config and I haven't found any typos. Today I will build a fresh version of Raspian and try to get this working, then compare to what I have on my current build. What I really want to do is have simultaneous and managed mode running at the same time. I found this article here: blog.thewalr.us/2017/09/26/… That would avoid any need to switch between the modes. I have no idea how/if that might be done with systemd-networkd. That would be the basis of another question. | |
| Sep 28, 2018 at 17:20 | history | edited | Ingo | CC BY-SA 4.0 |
Corrected typo
|
| Sep 28, 2018 at 14:12 | comment | added | Ingo |
A typo? That must be corrected of course. 3B or 3B+ doesn't matter. wlan0 as client is mostly stable. "no such device" is right when addressing absent ap0. Just use sudo iw dev. I have updated my answer with a section Troubleshooting. Tell me if you get it to run or not.
|
|
| Sep 28, 2018 at 14:01 | history | edited | Ingo | CC BY-SA 4.0 |
Added section for troubleshooting
|
| Sep 28, 2018 at 11:00 | comment | added | dazz | running sudo iw dev ap0 info gives: command failed: no such device (-19). | |
| Sep 28, 2018 at 10:59 | comment | added | dazz | OK I set the underscores. It is running on a RasPi 3 but I do have 3Bs and 3B+, all running Stretch Lite. The logs state a "usage" problem which indicates a typo. I have checked all the config files and they match the instructions. wlan0 is working OK. | |
| Sep 28, 2018 at 9:00 | comment | added | Ingo |
You have to set the two underscores. Otherwise it will never work. Please google with interface add ap0 type __ap. And it works on my RasPis. What RasPi do you use? Is it a RPi 3B+? Do you start from scratch with Raspbian Stretch Lite 2018-06-27 like me? The error message you give me is from systemd telling us ExecStartPre has failed. But there must be an error message from iw why it has failed. With journalctl -b -e you should find the output from iw (message prefixed with iw).
|
|
| Sep 28, 2018 at 8:14 | comment | added | dazz | wlan0 seems to be working as expected. I have problems when trying to swap to running ap mode. | |
| Sep 28, 2018 at 8:13 | comment | added | dazz | No. I am getting the error message: Process 581: ExecStartPre=/sbin/iw dev wlan0 interface add ap0 type ap (code=exited, status=2) Note that I have removed the underscores between type and ap. They didn't seem to match the documentation I found. Still doesn't work without the underscores. | |
| Sep 28, 2018 at 7:52 | comment | added | Ingo |
No, the type is OK. But the wifi driver brcmfmac is a bit buggy with access point so it it very sensitive. Is it the error message command failed: Device or resource busy (-16)?
|
|
| Sep 28, 2018 at 5:55 | comment | added | dazz | It doesn't quite work yet. The logs indicate the command 'ExecStartPre=/sbin/iw dev wlan0 interface add ap0 type __ap' failed. Could it be the 'type__ap' part?? | |
| Sep 28, 2018 at 5:38 | comment | added | dazz | Thank you for your detailed instructions. Easy to follow. | |
| Sep 27, 2018 at 23:44 | history | answered | Ingo | CC BY-SA 4.0 |