Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Sophos Firewall: v19.0 GA: Feedback and experiences

Parents
  • Picking up issues with NAT. I have multiple public IP's configured on a singe port all using the same Gateway which is the ISP's router. I need some outgoing traffic to come from a specific IP configure on the port.

    For this I used NAT rules and translated the source to the IP specific public IP address I want the traffic to come from. Since v19, traffic is now translated to the IP of my ISP's router, in other words, the gateway for the port.

Reply
  • Picking up issues with NAT. I have multiple public IP's configured on a singe port all using the same Gateway which is the ISP's router. I need some outgoing traffic to come from a specific IP configure on the port.

    For this I used NAT rules and translated the source to the IP specific public IP address I want the traffic to come from. Since v19, traffic is now translated to the IP of my ISP's router, in other words, the gateway for the port.

Children
  • Hi,

    please review linked Nat rules to see if they might be useful.

    ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • Sorry for the late reply. NAT issues have been on going for a long time in SFOS. I reported this back in the V16 days, but they never did anything about it. Every once in a while on upgrades of a few different clusters, some NAT rules would just stop processing. If you had custom NAT rules, the easiest fix is to just delete them, and recreate. I also specify interfaces in NAT rules and disable the default SNAT rule. It seems to help on upgrades.