# Source nat

**URL:** <https://community.a10networks.com/t/source-nat/586>\
**Category:** CGN - CGNAT & IPv6 Migration\
**Created:** [January 27, 2020, 6:23pm UTC](https://community.a10networks.com/t/source-nat/586 "2020-01-27T18:23:56Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 27, 2020, 6:23pm UTC](https://community.a10networks.com/t/source-nat/586/1 "2020-01-27T18:23:56Z")

</div>

We are setting up source NAT and the idea was to use the ve IP addresses for the associated vlan as the source NAT address in the pool.

I swear we had it setup like this in version 2.7.2P6. but since the upgrade it says we can not use the ve interface IP address as the source nat address in a pool.

Is there anyway of using the interface address as the source NAT now? Just trying to keep the number of IP addresses used down.

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 27, 2020, 8:14pm UTC](https://community.a10networks.com/t/source-nat/586/2 "2020-01-27T20:14:39Z")

</div>

Hello -  
This should be possible with “Smart NAT” which will use the interface IP or VRRP Floating IP. Per admin guide:  
Smart NAT provides source NAT for virtual ports. The IP addresses that Smart NAT uses to create the mappings depend on whether VRRP-A high availability is enabled and floating-IP addresses are configured:  
• With VRRP-A high availability – If VRRP-A high availability is configured, Smart NAT uses configured floating IP addresses as NAT addresses.  
• Without VRRP-A high availability – If VRRP-A high availability is not configured, then Smart NAT uses IP address(es) on the ACOS interface connected to the real server.  
The configuration is applied to the VPORT with “source nat auto” command.

Mike

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 28, 2020, 5:24am UTC](https://community.a10networks.com/t/source-nat/586/3 "2020-01-28T05:24:46Z")

</div>

my configuration is as below, kindly let me know what i am missing.  
!  
access-list 111 permit ip 10.0.0.0 0.255.255.255 any&nbsp;  
!  
access-list 111 permit ip 192.168.0.0 0.0.255.255 any&nbsp;  
!  
interface ethernet 2&nbsp;  
&nbsp;name “ISP 1”  
&nbsp;enable&nbsp;  
&nbsp;ip address 100.100.101.1 255.255.255.224&nbsp;  
&nbsp;ip nat outside&nbsp;  
&nbsp;exit-module  
!  
interface ethernet 3&nbsp;  
&nbsp;name “ISP 2”&nbsp;  
&nbsp;enable&nbsp;  
&nbsp;ip address 100.100.102.1 255.255.255.224&nbsp;  
&nbsp;ip nat outside&nbsp;  
&nbsp;exit-module  
!  
interface ethernet 4&nbsp;  
&nbsp;name “ISP 3”&nbsp;  
&nbsp;enable&nbsp;  
&nbsp;&nbsp;ip address 100.100.103.1 255.255.255.224&nbsp;  
&nbsp;ip nat outside&nbsp;  
&nbsp;exit-module  
!  
!  
ip nat pool SNAT\_ISP1 100.100.101.2 100.100.101.2 netmask /29 gateway 100.100.100.254&nbsp;  
!  
ip nat pool SNAT\_ISP2 100.100.102.2 100.100.102.2 netmask /29 gateway 100.100.100.253&nbsp;  
!  
ip nat pool SNAT\_ISP3 100.100.103.2 100.100.103.2 netmask /29 gateway 100.100.100.252&nbsp;  
!  
ip nat pool-group LLB2&nbsp;  
&nbsp;member SNAT\_ISP1 &nbsp;SNAT\_ISP2 SNAT\_ISP3  
&nbsp;exit-module

!  
slb virtual-server INTERNET 0.0.0.0 acl 111&nbsp;  
&nbsp;extended-stats&nbsp;  
&nbsp;port 0 tcp&nbsp;  
&nbsp;&nbsp;clientip-sticky-nat&nbsp;  
&nbsp;&nbsp;source-nat pool LLB2&nbsp;  
&nbsp;&nbsp;service-group IPV4\_0&nbsp;  
&nbsp;&nbsp;use-rcv-hop-for-resp&nbsp;  
&nbsp;&nbsp;template persist destination-ip dstpersist&nbsp;  
&nbsp;&nbsp;no-dest-nat&nbsp;  
&nbsp;&nbsp;exit-module  
&nbsp;port 0 udp&nbsp;  
&nbsp;&nbsp;clientip-sticky-nat&nbsp;  
&nbsp;&nbsp;source-nat pool LLB2&nbsp;  
&nbsp;&nbsp;service-group IPV4\_1&nbsp;  
&nbsp;&nbsp;use-rcv-hop-for-resp&nbsp;  
&nbsp;&nbsp;template persist destination-ip dstpersist&nbsp;  
&nbsp;&nbsp;no-dest-nat&nbsp;  
&nbsp;&nbsp;exit-module  
&nbsp;port 0 others&nbsp;  
&nbsp;&nbsp;clientip-sticky-nat&nbsp;  
&nbsp;&nbsp;source-nat pool LLB2&nbsp;  
&nbsp;&nbsp;service-group IPV4\_0&nbsp;  
&nbsp;&nbsp;use-rcv-hop-for-resp&nbsp;  
&nbsp;&nbsp;template persist destination-ip dstpersist&nbsp;  
&nbsp;&nbsp;no-dest-nat&nbsp;  
&nbsp;&nbsp;exit-module  
&nbsp;exit-module  
in the CLI when i ping 8.8.8.8 using source interface ethernet 2,3 and 4 i can ping 8.8.8.8  
but when i use source snap ip  
ping source 100.100.101.2 8.8.8.8 (no response)  
ping source 100.100.102.2 8.8.8.8 (no response)  
ping source 100.100.103.2 8.8.8.8 (no response)

Thanks,

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 28, 2020, 4:53pm UTC](https://community.a10networks.com/t/source-nat/586/4 "2020-01-28T16:53:42Z")

</div>

I don’t believe testing with a ping source IP of a NAT pool is a valid option. You may wish to execute that command while running axdebug to see what’s being sent / received.  
Overall, your config looks correct. I don’t see an “inside” interface configured, but I assume that’s planned. However, you need not configure inside / outside NAT interfaces unless you’re using “snat-on-vip”.

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 28, 2020, 4:58pm UTC](https://community.a10networks.com/t/source-nat/586/5 "2020-01-28T16:58:54Z")

</div>

users are unable to reach internet  
trace shows traffic is going to A10 after that \* \* \*

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 28, 2020, 5:00pm UTC](https://community.a10networks.com/t/source-nat/586/6 "2020-01-28T17:00:17Z")

</div>

All my ISP interface are access ports

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 28, 2020, 5:07pm UTC](https://community.a10networks.com/t/source-nat/586/7 "2020-01-28T17:07:19Z")

</div>

So it appears you’re looking to run NHLD. A few thoughts:  
Do you have “ip allow-promiscuous-vip” configured on your inside interface?  
Do your slb servers, service-groups, and VIP show UP status?  
Also, in my configs and also the admin guide, the NAT pools do not have a gateway defined. You may wish to try removing that.

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 28, 2020, 5:12pm UTC](https://community.a10networks.com/t/source-nat/586/8 "2020-01-28T17:12:35Z")

</div>

Yes ip allow-promiscuous-vip is enable on inside interface  
yes the status shows up  
can you share any config example please?

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 28, 2020, 7:47pm UTC](https://community.a10networks.com/t/source-nat/586/9 "2020-01-28T19:47:30Z")

</div>

Here’s a lab config I’ve used. In this instance, 192.168.1.x was inside, 10.x.x.x was outside.  
I do see in your config the following, which is incorrect syntax (at least in version 4.x). Pool group members should be one per line. What version are you running?

```yaml
ip nat pool-group LLB2 
 member SNAT_ISP1 SNAT_ISP2 SNAT_ISP3
 exit-module

```

[nhld\_lab.txt](https://community.a10networks.com/uploads/short-url/AkYrYfjF5gewEAuX5pH1eyAG7mB.txt) (2.21 KB)

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 28, 2020, 7:53pm UTC](https://community.a10networks.com/t/source-nat/586/10 "2020-01-28T19:53:59Z")

</div>

version 4.1.0-P7, build 10

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 29, 2020, 8:30am UTC](https://community.a10networks.com/t/source-nat/586/11 "2020-01-29T08:30:17Z")

</div>

still users traffic cannot browse internet

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 29, 2020, 5:00pm UTC](https://community.a10networks.com/t/source-nat/586/12 "2020-01-29T17:00:58Z")

</div>

At this point I would suggest packet captures to validate the behavior of the A10 and/or contacting A10 Support for assistance. Seems that there is some other environment specific issue at play here.

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 30, 2020, 11:09am UTC](https://community.a10networks.com/t/source-nat/586/13 "2020-01-30T11:09:45Z")

</div>

[axdebug\_file\_2020-01-29\_06-49-33.tar.gz](https://community.a10networks.com/uploads/short-url/jBvascMfuhpM4e5N3BmDUcLneue.gz) (60.6 KB)

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 30, 2020, 3:00pm UTC](https://community.a10networks.com/t/source-nat/586/14 "2020-01-30T15:00:53Z")

</div>

Reviewing the captures, it appears that all of your TCP SYN packets have the same 2 destination IP’s, and we never receive a SYN ACK from either of them. Also, I see no traffic with a destination port of 80 or 443.  
The IP’s do not align with the config you initially posted, so some of the context is lost.

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 30, 2020, 3:47pm UTC](https://community.a10networks.com/t/source-nat/586/15 "2020-01-30T15:47:12Z")

</div>

what could be a reason for not receiving SYN ACK?

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 30, 2020, 3:51pm UTC](https://community.a10networks.com/t/source-nat/586/16 "2020-01-30T15:51:38Z")

</div>

!Configuration last saved at 17:43:31 AST Thu Jan 30 2020  
!64-bit Advanced Core OS (ACOS) version 4.1.0-P7, build 10 (Oct-29-2016,00:54)  
!  
access-list 111 permit ip 10.0.0.0 0.255.255.255 any  
!  
access-list 111 permit ip 192.168.0.0 0.0.255.255 any  
!  
multi-config enable  
!  
terminal idle-timeout 60  
!  
ip dns primary 8.8.8.8  
!  
ip nat translation service-timeout udp 53 fast  
!  
vlan 2740  
&nbsp;untagged ethernet 1  
&nbsp;router-interface ve 2740  
interface management  
&nbsp;ip address 192.168.0.36 255.255.255.0  
&nbsp;ip default-gateway 192.168.0.254  
&nbsp;enable  
!  
interface ethernet 1  
&nbsp;name “STC Link2”  
&nbsp;enable  
!  
interface ethernet 2  
&nbsp;name “MOBILY Link2”  
&nbsp;enable  
&nbsp;ip address 86.51.170.35 255.255.255.224  
&nbsp;ip nat outside  
!  
interface ethernet 3  
&nbsp;name “KACST Link2”  
&nbsp;enable  
&nbsp;ip address 212.26.63.179 255.255.255.248  
&nbsp;ip nat outside  
!  
interface ethernet 4  
&nbsp;name “A10 LAN PRI”  
&nbsp;enable  
&nbsp;ip address 192.168.4.131 255.255.255.248  
&nbsp;ip nat inside  
!  
interface ethernet 5  
!  
interface ethernet 6  
!  
interface ethernet 7  
!  
interface ve 2740  
&nbsp;ip address 37.224.22.164 255.255.255.240  
!  
!  
ip nat pool SNAT\_KACST\_Link 212.26.63.180 212.26.63.180 netmask /29 gateway 212.26.63.177  
!  
ip nat pool SNAT\_POOL\_MOBILY 86.51.170.36 86.51.170.36 netmask /27 gateway 86.51.170.33  
!  
ip nat pool STC\_SNAT\_POOL 37.224.22.165 37.224.22.165 netmask /29 gateway 37.224.22.161  
!  
ip nat pool-group LLB2  
&nbsp;member SNAT\_KACST\_Link  
&nbsp;member SNAT\_POOL\_MOBILY  
&nbsp;member STC\_SNAT\_POOL  
!  
ip nat inside source static 192.168.4.133 37.224.22.172  
!  
!  
ip route 0.0.0.0 /0 37.224.22.161  
!  
ip route 10.1.52.0 /24 192.168.4.133  
!  
health monitor ping  
!  
slb template persist destination-ip dstpersist  
!  
slb template persist source-ip SRpersistent  
!  
slb template port KACST  
&nbsp;source-nat SNAT\_KACST\_Link  
!  
slb template port STC  
&nbsp;source-nat STC\_SNAT\_POOL  
!  
slb template port Mobily  
&nbsp;source-nat SNAT\_POOL\_MOBILY  
!  
slb server KACST\_Link 212.26.63.177  
&nbsp;health-check ping  
&nbsp;weight 2  
&nbsp;port 0 udp  
&nbsp;&nbsp;health-check-disable  
&nbsp;port 0 tcp  
&nbsp;&nbsp;health-check-disable  
!  
slb server MOBILY\_LINK 86.51.170.33  
&nbsp;health-check ping  
&nbsp;port 0 tcp  
&nbsp;&nbsp;health-check-disable  
&nbsp;port 0 udp  
&nbsp;&nbsp;health-check-disable  
!  
slb server STC\_Link 37.224.22.161  
&nbsp;health-check ping  
&nbsp;weight 3  
&nbsp;port 0 tcp  
&nbsp;&nbsp;health-check-disable  
&nbsp;port 0 udp  
&nbsp;&nbsp;health-check-disable  
!  
slb service-group IPV4\_0 tcp  
&nbsp;method weighted-least-connection  
&nbsp;health-check ping  
&nbsp;member KACST\_Link 0  
&nbsp;&nbsp;template KACST  
&nbsp;member MOBILY\_LINK 0  
&nbsp;&nbsp;template Mobily  
&nbsp;member STC\_Link 0  
&nbsp;&nbsp;template STC  
!  
slb service-group IPV4\_1 udp  
&nbsp;method weighted-least-connection  
&nbsp;health-check ping  
&nbsp;member KACST\_Link 0  
&nbsp;&nbsp;template KACST  
&nbsp;member MOBILY\_LINK 0  
&nbsp;&nbsp;template Mobily  
&nbsp;member STC\_Link 0  
&nbsp;&nbsp;template STC  
!  
slb virtual-server INTERNET 0.0.0.0 acl 111  
&nbsp;extended-stats  
&nbsp;port 0 tcp  
&nbsp;&nbsp;clientip-sticky-nat  
&nbsp;&nbsp;source-nat pool LLB2  
&nbsp;&nbsp;service-group IPV4\_0  
&nbsp;&nbsp;use-rcv-hop-for-resp  
&nbsp;&nbsp;template persist destination-ip dstpersist  
&nbsp;&nbsp;no-dest-nat  
&nbsp;port 0 udp  
&nbsp;&nbsp;clientip-sticky-nat  
&nbsp;&nbsp;source-nat pool LLB2  
&nbsp;&nbsp;service-group IPV4\_1  
&nbsp;&nbsp;use-rcv-hop-for-resp  
&nbsp;&nbsp;template persist destination-ip dstpersist  
&nbsp;&nbsp;no-dest-nat  
&nbsp;port 0 others  
&nbsp;&nbsp;clientip-sticky-nat  
&nbsp;&nbsp;source-nat pool LLB2  
&nbsp;&nbsp;service-group IPV4\_0  
&nbsp;&nbsp;use-rcv-hop-for-resp  
&nbsp;&nbsp;template persist destination-ip dstpersist  
&nbsp;&nbsp;no-dest-nat  
!  
end

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 30, 2020, 8:24pm UTC](https://community.a10networks.com/t/source-nat/586/17 "2020-01-30T20:24:06Z")

</div>

There are many possibilities for why the SYN ACK would not return. However, I think the bigger issue is that the A10 is not receiving any packets from either 10.0.0.0/8 or 192.168.0.0/16 networks. Do you have any hits on the ACLs?  
Is there a NAT before the A10 or some strange routing?

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [January 30, 2020, 8:55pm UTC](https://community.a10networks.com/t/source-nat/586/18 "2020-01-30T20:55:37Z")

</div>

A10 is the main device to do NAT  
there is no egde firewall  
How can i run debug in A10 or check acl hits?

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [January 30, 2020, 9:37pm UTC](https://community.a10networks.com/t/source-nat/586/19 "2020-01-30T21:37:12Z")

</div>

ACL hits: show access-list  
Debugging: axdebug  
I would suggest using the “?” within axdebug to see the commands for filters etc.

---

<div class="post-metadata">

**Author:** ![salman210](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@salman210](https://community.a10networks.com/u/salman210)\
**Post date:** [February 2, 2020, 2:24pm UTC](https://community.a10networks.com/t/source-nat/586/20 "2020-02-02T14:24:49Z")

</div>

SRC-PRI-A10-Active#sh access-list  
access-list 111 4 permit ip 10.0.0.0 0.255.255.255 any Data plane hits: 0  
access-list 111 8 permit ip 192.168.0.0 0.0.255.255 any Data plane hits: 0

[Next page](https://community.a10networks.com/t/source-nat/586.md?page=2)
