3rd Party Ipsec, NAT, and Azure VWAN

[Netwow]

There are 70 + sites in an organization . There is a 3rd party tunnel to a vendor. Some of the IP ranges overlap with the vendors other client's tunnel . They have asked us to NAT. Each 1 of the sites has a /24 subnet. The NAT they want to provide us with is a /27. We know the limitations of the MX and Nat so we have built a VWAN hub in Azure with all sites connected and the 3rd party vender. This still requires a 1 to 1 Nat however the vendor is not willing to provide a larger NATTd subnet . Has anyone ever experienced a similar issue and if so how did you resolve it, short of putting an MX at the vendor's site?

[PhilipDAth · Accepted solution]

I've used an Unbuntu VM.  NATed the entire source network to a single IP address in the new network.  Basically, you set it up Ubuntu like you are accessing the Internet, but rather than being NATed to a single public IP, it is NATed to a single IP in the remote network.