| File | Date | Author | Commit |
|---|---|---|---|
| web | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| .gitignore | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| LICENSE.txt | 2016-12-05 |
|
[b714ea] Release v1.0 |
| README.md | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| config.py | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| index.html | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| install.py | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| otpspot.py | 2018-06-22 |
|
[7bed0d] Release v2.0 |
| template_pam | 2016-12-05 |
|
[d3ba65] Initial commit |
| template_service.sh | 2018-06-22 |
|
[7bed0d] Release v2.0 |
Run a captive portal on your raspberry (or any linux box) to allow your guests to register before accessing your Wifi at home.
Users will be requested for an OTP code that you can generate on your phone. Get rid of the typical captive portal static
username and password without the need for a radius server.
OTPspot (since version 2.0) is fully compatible with nodogsplash and can run as a FAS service. In this configuration,
nodogsplash will take care of the networking whereas OTPspot will just authenticate the users.
Once a user connects to the guest wireless network, nodogsplash will make te device detecting additional credentails are required and present the user with the OTPspot web-based and responsive captive portal where an access code is requested for
the authentication.
This code is generated by the Google Authenticator/Authy app running on the host's phone and aligned with a service running on the raspberry used to validate the authentication. This requires the google-authenticator service running on the raspberry and
a custom pam service which is provided by OTPspot and installed automatically.
Once a valid OTP is provided the portal will notify nodogsplash the user has successfully authenticated and Internet access
will be then granted.
To install and configure nodogsplash on a Openwrt-based router: