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.

Sign up for GitHub

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

Jump to bottom

Display correct maximal MAC address update time #474

Merged
merged 1 commit into from
Oct 30, 2023
Merged

Display correct maximal MAC address update time #474

merged 1 commit into from
Oct 30, 2023

Conversation

FestplattenSchnitzel
Copy link
Member

No description provided.

@lukasjuhrich
Copy link
Collaborator

Regardless of whether it's 15 minutes or 10 minutes or something similar, this is a much more accurate bound and can be merged. Let's not get nitpicky here.

Times that matter in this case are:

  • time until hades discovers something changed (hades-refresh runs once per minute, hades-forced-refresh every five minutes)
  • reauth period on the switch (communicated by radius attribute)
  • length of DHCP lease the client holds (configured in the Hades dnsmasq instances i think?)

(alle Angaben ohne Gewähr)

@FestplattenSchnitzel FestplattenSchnitzel merged commit 1709179 into develop Oct 30, 2023
7 checks passed
@FestplattenSchnitzel FestplattenSchnitzel deleted the mac_update_time branch October 30, 2023 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lukasjuhrich lukasjuhrich lukasjuhrich approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@FestplattenSchnitzel @lukasjuhrich