User:Magick777/WISPr WiFi Autologin
(→Methods) |
|||
| Line 8: | Line 8: | ||
== Methods == | == Methods == | ||
| - | My preference is for event-driven, script-based autologin; whilst turning it into an application might take it to the masses, we then have needless complications of putting a GUI on it, running a daemon to take care of listening for new connections, etc. So, my aim is for a command line client that can be launched from dbus-scripts on connection to a wireless network. | + | My preference is for an event-driven, script-based autologin; whilst turning it into an application might take it to the masses, we then have needless complications of putting a GUI on it, running a daemon to take care of listening for new connections, etc. So, my aim is for a command line client that can be launched from dbus-scripts on connection to a wireless network. |
This client should | This client should | ||
| Line 24: | Line 24: | ||
* interfere with connections to private or non-WISPr WiFi networks | * interfere with connections to private or non-WISPr WiFi networks | ||
* open any popups or applications that require user interaction | * open any popups or applications that require user interaction | ||
| - | |||
== Sources == | == Sources == | ||
See also http://talk.maemo.org/showthread.php?t=90777 | See also http://talk.maemo.org/showthread.php?t=90777 | ||
Revision as of 07:36, 23 July 2013
This page documents work on automated logins to UK WiFi hotspots, and attempts to achieve native support in the N900 for WISPr auto-login, on any hotspot network that supports it.
Existing WISPr clients
WISPr clients seem to be very few and far between; it's used in network-specific clients such as the BT app, and there are generic clients for Android and iOS, but it hasn't taken off in a big way.
Methods
My preference is for an event-driven, script-based autologin; whilst turning it into an application might take it to the masses, we then have needless complications of putting a GUI on it, running a daemon to take care of listening for new connections, etc. So, my aim is for a command line client that can be launched from dbus-scripts on connection to a wireless network.
This client should
- make an HTTP GET request and determine whether we are connected
- determine whether our captive portal supports WISPr
- determine whether we have credentials
- attempt authentication and determine the response
- (optionally) record the logoff URL and provide a means to log off
- (optionally) notify the user of relevant information during the process
- support multiple sets of credentials for multiple WISPr captive portals
but should not
- interfere with connections to private or non-WISPr WiFi networks
- open any popups or applications that require user interaction