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

Static IP addresses not reserved in database #16

Open
ppacher opened this issue Jan 10, 2020 · 2 comments
Open

Static IP addresses not reserved in database #16

ppacher opened this issue Jan 10, 2020 · 2 comments
Assignees
Labels
bug Something isn't working plugin The issue is about a new plugin
Milestone

Comments

@ppacher
Copy link
Collaborator

ppacher commented Jan 10, 2020

The static plugin currently fails to add a lease/reservation for the IP address in the lease database. Under certain configurations this could become a problem as other plugins may try to lease the very same IP address to different clients.
The following configuration outlines the problem:

192.168.0.1/24 {
    # range will lease 192.168.0.10 to the first client however, that IP is actually reserved for
    # aa:bb:cc:dd:ee:ff
    range 192.168.0.10 192.168.0.20
    static aa:bb:cc:dd:ee:ff 192.168.0.10
}
@ppacher ppacher added bug Something isn't working plugin The issue is about a new plugin next Planned for v0.2 labels Jan 10, 2020
@ppacher ppacher self-assigned this Jan 10, 2020
@ppacher ppacher added this to the v0.5 milestone Jan 10, 2020
@ppacher ppacher removed the next Planned for v0.2 label Jan 10, 2020
@gaby
Copy link
Member

gaby commented Oct 15, 2021

@ppacher Any updates on this?

@ppacher
Copy link
Collaborator Author

ppacher commented Oct 17, 2021

Not yet - sorry. It's not a real issue if you can manage to have static leases not conflicting with dynamic ranges so I did't put much effort into this yet.

Though, I'll take care of it when I find some free time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working plugin The issue is about a new plugin
Projects
None yet
Development

No branches or pull requests

2 participants