[OVN] SNAT only happens for subnets directly connected to a router
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
High
|
Brian Haley | ||
neutron (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am trying to achieve the following scenario:
I have a VM attached to a router w/o external gateway (called project-router) but with a default route which send all the traffic to another router (transit router) which has an external gateway with snat enabled and it is connected to a transit network 192.168.100.0/24
My VM is on 172.16.100.0/24, traffic hits the project-router thanks to the default route gets redirected to the transit-router correctly, here it gets into the external gateway but w/o being snat.
This is because in ovn I see that SNAT on this router is only enabled for logical ip in 192.168.100.0/24 which is the subnet directly connected to the router
# ovn-nbctl lr-nat-list neutron-
TYPE EXTERNAL_IP EXTERNAL_PORT LOGICAL_IP EXTERNAL_MAC LOGICAL_PORT
snat 147.22.16.207 192.168.100.0/24
But I would like that this router snat all the traffic that hits it, even when coming from a subnet not directly connected to it.
I can achieve this by setting in ovn the snat for 0.0.0.0/0
# ovn-nbctl lr-nat-add neutron-
# ovn-nbctl lr-nat-list neutron-
TYPE EXTERNAL_IP EXTERNAL_PORT LOGICAL_IP EXTERNAL_MAC LOGICAL_PORT
snat 147.22.16.207 0.0.0.0/0
snat 147.22.16.207 192.168.100.0/24
But this workaround can be wiped if I run the neutron-
Is there a way to achieve this via OpenStack? If not does it make sense to have this as a new feature?
description: | updated |
summary: |
- [OVN] SNAT only happens for subnets directly connected to the router + [OVN] SNAT only happens for subnets directly connected to a router |
tags: | added: ovn |
Same scenario described on the bug works out of the box on an OpenStack environment using ML2/OVS instead of OVN