Guest User!

You are not Sophos Staff.

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

Masquerading NAT?

We have a block of 16 ipv4 public addresses.

Our network has various LANS and a couple of DMZ's.

Our main DMZ has 4 servers sitting within it, each with it's own public ip natting to it.

How do you set up masquerading for this? Is it simply:

DMZ Server A > WAN (public address A)

DMZ Server B > WAN (public address B)

DMZ Server C > WAN (public address C)  etc etc



This thread was automatically locked due to age.
  • I don't think you can count on ordering masq rules in WebAdmin.  If that were the developer's intent, I think the rules would have been numbered (an "ordered" list) - that's a basic thing in the WebAdmin "culture."  In other words, your suggestion might work in some cases, but not in others.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • In that case then why is it possible to adjust the "position" when editing Masq. rules?

    Also the online help says the following on masquerading:

    Position: The position number, defining the priority of the rule. Lower numbers have higher priority. Rules are matched in ascending order. Once a rule has matched, rules with a higher number will not be evaluated anymore.


    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

  • "rules with a higher number" - masq rules don't have numbers...

    Wait!  They do!  They're just not displayed.  I looked at an Edit of a Masq rule and there are numbers.

    I'm not sure when that was changed (it was in V9.2 in early 2014).  I never noticed it because I've always used SNATs for exceptions to the IP used for a particular subnet.  Now, I need to reevaluate that standard...

    This would let you stop using SNAT unless the port needs to change, making the list of NAT rules shorter and more consistent.  Those advantages would seem to outweigh the disadvantage of a longer list of masq rules.

    Position-sensitive masq rules rule!

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?