# Send pritunl source NAT method to SNAT instead MASQ

**URL:** <https://forum.pritunl.com/t/send-pritunl-source-nat-method-to-snat-instead-masq/1055>\
**Category:** Pritunl VPN\
**Created:** [May 22, 2023, 3:11pm UTC](https://forum.pritunl.com/t/send-pritunl-source-nat-method-to-snat-instead-masq/1055 "2023-05-22T15:11:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![roland.schmidt](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/r/a9adbd/32.png) [@roland.schmidt](https://forum.pritunl.com/u/roland.schmidt)\
**Post date:** [May 22, 2023, 3:11pm UTC](https://forum.pritunl.com/t/send-pritunl-source-nat-method-to-snat-instead-masq/1055/1 "2023-05-22T15:11:57Z")

</div>

Hi,

For pritunl VPN would be nice to use SNAT with --to-source instead of MASQUERADE  
It has a much granular control on source NAT outbound IP  
For example I would like to use IPs from same network as alias IPs on same interface as different outbound SNAT IPs which is not possible with MASQ which requires different interfaces (no interface alias like eth0:1)  
Using IPs from same network on different interfaces is not a solution on linux.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [May 22, 2023, 3:36pm UTC](https://forum.pritunl.com/t/send-pritunl-source-nat-method-to-snat-instead-masq/1055/2 "2023-05-22T15:36:04Z")

</div>

This option may be added in the future.

---

<div class="post-metadata">

**Author:** ![davisonja](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/d/ecc23a/32.png) [@davisonja](https://forum.pritunl.com/u/davisonja)\
**Post date:** [July 25, 2025, 11:22am UTC](https://forum.pritunl.com/t/send-pritunl-source-nat-method-to-snat-instead-masq/1055/3 "2025-07-25T11:22:48Z")

</div>

I’d also be keen for this functionality; we’re looking to have a distinct outbound source IP for each VPN under linux. Currently working around the lack of support for this with custom iptables rules, but it’s not ideal.
