Thanks.
I applied the same changes and get the same feedback as Peter (above).
For the record I get the same response with not only the TP-Link TL-WN722N but also the WIPI (FCC ID: OYR-COMFAST88). Both are listed as known to be working. I just wondered what might be different in our cases here where the setup is working.
I applied the same changes and get the same feedback as Peter (above).
[root@alarmpi ~]# systemctl status piratebox * piratebox.service - PirateBox Service Loaded: loaded (/etc/systemd/system/piratebox.service; enabled) Active: failed (Result: exit-code) since Wed 1969-12-31 17:00:10 MST; 44 years 6 months ago Process: 107 ExecStart=/opt/piratebox/init.d/piratebox_alt start (code=exited, status=255) Dec 31 17:00:10 alarmpi piratebox_alt[107]: Starting hostap... Dec 31 17:00:10 alarmpi piratebox_alt[107]: 0 Dec 31 17:00:10 alarmpi piratebox_alt[107]: Setting up wlan Dec 31 17:00:10 alarmpi piratebox_alt[107]: Bringing up wifi interface wlan0 Dec 31 17:00:10 alarmpi piratebox_alt[107]: wlan0: ERROR while getting interface flags: No such device Dec 31 17:00:10 alarmpi piratebox_alt[107]: ..failed Dec 31 17:00:10 alarmpi systemd[1]: piratebox.service: control process exited, code=exited status=255 Dec 31 17:00:10 alarmpi piratebox_alt[107]: failed setting up Interface Dec 31 17:00:10 alarmpi systemd[1]: Failed to start PirateBox Service. Dec 31 17:00:10 alarmpi systemd[1]: Unit piratebox.service entered failed state.
For the record I get the same response with not only the TP-Link TL-WN722N but also the WIPI (FCC ID: OYR-COMFAST88). Both are listed as known to be working. I just wondered what might be different in our cases here where the setup is working.