Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 5000 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

I can't access internal/external ports

Simon Klaus

I have a XGS Firewall in bridge mode behind a Uniif Dream Machine. Sadly the port forwarding rules don't work and i wanted to ask if someone maybe knows why. The XGS is in the 192.168.55.x LAN and the Unifi (my main LAN with all devices) is in the 192.168.77.x LAN. Both LAN's already have access to each other and i can open some web-gui's from devices, that use the standard port (http). But if i wanna open a web-gui that uses a different port then http/https like 5001, it doesnt work internal and it neither works external. Btw I've already did the forwarding rules and opened all ports that i need for my network.

  I've configured Sophos Firewalls before, but in bridge-mode this time, it doesnt really work out. 



This thread was automatically locked due to age.
Parents
  • +1

    You have a bridge mode but separate networks? 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    We've got a Unifi Dream Machine that is our main firewall with our main network. We got multiple VLAN's with multiple internal firewall rules configurated on the Unifi. The point of the Sophos Firwall is only to improve our security thats why we have our main Firewall (Unifi) -> Bridge Mode Firewall (Sophos) -> Main Switch. The Sophos Firewall's purpose is only to improve the security thats why it is in the Bridge mode and comes after our main Firewall. 

  • 0 in reply to Simon Klaus

    Bridge mode is not designed to route between networks. If you want to do routing, you have to enable routing. From looking at the WAN to LAN route, it does not look like the firewall has the routes provided to figure out where to go. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    It works now, had to define client ports for source/destination instead of 5001. But thanks for your time and help. 

Reply Children
No Data
Unfiltered HTML