Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iplog: Floored lease time for "tolerance" #1965

Closed
dwlfrth opened this issue Jan 19, 2017 · 0 comments · Fixed by #1968
Closed

iplog: Floored lease time for "tolerance" #1965

dwlfrth opened this issue Jan 19, 2017 · 0 comments · Fixed by #1968

Comments

@dwlfrth
Copy link
Contributor

dwlfrth commented Jan 19, 2017

When opening an iplog entry (either creating a new one or updating an existing one), PacketFence is using the actual lease time of a given DHCP lease (if provided) or set a NULL (which defaults to 0000-00-00 00:00:00) as the 'end_time' for the record.

It looks like more and more device "may not care" about the provided lease time or it may be some other reason, but the thing is, we are seeing more and more issues where "The device cannot be found in PacketFence database" when trying to reach the captive-portal, which is the result of the portal not being able to get an "open" iplog entry to do the IP <-> MAC lookup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant