Skip to content

Fix: NAT is always configured on sdwan_transport_wan_vpn_interface_ethernet_feature #488

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

Merged
merged 6 commits into from
Aug 8, 2025

Conversation

rchrabas
Copy link
Collaborator

Description

Fix issue, where NAT is always configured on sdwan_transport_wan_vpn_interface_ethernet_feature

Issue #485

Types of Changes

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Build/CI change
  • Code quality improvement/refactoring/documentation (no functional changes)

Checklist

  • My code follows the code style of this project
  • N/A I have added tests to cover my changes
  • All new and existing tests pass locally

@rchrabas rchrabas linked an issue Jul 29, 2025 that may be closed by this pull request
@rchrabas rchrabas requested a review from tzarski0 July 31, 2025 07:26
Copy link
Collaborator

@tzarski0 tzarski0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this doesn't fix the problem. In the API payload, we have two blocks of configuration:

            "nat":
            {
                "optionType": "default",
                "value": false
            },
            "natAttributesIpv4":
            {
                "natType":
                {
                    "optionType": "default",
                    "value": "interface"
                },
                "udpTimeout":
                {
                    "optionType": "default",
                    "value": 1
                },
                "tcpTimeout":
                {
                    "optionType": "default",
                    "value": 60
                },
                "newStaticNat":
                []
            },

The nat field should always be present. The natAttributesIpv4 should be present only if nat.value is true. Similar fix needed for natAttributesIpv6.

@rchrabas rchrabas requested a review from tzarski0 August 8, 2025 08:57
@tzarski0
Copy link
Collaborator

tzarski0 commented Aug 8, 2025

@rchrabas looks better now. Could you please resolve conflicts?

@rchrabas
Copy link
Collaborator Author

rchrabas commented Aug 8, 2025

@tzarski0 done

@danischm danischm merged commit b09b668 into CiscoDevNet:main Aug 8, 2025
1 check failed
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

Successfully merging this pull request may close these issues.

[UX 2.0] NAT is always configured for transport interface
3 participants