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

Correct instructions for setting up basic port forwarding on XG v16.x

Creating port forwarding policy or rule on XG 16x.

 

I tried to post this to the forum but looks like it did not post. If this is a duplicate post let me know so I can remove it assuming the original one is there.

 

Want to create a simple step by step port forward instruction and rule. Right now want to port forward port 443 to a server behind XG.

1. Any Internet host can access server on 443 behind XG by the domain name example.net

2. My internal LAN computers can also access the internal server by it’s external domain name example.net on port 443.

 

I have read many posts on the port forward and access internal by it’s FQDN.

 

These are my instructions and they do not work. Please help correct and spot errors.

Else it is a matter of time before I find a Sophos reseller / support company and pay the I image between $100 to $200 to have them remote in and configure my rules or tell me over the phone how to do it. Either way I think if I can get a working basic simple step by step port forward set of instructions posted to the forum, it might help many others review my steps and them make simple edits for their ports and servers behind XG. So this is my attempt at getting that done.

 

1. Log in with admin read write access.

2. Under Protect section on the left side, click on the Firewall.

3. at the right, click on the blue box Add Firewall Rule

4. next click on either user/network rule or Business Application Rule.

5. in my case we are clicking on the Business Application Rule choice.

6. Select Business App Rule

7. Select Template – in this case I selected the DNAT / Full NAT / Load Balance

8. Give the rule a name – port 443 forwarding

9. Put a description in

10. under Source Section.

A. Source Zones = LAN

b. Allowed Client Networks = Any

c. Blocked Client Networks = left blank / empty

11. under Destination & Services section

A. Destination Host Network = WAN Interface / IP address

B. Forward type = port

C. Service port(s) = 443 TCP (or select desired port and TCP or UDP)

12. Forward to section

A. protected Server(s) = select your server(s) if you created host objects for them, select it / them.

B. Mapped type = port

C. Mapped port = 443

D. Protected Zone = LAN

13. Advanced Section

A. Intrusion Prevention = WAN to LAN

B. Traffic Shaping = NONE

C. Synchronized Security = No Restriction

D. Minimum Destination HB Permitted = no restriction

E. Routing – check the box allow rewrite source address (MASQ)

MASQ[Interface to Default I.P.]

if desired select Log firewall traffic

This rule is not working for me. Anyone spot the error or issue in the above instructions?

Under Diagnostics, I can ping the example.net domain and it pings and reports back the correct Internet WAN I.P. as seen on the AT&T DSL Modem / router. All ports in question are being port forwarded on the AT&T modem to the XG WAN port.

Also with NS lookup under the Diags tools, I can resolve example.net domain name to the correct I.P. as well. Web server is up and running fine since from LAN I can access it by LAN I.P. directly. But can not access by external name from LAN client machines and not able to access from cell phone from Internet to it. So I assume I am missing a setting or have some things wrong.

 

So I first need to know if I have the port forwarding set up correctly first. Then I can figure out what log to go look at after that if things are not yet working.

 

Chad



This thread was automatically locked due to age.
Parents
  • Try:

    10A. Source Zones = WAN

    13A. Intrusion Prevention = I'd start of with no IPS on portmap

    13E. Routing – Better NOT use MASQ (If you do, internal host will see all connections being sourced from XG LAN IP)

  •  

    Hello,

     

    I did try:

    10A. Source Zones = WAN

    13A. Intrusion Prevention = I'd start of with no IPS on portmap - none selected

    13E. Routing – Better NOT use MASQ (If you do, internal host will see all connections being sourced from XG LAN IP) - box not checked.

     

    and no luck.

    I made two rules one for the web port 443 and one for port 80. I have been testing on port 80, since I have two firewalls and the AT&T modem is port forwarding 443 to the Linksys firewall router that I normally keep the web server VM on. Then port 80 is sent to the Sophos XG on the AT&T modem router. I have this setup to make easy testing. I just move the server between the two to test port 80 and 443, if I get port 80 rule working I just change it to the same on the 443 rule.

     

    Any other suggestions by anyone from anyone I can try?

     

    I have several goal I want to learn and configure with my XG, but getting the port forward rules working is number one, then the HTML VPN and user portal features, then just make sure my virus / malware / unified threat settings are set to try to catch any and all threats that it can.

    (My next thought is to fire up another XG VM and set it up for bridge mode and hope it just scans the packets for malware / viruses and other threat detection and let the Linksys do the port forward. Then wait for XG17, from what I read about Ver 17 of XG  " NAT Business rule improvements - Object based, more familiar to UTM9 users, more powerful"

Reply
  •  

    Hello,

     

    I did try:

    10A. Source Zones = WAN

    13A. Intrusion Prevention = I'd start of with no IPS on portmap - none selected

    13E. Routing – Better NOT use MASQ (If you do, internal host will see all connections being sourced from XG LAN IP) - box not checked.

     

    and no luck.

    I made two rules one for the web port 443 and one for port 80. I have been testing on port 80, since I have two firewalls and the AT&T modem is port forwarding 443 to the Linksys firewall router that I normally keep the web server VM on. Then port 80 is sent to the Sophos XG on the AT&T modem router. I have this setup to make easy testing. I just move the server between the two to test port 80 and 443, if I get port 80 rule working I just change it to the same on the 443 rule.

     

    Any other suggestions by anyone from anyone I can try?

     

    I have several goal I want to learn and configure with my XG, but getting the port forward rules working is number one, then the HTML VPN and user portal features, then just make sure my virus / malware / unified threat settings are set to try to catch any and all threats that it can.

    (My next thought is to fire up another XG VM and set it up for bridge mode and hope it just scans the packets for malware / viruses and other threat detection and let the Linksys do the port forward. Then wait for XG17, from what I read about Ver 17 of XG  " NAT Business rule improvements - Object based, more familiar to UTM9 users, more powerful"

Children
No Data