Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 2 subscribers
  • Views 9775 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ip masquerading

onats
Our ISP provided us 5 public IP addresses. We assigned 1 IP in the WAN interfaces and 4 IP as additional IP of the WAN link.

We are planning to allocate all of the public IP addresses such as:

192.168.100.1 - 192.168.100.5 | 1st public IP (assigned to WAN Interface Primary address) x.x.x.146


192.168.100.6 - 192.168.100.10 | 2nd public IP x.x.x.147


192.168.100.11 - 192.168.100.15 | 2nd public IP x.x.x.148


192.168.100.16 - 192.168.100.20 | 2nd public IP x.x.x.149


192.168.100.21 - 192.168.100.25 | 2nd public IP x.x.x.150



We've done it using Network Protection > NAT > IP Masquerading. However, the policy seems to be inconsistent. Initially it was working with the environment with 1 computer each group. However, when we put the configuration in production IP Masquerading policy was no longer effecting.

Please help.


This thread was automatically locked due to age.
Parents
  • 0
    Hi, Problem already resolved! Web requests was automatically translating the IP address. From the FW module, since the web requests came from webfilter, it translate the IP addresses to the primary IP address of WAN.
Reply
  • 0
    Hi, Problem already resolved! Web requests was automatically translating the IP address. From the FW module, since the web requests came from webfilter, it translate the IP addresses to the primary IP address of WAN.
Children
No Data