You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After configuring a NAT'ed IP address, there is no indication in the IP address list that the address is NAT'ed or what the associated address or device is. It's also not included in the Export. I can set it "Active" and use the "Description" field but that only infers the information.
The only place to find the information is to drill all the way down to the address and view on the detail page which makes auditing cumbersome when there are more than a handful of addresses.
It would be helpful to display a column indicating either the NAT address, or perhaps even just a check mark that there is, in fact, a NAT address assigned. It would also be useful to see the address in the Export for auditing and reporting purposes. It would also be useful to have a search option for NAT'ed addresses ("Devices with NAT").
The text was updated successfully, but these errors were encountered:
Issue type: Feature Request
Python version: v2
NetBox version: 1.9.6
After configuring a NAT'ed IP address, there is no indication in the IP address list that the address is NAT'ed or what the associated address or device is. It's also not included in the Export. I can set it "Active" and use the "Description" field but that only infers the information.
The only place to find the information is to drill all the way down to the address and view on the detail page which makes auditing cumbersome when there are more than a handful of addresses.
It would be helpful to display a column indicating either the NAT address, or perhaps even just a check mark that there is, in fact, a NAT address assigned. It would also be useful to see the address in the Export for auditing and reporting purposes. It would also be useful to have a search option for NAT'ed addresses ("Devices with NAT").
The text was updated successfully, but these errors were encountered: