Skip to main content
Contributor III
October 1, 2006
Question

Howto NAT an internal SMTP server IP to outside!

  • October 1, 2006
  • 7 replies
  • 4094 views
I use a 50A with NAT Config and German DSL Connection. From my ISP i get an fixed IP 213.9.120.38 and a Subnet 213.9.58.128/29. I use a VIP to forward the SMTP traffic on 213.9.58.129 coming to my internal SMTP server on 192.168.1.3 (Static NAT with Portforwarding only on Port25). Works perfect. But when i send out emails the connecting IP is the 213.9.120.38. How should i create a Policy for translating the 192.168.1.3 to the 213.9.58.129 in the outgoing traffic?

    7 replies

    Contributor III
    October 1, 2006
    Have you checked NAT in outgoing rule?
    Contributor III
    October 2, 2006
    shure. but i have the problem, that whenever i create an outgoing rule with NATs the 192.168.1.3 to the 213.9.58.129 over VIP an IP-Adress conflict arises and my SMTP server detects another 192.168.1.3 Adress in the Net (because then an loopback seems to be createt) (the 192.168.1.3 is NATed to the 213.9.58.129 and back to the 192.168.1.3 but with the MAC of the external A50 Network). So i define the VIP with source 192.168.1.3, destination 0.0.0.0 and portforwarding on port 25 in the VIP. in the rule i define ALL services allow. But the rule is not shown in the Active Connections Status.
    rwpatterson
    New Member
    October 3, 2006
    You should use an IP pool. Create a single IP pool, and use that dynamic IP pool in the rule. This will show outbound traffic for this policy to be coming from the IP address in the pool. -Bob
    Contributor III
    October 3, 2006
    create an ip pool with only the ip need to be used as external for the mailsrv (213.9.58.129) than create a firewall rule specific for the mailsrv. SRC LAN/192.168... DST WAN/all ACT Accept SRV Any NAT / Ip pool ( the name of the ip pool you have created before and go...) bye
    Contributor III
    October 3, 2006
    tnx PMan, this does the job. tnx a lot!
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!