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

IPv4 addresses can be assigned a status of SLAAC #5040

Closed
abrahamvegh opened this issue Aug 24, 2020 · 0 comments
Closed

IPv4 addresses can be assigned a status of SLAAC #5040

abrahamvegh opened this issue Aug 24, 2020 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@abrahamvegh
Copy link
Contributor

Environment

  • Python version: 3.7.3
  • NetBox version: 2.9.1

Steps to Reproduce

  1. Create a new IPv4 address e.g. 198.51.100.1/24
  2. Choose the ‘SLAAC’ status
  3. Save

Expected Behavior

The ‘SLAAC’ status should only be assignable to IPv6 addresses.

Observed Behavior

The status is accepted without error or warning.
@jeremystretch jeremystretch self-assigned this Aug 24, 2020
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Aug 24, 2020
@jeremystretch jeremystretch mentioned this issue Aug 27, 2020
Merged
delkyd pushed a commit to delkyd/netbox that referenced this issue Sep 25, 2020
@jeremystretch @delkyd
Fixes netbox-community#5040: Limit SLAAC status to IPv6 addresses
1830308
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abrahamvegh @jeremystretch