Outbound NAT - Source NAT Migration: Source NAT not considering Multi WAN?

[sorano]

I gave the source NAT migration a go.

I'm using Hybrid NAT and while the migration process in itself worked well I noticed that the Automatically generated rules under Source NAT does not consider creating rules for any additional WAN interfaces.

Please take a look at screenshots below to get a better picture of what I mean, Outbound_NAT has autogenerated rules for both WAN and WAN_Cellular:
You cannot view this attachment.

While Source NAT only has autogenerated rules for WAN:
You cannot view this attachment.

Edit: Forgot to mention that WAN_Cellular is assigned to a PPP interface.

[Monviech (Cedrik)]

What kind of ppp interface is WAN cellular? A pppoe interface?

https://github.com/opnsense/core/issues/10479

[sorano]

What kind of ppp interface is WAN cellular? A pppoe interface?

https://github.com/opnsense/core/issues/10479

It's configured as Link Type: "PPP" under Interfaces: Devices: Point-to-Point.

Should #10482 be appended with PPP aswell?

[Monviech (Cedrik)]

It's getting a little hard to keep the expectation in sync to the reality. I'm not sure yet we can add every case here since the backend decides this via runtime values.

What you see (In the automatic rules in SNAT) is just an approximation of the reality, the real rules (which are generated independent by the backend) can be seen via:

# pfctl -s nat

Not sure yet how to really display everything, but we probably have to postpone fixing more a little while or we chase each little edge case. We probably need some generic solution first.


Your most reliable fix is to create manual SNAT rules because those will ensure you always see and generate the full reality.