892
edits
Difference between revisions of "Mesh/Firmware/Splash page"
Jump to navigation
Jump to search
no edit summary
(Created page with "The splash page will be automatically displayed by devices that support captive portal detection. The splash page will not actually be a captive portal, it will only specifica...") |
|||
| Line 1: | Line 1: | ||
Some operating systems will attempt to detect whether you are behind a captive portal when you connect to a new network. This usually involves fetching a web page with known content from a web server controlled by the company behind the operating system. If a captive portal is detected, the operating system will pop up a dialog showing the web page from the captive portal. | |||
= Types of detection = | We will run a fake captive portal that causes our splash page to be displayed on any operating system supporting captive portal detection. The fake captive portal will _only_ interfere with captive portal detection traffic. All other traffic will go through unaltered. The fake captive portal will run on the [[network topology|exit nodes]] and so will only be active when the mesh is connected to the internet. | ||
If the mesh becomes disconnected from the internet, then all HTTP GET requests to the internet will receive 302 HTTP redirects to a community portal web app running on a server on the mesh that will inform the user that the internet is down. The redirection is accomplished with [https://github.com/sudomesh/internetisdownredirect internetisdownredirect]. If the node is not connected to any server running the community portal web app, then all HTTP GET requests will receive 302 HTTP redirects to a local web page telling the user that your mesh node has become disconnected from the rest of the mesh, and who to contact about it. | |||
Currently this page talks mostly about how to implement the fake captive portal. | |||
= Types of captive portal detection = | |||
== Android == | == Android == | ||