One Voucher Per Device
-
No progress, no code needed.
As said, you need Freeradius. The package.
On the first user you declare in Freeradius, you add this in the advanced section :
All further user will use this setting : not more then 2 logins per account.
How to set up Freeradius ?
That's not a question. This thing is huge and needs to be studied. It's like a mail server or web server, there is no such thing as "a click here and click therr and your up".I advise that you start looking at the videos from Netgate on Youtube.
Not that it really matters, but I'm using a MySQL (Maria) DB server for the Freeradius storage needs. That just a choice, none is needed actually, Freeradius can also work with a flat file data base, stored on the pfSense drive.
-
This post is deleted! -
@Gertjan said in One Voucher Per Device:
No progress, no code needed.
As said, you need Freeradius. The package.
On the first user you declare in Freeradius, you add this in the advanced section :
All further user will use this setting : not more then 2 logins per account.
@Gertjan ...ok.. i have added this above line in the freeRadius, with option 3 (First sessions per username / voucher) selected in non concurrent login, but only one device can log in, the second device comes wit the error "reuse of id not allowed'
am i missing something?? -
@colleytech said in One Voucher Per Device:
the second device comes wit the error "reuse of id not allowed'
am i missing something??Ah, so you're using my code that changes somewhat the way how vouchers login :
- many
- only last
- only first
Right ?
You can't change that behavior, except if you are will to "play"with the code (PHP script).If you are willing to drop voucher usage, and step over to the classic user/password,
and
you use FreeRadius
then
you could have something like
" Simultaneous-Use := 3 "
(maximum 2 user per login now ) -
@Gertjan said in One Voucher Per Device:
@colleytech said in One Voucher Per Device:
the second device comes wit the error "reuse of id not allowed'
am i missing something??Ah, so you're using my code that changes somewhat the way how vouchers login :
- many
- only last
- only first
Right ?
You can't change that behavior, except if you are will to "play"with the code (PHP script).If you are willing to drop voucher usage, and step over to the classic user/password,
and
you use FreeRadius
then
you could have something like
" Simultaneous-Use := 3 "
(maximum 2 user per login now )@Gertjan your code works with freeRadius users, thats what i use it for.. i dont mind going without vouchers..
if you use the default pfsense php code, the simultaneous-use =3 will work, but it wil always disconnect the logged in user, to make way for the new login...
just like what your code is doing, stopping reuse of id without disconnecting the current user,, is there a way to achieve that with freeRadius.. whereby, after two devices logs in, the third one will be dropped, instead of the already logged in devices..
Regards -
you use FreeRadius
then
you could have something like
" Simultaneous-Use := 3 "
(maximum 2 user per login now )@Gertjan i am still battling with this
... is there a way i could use this and stil not get my two connected devices disconnected when a third login attempt is done..
the goal is to get two devices per user, then a third login will be dropped instead of it, disconnecting an already connected device..thanks in advance
-
@colleytech said in One Voucher Per Device:
@Gertjan i am still battling with this... is there a way i could use this and stil not get my two connected devices disconnected when a third login attempt is done..
the goal is to get two devices per user, then a third login will be dropped instead of it, disconnecting an already connected device..That what's I'm doing right now. With FreeRadius.
Without it : I guess not. -
@Gertjan said in One Voucher Per Device:
@colleytech said in One Voucher Per Device:
@Gertjan i am still battling with this... is there a way i could use this and stil not get my two connected devices disconnected when a third login attempt is done..
the goal is to get two devices per user, then a third login will be dropped instead of it, disconnecting an already connected device..That what's I'm doing right now. With FreeRadius.
Without it : I guess not.@Gertjan ,
kindly indulge me, whenever i do it with freeradius, two devices will connect, but a third device attempting to log in will always disconnect one of the already logged in devices, thats what i am trying to avoid,,, if there is any additional setting or line of code to be added, kindly point me to it, -
@colleytech said in One Voucher Per Device:
whenever i do it with freeradius, two devices will connect, but a third device attempting to log in will always disconnect one of the already logged in devices
??
That's not my experience.The " Simultaneous-Use := 2 " statement will not allow a third login.
It doesn't kick out one of the two already logged in users.Example :
Room number (== uiser) 116 : 2 parents and 3 kids.
2 iPads, 3 iPhones, some Samsung device, a Kindle and some other wifi device (a portable PC ?).The first two logins for user "116" work fine, a third one get authenticated (same user = "116" and password) but gets thrown out a couple of seconds during the REAUTHENTICATION process : the max user threshold was reached.
-
@Gertjan said in One Voucher Per Device:
@colleytech said in One Voucher Per Device:
whenever i do it with freeradius, two devices will connect, but a third device attempting to log in will always disconnect one of the already logged in devices
??
That's not my experience.The " Simultaneous-Use := 2 " statement will not allow a third login.
It doesn't kick out one of the two already logged in users.Example :
Room number (== uiser) 116 : 2 parents and 3 kids.
2 iPads, 3 iPhones, some Samsung device, a Kindle and some other wifi device (a portable PC ?).The first two logins for user "116" work fine, a third one get authenticated (same user = "116" and password) but gets thrown out a couple of seconds during the REAUTHENTICATION process : the max user threshold was reached.
@Gertjan i must be missing something,,,
i have restored the box to factory and setup captive portal fresh, with no concurrent checked, and Simultaneous-Use := 3 placed in the freeRad user, i can get just one user connected, other subsequent users disconnects the first user "not what i want"..............no concurrent unchecked and Simultaneous-Use := 3 placed in the freeRad user, i can log in with multiple devices, "not what i want"
applying your patch to select
1.many
2. only last
3. only first
and Simultaneous-Use := 3 placed in the freeRad user, doesnt still get the job done,,,,
what can i post here for you to check -
@colleytech said in One Voucher Per Device:
applying your patch to select
1.many
2. only last
3. only firstThat patch has nothing to do with FreeRadius.
@colleytech said in One Voucher Per Device:
her subsequent users disconnects the first user "not what i want"..............
I have to check things tomorrow, when I'm on site.
Look at my image = log again.
See (bottom) the oldest login. Just above (log is reverse) some OTHER 116 user is disconnected ... etc. -
That patch has nothing to do with FreeRadius.
@Gertjan maybe u didn't test the patch,, that patch overrides every setting, anything u apply on freeRadius doesnt reflect, as far as the patch is there.. the patch is so powerful
I have to check things tomorrow, when I'm on site.
Look at my image = log again.
See (bottom) the oldest login. Just above (log is reverse) some OTHER 116 user is disconnected ... etc.@Gertjan please do,, i wil be so grateful if i accomplish my goal
-
@Gertjan said in One Voucher Per Device:
I have to check things tomorrow, when I'm on site.
@Gertjan , any luck?
-
This post is deleted! -
@Gertjan said in One Voucher Per Device:
Captive portal users get message you are connected but there is no internet
I was trying to apply this patch and I'm getting below error:
Patch can NOT be applied cleanly (detail)
Patch can NOT be reverted cleanly (detail)I can apply the patch by editing the below files,
src/etc/inc/captiveportal.inc
src/etc/inc/system.inc
src/usr/local/captiveportal/index.phpbut I'm using your version of 'src/etc/inc/captiveportal.inc'
What is the solution for this?
Thanks in advance
-
@rayyanthameem said in One Voucher Per Device:
I was trying to apply this patch and I'm getting below error:
Patch can NOT be applied cleanly (detail)
Patch can NOT be reverted cleanly (detail)So :
@Gertjan said in One Voucher Per Device:
See the 'other' thread that handles that subject.
See also here : https://github.com/pfsense/pfsense/pull/4042 the solution is in feedback stage. The patch can be imported 'official' (again, see other other thread for details how to do so).This thread handles an entire other issue.
-
@Gertjan Thanks for your help, I hope this is the patch I've to apply: https://patch-diff.githubusercontent.com/raw/pfsense/pfsense/pull/4042.diff
-
@rayyanthameem said in One Voucher Per Device:
https://patch-diff.githubusercontent.com/raw/pfsense/pfsense/pull/4042.diff
That's the one.
As you noticed, the patch can't be applied against a 2.4.4-p3 on your device.
This is because the actual version of pfSense on github is more recent (like a 2.4.4-p4) then the version you have (2.4.4-p3).
So, first, you have to retrieve from github the most recent files for :
/etc/inc/captiveportal.inc
/usr/local/captiveportal/index.php
/etc/inc/system.incThen the patch can be applied.
I using it right now :
-
@Gertjan said in One Voucher Per Device:
Here we go:
This is the new /etc/inc/captiveportal.inc file:
https://pastebin.com/V6uWHNz5Now I am using your version of 'captiveportal.inc'
Are you suggesting except 'captiveportal.inc' use everything els and apply patch?
-
@rayyanthameem said in One Voucher Per Device:
Now I am using your version of 'captiveportal.inc'
That won't (probably) work with the 4042 patch.
The issue of this thread, the "One Voucher use" is something different.
Because I didn't publish a patch on github (== a pull request) there is only one way to make my patch work : you have to distil yourself the modifications out of the two files mentioned above (the pastbin ones).I made a case-study of the issue because it pops up often : limiting a voucher to ONE device.
A fact is : when some one proposes a patch against github, the patch should be supported by the author during the entire implementation time and test phase.
I'm not using vouchers myself .... and lack the time to support such an issue.
