Portal login that is just a simple code, putting captive portal pages back to de
-
i'm new to this, so please give a noob a break. ;D
i have read through the captive portal config stuff and most of the methods seem to require either too much user interaction to authenticate or require backend servers. i'm looking to do something similar to vouchers except it's one simple code that would last for a week that all of the users can use. from what i've read vouchers are limited as to how many times they can be used and it sounds like if another device logs in using that voucher, the original is disconnected. maybe i'm wrong. or is there a way to use user id's and passwords and have the id part already "canned" into the user name field so all they have to enter is the password?
the other thing i'd like to do is to have a custom portal page. i have looked at some examples that have been posted and there are some great ideas there. what i want to know is if i create my own custom portal page and then want to go back to the default pages how do i get back to them? are there files in some directory that i need to copy prior to uploading my custom stuff and if so where will i find them?
thanks
-
Vouchers work just fine for this. Definitely no limit on how many times they can be used while still valid, plus you can use the same voucher on any number of devices at the same time without causing anyone to get logged off – unless you limited it to one in configuration.
-
i have activated vouchers and it seems easy enough. the verbiage in the screen says that if the voucher is used on another device that the previous session is cancelled. i want multiple devices to be able to use the same voucher. i'd like to keep the code down to 4 or 5 characters that i can change every week. i know that's not too secure, but it's like having a lock on a glass door. the brute force people will break the glass/code to get in and the casual door pusher/device will be locked out without the key/code. i'm trying to operate on the KISS principle.
-
I think that's only if Concurrent user logins is disabled.
Regarding the voucher length, getting down to 4 or 5 characters is going to be hard. The smallest I could manage was this:
31-bit RSA key
Character set: 2345678abcdefhijkmnpqrstuvwxyz
# of Roll Bits: 12
# of Ticket Bits: 12
# of Checksum Bits: 8That yields 7-8 characters. You can get fewer characters by adding capital letters to the character set, but that really doesn't make it any easier for users to enter on their phones.
No, you won't clobber the default page. It's included in the captiveportal.inc php page.
As far as going back to defaults you have to upload a 0-length file. On unix you could:
cp /dev/null captive_portal_reset.html
Then upload that as the page content file.
