Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 28 subscribers
  • Views 8714 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

Port Forward, tried everything, need help

l0rdraiden

 

Why the host subnet is 255.255.255.255? I can't change it and I am using 255.255.255.0, it's fine? does it matter?

I get an error when I check the port here and the app being forwarded doesnt' work well.

https://www.yougetsignal.com/tools/open-ports/ 



This thread was automatically locked due to age.
Parents
  • 0

    On first glance, you do not seem to have mapped your ports in the FW rule. I've not setup any forwarding rules in XG yest, but 99.99% of all the other firewalls I've worked with require you to define 1) the port(s) the FW will accept request on and 2) the port(s) on the destination/protected server that it forwards to.  On the XG FW rule page, that would be the "mapped port" section just to the right of the Protected Server(s) selection.

  • 0 in reply to Gary Parr

    Thanks for the answer, I tried but I can't change or type anything in those fields. Maybe is a bug or is the way it works, maybe someone can confirm it.

     

    Do I have to enable masquerading?

  • 0 in reply to l0rdraiden

    Hi,

    yes you will need MASQ or change destination port.

    Also your rule is being override by your higher rules. Change any source to LAN on your higher rules. In fact disable rule 1, it is not providing ant benefit at this stage until you work through all your internet access requirements. Then setup rules for each type of access.

    Ian

  • 0 in reply to rfcat_vk

    Like this? in the forwarding rule?

     

     

    Ok, I have notice something weird, It works with a port number but not with other port number, the rules are exactly the same except the port number, why this could be?

Reply Children
No Data