TheExpertNoob Wrote:
-------------------------------------------------------
> I don't know if putting it on the boot partition
> would be easier for the end user to edit it, mount
> /dev/boot to /boot on startup, and have
> WPA_supplicant pull config from
> /boot/WPA_supplicant.conf (fat 32 partition easliy
> readable on all systems to edit the file before
> first boot this way, a console cable may not be
> needed) As most users will probably be windows
> users.
> Also, a script to "toggle" between WPA and hostapd
> modes for the zero.
This is a great idea. Will implement it like this. Need to find a work around for qemu tho, since it is complaining about entries in /etc/fstab, that is why I "cleared" them ;-)
Your WiFi stick is registered after the init scripts run - that is a Problem.
I *think* we can solve this with a udev rule - but this means piratebox is not allowed to be enabled as a service at bootup but rather triggered by the udev rule when the driver is ready - don't know how to do that for *all* WiFi sticks with a single rule :-/
Other, ultra hacky way would be a wrapper script for the piratebox init. It would need to check every n seconds if the wifi device is available and only then run the init script.
TheExpertNoob thank you for all the logs, this helps a lot :-) Almost feels if I was working on a Zero myself.
-------------------------------------------------------
> I don't know if putting it on the boot partition
> would be easier for the end user to edit it, mount
> /dev/boot to /boot on startup, and have
> WPA_supplicant pull config from
> /boot/WPA_supplicant.conf (fat 32 partition easliy
> readable on all systems to edit the file before
> first boot this way, a console cable may not be
> needed) As most users will probably be windows
> users.
> Also, a script to "toggle" between WPA and hostapd
> modes for the zero.
This is a great idea. Will implement it like this. Need to find a work around for qemu tho, since it is complaining about entries in /etc/fstab, that is why I "cleared" them ;-)
Your WiFi stick is registered after the init scripts run - that is a Problem.
I *think* we can solve this with a udev rule - but this means piratebox is not allowed to be enabled as a service at bootup but rather triggered by the udev rule when the driver is ready - don't know how to do that for *all* WiFi sticks with a single rule :-/
Other, ultra hacky way would be a wrapper script for the piratebox init. It would need to check every n seconds if the wifi device is available and only then run the init script.
TheExpertNoob thank you for all the logs, this helps a lot :-) Almost feels if I was working on a Zero myself.