Project

General

Profile

Actions

Bug #1317

closed

Voucher database synchronization

Added by Stefan baldus over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
Start date:
03/02/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

I have 2 pfsense, one in the DMZ and one in LAN.

The LAN manages the vouchers,
on the page -> status_captiveportal_test.php I did the test

LAN shows:
sjQKqhaQPY3 (1/16) good for 1440 Minutes
Access granted for 1440 Minutes in total.

DMZ shows:
sjQKqhaQPY3 (1/16) good for 1440 Minutes
Access granted for 1440 Minutes in total.

so far so good, but when I actually use the voucher over the pfsense in the DMZ I can see in the log:

DMZ
System log -> Captive Portal
logportalauth32176: Voucher login good for 1 min.: sjQKqhaQPY3, , ip_addr

log also shows this:
php: /index.php: CaptivePortalVoucherSync XMLRPC reload data success with http://LAN_IP_ADDR:8080:8080 (pfsense.exec_php).

My portal runs on 8080 (not 80) , I disabled https for now. Strange is, it shows the port nr twice. Not sure if this is just a log bug tho, as it seams to work correctly, except for the 1min duration instead of 1440.

any idear? The sync seams to work fine, but the time period seams odd to me. Also the user gets logged out after one minute, which is kinda to short of course

both boxes run the same Version

2.0-RC1 (i386)
built on Mon Feb 28 18:12:00 EST 2011

Actions #1

Updated by Stefan baldus over 13 years ago

Hi,

I think I found kinda relation between the duration of the voucher and the length of the ticket.

Looks like only the 1st digit is actually "active" in the end.

For example:

I create 3 vouchers:

200 min

300 min

400 min

and on the test page(status_captiveportal_test.php) it shows :

FqGkVaxLwZc (3/4) good for 400 Minutes

when a voucher is actullay used it shows in the system logs -> captive portal

Voucher login good for 4 min.: FqGkVaxLwZc,

Same with 300 min, and then its valid 3 min duration, 200 min -> 2min duration...

Maybe this helps a little
Stefanero

Actions #2

Updated by Stefan baldus over 13 years ago

Hello again,

just thought I let you know, this is still present in current snapshots.

regards
Stefanero

Actions #3

Updated by Chris Buechler over 13 years ago

  • Priority changed from High to Normal
  • Target version set to 2.0
Actions #4

Updated by Ermal Luçi over 13 years ago

  • Status changed from New to Feedback

Latest snapshot should have this ok now.

Actions #5

Updated by Stefan baldus over 13 years ago

Hi,

this can be closed. It is working now.

Thnx a lot
stefan

Actions #6

Updated by Chris Buechler over 13 years ago

  • Status changed from Feedback to Resolved

thanks

Actions

Also available in: Atom PDF