Remote clients checking in with NAT IP

Recently we turned our SMA public facing. However now when users are on the VPN and they check in their IP address shows them with an NAT IP of their home network. With this happening some of our Smart Labels have stopped to work correctly. If I view a device and then look under Network Interface I can see the different network connections and see the VPN listed with an IP. Any help would be great..

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Channeler 1 year ago
Red Belt

I believe you're talking about this:

You want the gateway IP (Public IP or VPN IP), instead of the device's LAN IP address.

Due to some major changes in 10.2, I believe this is working as designed, and requires users to modify the labels or create new ones. (in case they're using IP Range based labels).

If those are MySQL created labels, you will need to filter them like this:

If they're wizard created labels, you will need to go back to the Wizard.

Check this post's comments from July 2020:

Posted by: Hobbsy 1 year ago
Red Belt

If the VPN address is the same you can tell the SMA to ignore it. Go to Settings>general settings and scroll down to the section “ignore client IP address” and enter the VPN addresses in that box. The SMA should then ignore the IP and use the correct one

  • I did see others mention this but it has not worked. My vpn addresses go from i'd rather not list those out. I did try putting my NAT IP and then checked in the device. After doing that the asset showed the VPN IP address. - JC_Chi 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ