Outbound NAT not translating over IPSec

NAT
Log in to reply
  • W

    @hoba:

    This is not doable through the gui currently (not sure if it's doable at all).

    Does this mean that an Outbound NAT rule will not apply over IPSec VPN?

    We're attempting to translate the Source IP 10.10.70.x to a specific Source IP of 10.10.60.120 so that the remote side [of the VPN] would see traffic coming from 10.10.60.120 instead of 10.10.70.x.  So far, our tests show that the NAT Translation is not carrying over to the remote side.  Pings still show coming from 10.10.70.x.
    I thought that there could be a XML command that could assist, but have not found one yet.

    <nat><ipsecpassthru><advancedoutbound><rule><source>
    <network>10.10.70.0/24</network>

    <sourceport><descr><target>10.10.60.120</target>
    <interface>lan</interface>
    <destination><address>172.16.0.0/23</address></destination>
    <natport></natport></descr></sourceport></rule>
    <enable></enable></advancedoutbound></ipsecpassthru></nat>

    0

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

© 2021 Rubicon Communications, LLC | Privacy Policy