I've been using a similar solution, but I had quite some problems using AP and client mode at the same time. The WiFi chip inside the RPi Zero W (BCM43430) only supports AP and client mode on the same channel. If you setup an AP first, then connect to a client network, hostapd will update the channel of the AP, but clients will notice a disconnect. There are also issues with the firmware blob (see <a href="https://github.com/raspberrypi/firmware/issues/1403" rel="nofollow">https://github.com/raspberrypi/firmware/issues/1403</a>) in AP mode that haven't been solved yet.
The pithier article (linked to from the above) is at<p><a href="https://blog.thewalr.us/2017/09/26/raspberry-pi-zero-w-simultaneous-ap-and-managed-mode-wifi/" rel="nofollow">https://blog.thewalr.us/2017/09/26/raspberry-pi-zero-w-simul...</a>
Thanks for this.<p>I had built [similar repository](<a href="https://github.com/computationalprivacy/unveil-pi-data-collector" rel="nofollow">https://github.com/computationalprivacy/unveil-pi-data-colle...</a>) as a part of wifi data capture and visualisation experiment ([Project UNVEIL](<a href="https://github.com/computationalprivacy/unveil-deployment)" rel="nofollow">https://github.com/computationalprivacy/unveil-deployment)</a>) but it used external antenna.<p>Any links on how does underlying hardware work to enable simultaneous connections?
This is perfect for hotels whose TV sucks and their wifi has those captive portals so you can't use a Chromecast, Firestick, or Roku.<p>It just needs a captive portal of its own when the client side is disconnected.
Would this be good for something like connecting the Pi to a VPN for say Canada, then broadcasting an SSID for it.<p>Then connecting a Fire TV Stick or Chromecast to this AP, and tricking it into letting you stream Canadian Netflix or DAZN etc.
Any idea why systemd was not able to be reliably used, and had to use cron?<p>Is there a ‘fix’ for that ?<p>edit: This was not meant to be offensive. I was simply hoping somebody could offer how it could be used with systemd and remove the reliance on cron.
Can this be used as a range extender if you use the same SSID and password for the access point as the net you're connecting to? Would other clients silently roam between the two (or more) networks using the same name and password?
I wonder what's the use case other than a poor wifi extender, or niche cases of sharing one connection between multiple devices where you pay per connection.<p>Though I do wonder whether you can add a proper wifi antenna and make the RPI an 'ok' wifi extender. That might be a viable option, provided the performance is ok.
Why is that not easy and widely used as nearly all devices we used like camera (dslr to car camera) and remote controller all resolved to stop WiFi and switch to another mode etc to connect.
A bit off topic:<p>I'm looking for a project that starts with an AP. Once someone connected to it; it opens a web page to configure the client (choose which WIFI from a list, and type the password).<p>It connects to the chosen WIFI and shuts down the AP.<p>Anyone here did something similar to that?
Just curious, but I was trying to help someone with a Raspberry Pi Zero W wifi issue the other day and had trouble finding sny info about the wireless chipset used. I couldn't find it listen anywhere on the site, or several tech review sites, only extremely useless information on the 802.11 versions support. If it recall correctly, it didn't even show up in the schematica. Luckily wikipedia had the name of the chipset used, but I don't get it. Why does their official documentation seem to be so secretive?
How to get faster internet at a hotel:
Have 4-5 of these connected and talking with the hotels WiFi, and one who share Internet with you. All the traffic goes to a server you have at home that “join+proxy” the traffic. Based on the idea that every user have a limited bandwidth, combining multiple will give you higher speed.