Posted: Fri Jun 23, 2017 7:06 Post subject: Easy Solution for Restaurant Hotspot with Asus RT-N18U
Hi, I'm looking for an easy solution for:
Hotspot that redirect user to a webpage, ask him for his emailaddress and then grant Internet Access to his MAC for lets say 2 hours.
I have DD-WRT v3.0-r32170 std (06/01/17) installed.
Router Works fine - WIFI Works fine.
I tried with chillispot and onboard radiusserver - radisserver worked but didn't get chillispot to run properly.
I tried nocatsplash - no way.
Is there an Instruction for dummies? (and I really won't call me dummy if I wouldn't hat spend so much time until now)
I don't want to use public services, it must be all STANDALONE.
Thanks
Markus
Joined: 03 Jan 2017 Posts: 49 Location: Lindau, Germany
Posted: Sat Jun 24, 2017 14:06 Post subject: Re: Easy Solution for Restaurant Hotspot with Asus RT-N18U
Hello Markus,
I managed to get an chillispot guest network (vap on wl0.1) running on my dd-wrt router (with KONG firmware 32170) not long ago. It uses only the build-in webserver (lighttp) and build-in hotspot (coovachilli).
I do not use freeradius: coovachili allows the specification of usernames und passwords itself in a simple file. To use a radius server would allow far more options I think but I don't need them. For me it is complex enough.
I tried several instructions on the net and other hotspots (e.g. wifidog) but as far as I remember most of them are to specific or describe a complete different and more complex approach.
Short explanation of the steps I successfully went through:
1) Setup of vap wifi for "guest-access" (e.g. wl0.1) in bridge mode, create a bridge (e.g. br1) with
the containing the interface and assure that no DHCP server is installed or running on this interface or bridge. Chilli has an own dhcp server. I only use one vap, my "old" guest wifi is deleted. Theoretically several vap networks should be possible but I've not tested it.
2) Enable and configure of the build-in webserver lighttp: A hotspot.php file is required to authenticate (I used this one https://wiki.iserv.eu/w/images/d/d0/Hotspot.zip. It has to be modified to work, e.g. $uamsecret! Without modification it requires https) via the integrated webserver. It has to be placed under jffs/www (or where the webserver files are located).
You can test it by adressing it via a browser from the PC: You should get an error message that it can only be accessed by a router.
3) Configure chilli-spot for the generated bridge and link to the http(s) address of the generated hotspot.php file.
If coovachilli is running it uses the tun0 device.
4) Adapt the firewall-settings: The stock configuration is quite OK but can be improved. Therefore two scripts are used (ip-up.sh and ip-down.sh)
5) In my setup communication with radius is not required as I use the integrated user/password option. There is a config file in which the user/passwords are stored.
6) The location of the password/user file (fonusers.local) and the ip-up.sh and ip-down scripts can be exchanged via "Additional Chillispot Options": These settings overrides the default path. This makes an adaption simple by scripts/files on an external storage.
In the end much work for a simple configuration, even without radius. I haven't tried to use radius (yet).
So if one of the steps may help you let me know and I can give you my detailed configuration for guidance.