Error - logportalauth[11713]
-
Sometimes experiencing this error
logportalauth[11713]: CONCURRENT LOGIN - REUSING IP x.x.x.x WITH DIFFERENT MAC ADDRESS
and all cannot login using captive portal. Rebooting the system makes it back to normal operation.
Any idea what's causing it?Thank you. -
Usually that is from having your CP timeout longer than your DHCP lease timeout.
So someone else gets the same IP as a person who was logged on before.
So shorten the DHCP lease time, and/or lengthen the CP timeout.
-
I'm confuse
from having your CP timeout longer than your DHCP lease timeout.
solution
shorten the DHCP lease time, and/or lengthen the CP timeoutWhich is correct?
Thank you
Usually that is from having your CP timeout longer than your DHCP lease timeout.
So someone else gets the same IP as a person who was logged on before.
So shorten the DHCP lease time, and/or lengthen the CP timeout.
-
Either of those is OK so long as your lease time is longer than your CP timeout.
-
Either of those is OK so long as your lease time is longer than your CP timeout.
Thank you. I've already read this answer on your previous post
Attached is my current settings, that I get this error
-
Lifeform08: 2 remarks:
Add a time to Hard timeout (lets says: half the DHCP lease time). If users stay connected to the Wifi all the time they might as well active all the time. Today' devices never become really "inactive" ….
And that brings me to this question:
If the number of Wifi users is far more bigger then max the number of DHCP leases on the portal interface, IP's get recycled.
Are your portal users deconnected ? (Like this: http://www.test-domaine.fr/munin/dyndns.org/brithotelfumel.dyndns.org/index.html#portalusers ) -
Not all were disconnected, there are those that still can and have an internet connection, and there are cannot connect anymore stuck on the captive portal page.
