As nodogsplash Captive Portal support might be changing to an iptables approach instead, I won't push these DRAFT configuration materials (transcribed from http://minutes.iiab.io under Dec 28, 2017 Item 2. h.) into FAQ.IIAB.IO until the outcome is more clear...

Captive Portal Experimentation (#597) Summary:

Set these both to True in your /opt/iiab/iiab/vars/local_vars.yml :
nodogsplash_install: True
nodogsplash_enabled: True
Arrange for Ansible to run the nodogsplash playbook AFTER ./iiab-install (incl network playbook!) have completed, similar to the 5-line “CALIBRE” section in roles/9-local-addons/tasks/main.yml but remember the “network” playbook runs AFTER Stage 9.
1. Explanation: IIAB’s networking playbook will revert iptables. So you need the nodogsplash playbook To Run At The Very End!
Works very well on Windows/Mac...but Android sign-in page never quite goes away? Also a time-out issue might hit Android folk etc. So encourage them to bookmark it after they get thru to http://box or whatever. Android is the worst, old or new Android :-( (Possibly Firefox on Android isn’t so bad?)
1. Tim pasted in his testing across 4 platforms, so others can confirm problem clients: initial check in #597 (comment)
Modify its configuration until you get your favorite browsers/clients working better:
1. /etc/nodogsplash/nodogsplash.conf ← modify this one especially!
2. /etc/nodogsplash/htdocs/splash.html
3. Of course run “systemctl restart nodogsplash” each time to test!
4. Possibly change the timeout (which uses client devices’ MAC addresses) reducing it to 10min or so? (George's suggestion)
5. Later do the same with Ansible?
  https://github.com/iiab/iiab/blob/master/roles/nodogsplash/templates/nodogsplash.conf.j2
  https://github.com/iiab/iiab/blob/master/roles/nodogsplash/templates/splash.html.j2

Captive Portal experimental support summary in FAQ.IIAB.IO ? #608

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions