Problems Captive Portal Idle timeout Pfsense 2.1.3
-
Using the value in Captive Portal idle timeout greater 60 minutes, connection does not expire.
Tested with 70 to 120 minutes, but does not expire. Notebook Client shut down to prevent connection attempt.
Disable MAC filtering parameter checked.
Using Captive Portal Integrated Freeradius (Base Openldap)
-
Hi there.
@gilmarcabral:….
Disable MAC filtering parameter checked.
Using Captive Portal Integrated Freeradius (Base Openldap)When you did so, this applies:
If this option is set, no attempts will be made to ensure that the MAC address of clients stays the same while they're logged in.This is required when the MAC address of the client cannot be determined (usually because there are routers between pfSense and the clients). If this is enabled, RADIUS MAC authentication cannot be used.
pfSense should see the MAC of the client, this will give you the best situation where the 'time out' will work.
Its also stated that RADIUS really would like to see and use the client's MAC.So, is it true that your pfSense box doesn't see the client's MAC address ?
If so, do whatever is possible to remove the 'router' after 'router' situation.
Remove that router, or reprogram your access point.Test also for a short moment with 'local' users (the ones you can declare with pfSense).
Does the time-out then work ? Mine does: http://www.papy-team.org/munin/dyndns.org/brithotelfumel.dyndns.org/portalusers.html
This test might show you where your problem originates.
-
captive portal receives acress mac notebook
-
Why are you mentionning a notebook ?
-
autenticate Notebook Captive Portal.
-
Problem is related to time Last Activity as print attached.
Login as 07:46:12 and presented logout but time was 12:06:19 Activity
-
With my current time zone(gmt -3), session last activity is almost 5 hours ahead.
so I've tried to set my timezone to london (gmt 0) and for my surprise, last activity is earlier then start time.
