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

How to handle IP addresses entered as RANGE #28

Open
chr1sn3al opened this issue Apr 12, 2023 · 3 comments
Open

How to handle IP addresses entered as RANGE #28

chr1sn3al opened this issue Apr 12, 2023 · 3 comments

Comments

@chr1sn3al
Copy link

image

So issue is.. When using Get-PHPIpamAddress there is no attribute to tell me that it's a range? so I that if I want via API to now break that down into individual addresses I need to remove the entry not just update..

Any thoughts?

@chr1sn3al
Copy link
Author

So appears to be somehow creating some of these as DHCP (Range) in the UI.. I can see from the API that there are different IpAddress records in the DB.. But the UI is showing as RANGE.. Very odd.. Not sure how the UI determines when they need to be a RANGE.

@chr1sn3al
Copy link
Author

These are from my Updates.. using the Update-PHPIpamAddress

@chr1sn3al
Copy link
Author

Found it.. (Wasn't API issue.. )_ It was the TAG "DHCP" was set to "compress range"
No idea why some records were compressed others were not.. But now it's fixed.

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

No branches or pull requests

1 participant