RaspAP Known WiFi Client Auto-connect #1563
Replies: 2 comments 3 replies
-
This is the default behavior of wpa_supplicant. That is, on startup the wpa_supplicant.service is executed by systemd (not RaspAP) and enables logging and the DBus control interface, nothing more.
The DBus interface is used to communicate with wpa_supplicant. You can have it auto connect on startup by adding the following to the root user's crontab:
|
Beta Was this translation helpful? Give feedback.
-
I used this way to autoconnect ... but still got one problem. If there is a way the connection could be reconnect automatically too, it would be perfect. I realized the autoconnect with a crontab that runs every minute and checks the interface connection. If it is not connected it makes a scan to lookup for known networks. If a known network is found it connects. But is the connection lost - no more scans are possible :( |
Beta Was this translation helpful? Give feedback.
-
I'm using RaspAP with two WiFi networks: wlan1 for the AP and wlan0 as the client connecting to a network with access to the Internet and this works great. However, I will like to know if there is a way to set RasAP to auto connect to known wifi client on boothup in stead of having to do this manually every time.
Beta Was this translation helpful? Give feedback.
All reactions