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

Webserver protection vs Firewall nat rules

I was only successful using the webserver protection option to setup an internal webserver with its own external static ip address. For some reason using various NAT rules/firewall rules I couldn't succeed. Very basic setup, is that the only way to setup webservers?

my example:  firewall external  ip address  xx.***.***.5
webserver via external:  xx.***.***.6
used dnat rules to take traffic from any, using http, to external (.6) change dest to internal webserver, service to http

also, noticed that using webserver protection doesn't create any firewall rules?


This thread was automatically locked due to age.
Parents
  • I guess I don't understand your original complaint/question.  Maybe #2 in Rulz addresses it? 

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • maybe this will explain it better. If I use webserver protection in the utm and setup the virtual webserver and the real webserver. I can communicate with my internal webserver through a static ipaddress/external DNS..everything works fine. If I don't use that option and try to use nat and firewall rules, I see the packets getting to the internal webserver from the outside but no return traffic
Reply
  • maybe this will explain it better. If I use webserver protection in the utm and setup the virtual webserver and the real webserver. I can communicate with my internal webserver through a static ipaddress/external DNS..everything works fine. If I don't use that option and try to use nat and firewall rules, I see the packets getting to the internal webserver from the outside but no return traffic
Children
No Data