||7 years ago|
|bower_components||7 years ago|
|dist||7 years ago|
|img||7 years ago|
|includes||7 years ago|
|js||7 years ago|
|less||7 years ago|
|.gitignore||7 years ago|
|README.md||7 years ago|
|bower.json||7 years ago|
|index.php||7 years ago|
A simple, responsive web interface to control wifi, hostapd and related services on the Raspberry Pi.
This project was inspired by a blog post by SirLagz about using a web page rather than ssh to configure wifi and hostapd settings on the Raspberry Pi. I mostly just prettified the UI by wrapping it in SB Admin 2, a Bootstrap based admin theme 😄
Start off by installing lighttpd and php5.
$ apt-get install lighttpd php5-cgi
After that, enable PHP for lighttpd and restart it for the settings to take effect.
sudo lighty-enable-mod fastcgi-php /etc/init.d/lighttpd restart
Now comes the fun part. For security reasons, the
www-data user which lighttpd runs under is not allowed to start or stop daemons, or run commands like ifdown and ifup, all of which we want our page to do.
So what I have done is added the
www-data user to the sudoers file, but with restrictions on what commands the user can run.
Add the following to the end of
www-data ALL=(ALL) NOPASSWD:/sbin/ifdown wlan0,/sbin/ifup wlan0,/bin/cat /etc/wpa_supplicant/wpa_supplicant.conf,/bin/cp /tmp/wifidata /etc/wpa_supplicant/wpa_supplicant.conf,/sbin/wpa_cli scan_results, /sbin/wpa_cli scan,/bin/cp /tmp/hostapddata /etc/hostapd/hostapd.conf, /etc/init.d/hostapd start,/etc/init.d/hostapd stop,/etc/init.d/dnsmasq start, /etc/init.d/dnsmasq stop,/bin/cp /tmp/dhcpddata /etc/dnsmasq.conf
Once those modifications are done, git clone the files to
sudo git clone https://github.com/billz/raspap-webgui /var/www
Set the files ownership to
sudo chown -R www-data:www-data /var/www
Reboot and it should be up and running!
How to contribute
- File an issue in the repository, using the bug tracker, describing the contribution you'd like to make. This will help us to get you started on the right foot.
- Fork the project in your account and create a new branch:
- Commit your changes in that branch.
- Open a pull request, and reference the initial issue in the pull request message.
See the LICENSE file.