Assigning IP to devices and interfaces in v3.5.1 #12577
Replies: 2 comments 3 replies
-
The new interface allows to define additional filters compared to the previous system and to apply filter on different properties rather than only the device name. |
Beta Was this translation helpful? Give feedback.
-
Dear developers, Can you please do something with this issue? The assignment of IP adresses to devices is very difficult compared to how it was in earlier versions. It would be very useful to have tenant and device fields in the "Interface Assignment" of an IP Address, which filters each following field, so there are limited interfaces left. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Having just upgraded to v3.5.1, I've just noticed that the assignment section has been modified and now only shows the Interfaces entry box. In previous versions, there was first a Device (or Virtual Machine) box which would filter based on device to then list only the interfaces present on that device / VM.
Now, that first level filter is gone.
It looks like I can bring up a filter selection tool by clicking on the icon to the right, but it seems strange to have to do this. But with the current method of operation, this seems mandatory: I have like 100 "Gigabit Ethernet 0/1" interfaces with no indication which device each one belongs so it's totally useless having just the "Interface" box to select from.
Is this by design and I'm missing a trick or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions