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
The ServiceObject model should allow for both source and destination ports or have a direction identifier.
Use Case
Every firewall I've worked with defines a Service as including both source and destination ports. This creates problems when mapping from and to firewall vendors as Nautobot ServiceObjects are ambiguous in their definition.
With my understanding of the current implementation, I would need to create multiple ServiceObjects and distinguish them by name.
The text was updated successfully, but these errors were encountered:
Environment
Proposed Functionality
The ServiceObject model should allow for both source and destination ports or have a direction identifier.
Use Case
Every firewall I've worked with defines a Service as including both source and destination ports. This creates problems when mapping from and to firewall vendors as Nautobot ServiceObjects are ambiguous in their definition.
With my understanding of the current implementation, I would need to create multiple ServiceObjects and distinguish them by name.
The text was updated successfully, but these errors were encountered: