<![CDATA[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.

]]>https://forum.netgate.com/topic/61978/error-logportalauth-11713RSS for NodeWed, 13 May 2026 00:20:57 GMTTue, 22 Oct 2013 09:58:58 GMT60<![CDATA[Reply to Error - logportalauth[11713] on Tue, 26 Nov 2013 01:35:54 GMT]]>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.

]]>https://forum.netgate.com/post/431471https://forum.netgate.com/post/431471Tue, 26 Nov 2013 01:35:54 GMT<![CDATA[Reply to Error - logportalauth[11713] on Fri, 08 Nov 2013 07:32:43 GMT]]>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 )

]]>https://forum.netgate.com/post/428707https://forum.netgate.com/post/428707Fri, 08 Nov 2013 07:32:43 GMT<![CDATA[Reply to Error - logportalauth[11713] on Thu, 07 Nov 2013 03:23:50 GMT]]>@jimp:

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

dhcp.png
dhcp.png_thumb
cp.png
cp.png_thumb

]]>https://forum.netgate.com/post/428467https://forum.netgate.com/post/428467Thu, 07 Nov 2013 03:23:50 GMT<![CDATA[Reply to Error - logportalauth[11713] on Tue, 05 Nov 2013 17:07:39 GMT]]>Either of those is OK so long as your lease time is longer than your CP timeout.

]]>https://forum.netgate.com/post/428157https://forum.netgate.com/post/428157Tue, 05 Nov 2013 17:07:39 GMT<![CDATA[Reply to Error - logportalauth[11713] on Tue, 05 Nov 2013 02:29:29 GMT]]>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 timeout

Which is correct?

Thank you

@jimp:

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.

]]>https://forum.netgate.com/post/428070https://forum.netgate.com/post/428070Tue, 05 Nov 2013 02:29:29 GMT<![CDATA[Reply to Error - logportalauth[11713] on Wed, 23 Oct 2013 13:51:48 GMT]]>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.

]]>https://forum.netgate.com/post/426360https://forum.netgate.com/post/426360Wed, 23 Oct 2013 13:51:48 GMT