Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
1–10 of 92 posts
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#2The pithier article (linked to from the above) is at
https://blog.thewalr.us/2017/09/26/raspberry-pi-zero-w-simul...
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#3Any idea why systemd was not able to be reliably used, and had to use cron?
Is there a ‘fix’ for that ?
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.
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#4Thanks for this.
I had built [similar repository](https://github.com/computationalprivacy/unveil-pi-data-colle...) as a part of wifi data capture and visualisation experiment ([Project UNVEIL](https://github.com/computationalprivacy/unveil-deployment)) but it used external antenna.
Any links on how does underlying hardware work to enable simultaneous connections?
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#5Any idea why systemd was not able to be reliably used, and had to use cron? Is there a ‘fix’ for that ? 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.
I think it’s just a shortcut because of lack of experience with systemd (this is not intended to be offensive btw - if cron is already installed and you save time by just using what you know, why not?). I would be very surprised if cron could do something that can’t be done with systemd timers.
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#6Any idea why systemd was not able to be reliably used, and had to use cron? Is there a ‘fix’ for that ? 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.
No idea! I spent some time debugging it, but it just does't make sense it works with cron and not with systemd. Let me know if you have any idea where to look!
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#7Any idea why systemd was not able to be reliably used, and had to use cron? Is there a ‘fix’ for that ? 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.
I think it’s just a shortcut because of lack of experience with systemd (this is not intended to be offensive btw - if cron is already installed and you save time by just using what you know, why not?). I would be very surprised if cron could do something that can’t be done with systemd timers.
I saw the apt install cron, and wondered what the solution w/out cron entailed.
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#8Any idea why systemd was not able to be reliably used, and had to use cron? Is there a ‘fix’ for that ? 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.
I think it’s just a shortcut because of lack of experience with systemd (this is not intended to be offensive btw - if cron is already installed and you save time by just using what you know, why not?). I would be very surprised if cron could do something that can’t be done with systemd timers.
I suspected that the network wasn't ready, so I configured the service start after network without much luck. I didn't go further than that.
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#9Whatever happened to ad-hoc mode?
Re: Simultaneous AP and Client Mode Wi-Fi on Raspberry Pi Zero W
#10Earlier quoted context omitted.
I think it’s just a shortcut because of lack of experience with systemd (this is not intended to be offensive btw - if cron is already installed and you save time by just using what you know, why not?). I would be very surprised if cron could do something that can’t be done with systemd timers.
I suspected that the network wasn't ready, so I configured the service start after network without much luck. I didn't go further than that.
Systemd can be very powerful and you can even depend on individual devices being added/removed. I’m pretty sure you can even replace the udev rules with a systemd equivalent if you tried hard enough.