Static-NAT update #642
Static-NAT update #642
Conversation
docs/config_nat.md
Outdated
| @@ -106,6 +106,29 @@ exit | |||
|
|
|||
| ``` | |||
|
|
|||
| ### Non-SVR Traffic | |||
|
|
|||
| The `ingress-source-nat-pool` and the `source-nat` settings of `bidirectional-nat` are both `ingress source-nat` that are intended for SVR traffic targeted towards an inter-router peer. In this situation, the NAT will be applied on the ingress router rather than the final egress router. | |||
There was a problem hiding this comment.
I had to read the first sentence four times and I still don't think I grok it. This statement needs to be changed for readability.
Additionally, ingress-source-nat-pool is being referenced for the first time here. Definitions would help.
There was a problem hiding this comment.
@MichaelBaj below is the "annotation" for the first sentence.
Depending on when and where a packet gets source NAT'd, there are two types of source NAT - ingress and egress.
The
bidirectional-natconfig is in the form oflocal-ipandremote-ippair.
- source-nat (local-ip -> remote-ip) is performed for packet ingressing the interface where
bidirectional-natis configured.- dest-nat (remote-ip -> local-ip) is performed for packet egressing the interface where
bidirectional-natis configured.In this sense, along with
ingress-source-nat-pool, thesource-natpart ofbidirectional-natfalls into the ingress source-nat category and will be handled accordingly.
docs/config_nat.md
Outdated
|
|
||
| The `ingress-source-nat-pool` and the `source-nat` settings of `bidirectional-nat` are both `ingress source-nat` that are intended for SVR traffic targeted towards an inter-router peer. In this situation, the NAT will be applied on the ingress router rather than the final egress router. | ||
|
|
||
| If you want to configure `ingress source-nat` for non-SVR traffic, for example LAN-to-LAN traffic traversing a single SSR router, you can use the configuration above. However, you must also disable `egress source-nat` at the service level by setting `service->source-nat` to `disabled` as shown below: |
There was a problem hiding this comment.
convention for referencing config path is to use a single right angle bracket between objects. e.g.
service > source-nat
Static-NAT update for non-svr traffic, per note from Chao