Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 39 subscribers
  • Views 2494 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

Communication between two zones not working

Jelle

We have a WAN connection which is controlled by our XG210 (PPPoE). This one is used for data transmission only. LAN to WAN works perfect.

Now we have switched our PBX to VoIP. To avoid QoS issues we set up a second WAN for our PBX with a Lancom 884 router. This connection is standalone and not controlled by XG, the PBX is in a seperate network. We are able to make and receive calls. So also this works perfect. So we have two seperate networks, LAN and PBX LAN.

Now we need to connect these two LANs for CTI. So I set up a new zone in our XG and connected the port to the Lancom router. For now the XG port got a DHCP address from the PBX LAN / Lancom router. Then I created a firewall rule which allows connections from LAN to PBX LAN, currently without host or service restrictions.

Unfortunaltely connections from LAN to PBX LAN don't work. Even a ping to the PBX LAN does not work. I don't see the reason for this. Can anybody give a hint what is wrong here?



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

    The policy test tells me everything is allowed. Looking at the log I can see succesful connections from PortE0 (LAN) to PortE1 (LAN PBX). Still it doesn't work.

    Could it be that this is related to the Lancom router acting as the gateway in the PBX LAN?

    Regards, Jelle

    Sophos XG210-HA (SFOS 18.0.4) on SG210 appliances with Sandstorm and 1x AP55
    Sophos Central with Intercept X Advanced, Device Encryption, Phish Threat, Mobile Control Advanced

    If a post solves your question use the 'This helped me' link.

  • +1 in reply to Jelle

    Adding the appropriate route in the Lancom router solved my problem. Sometimes it helps talking or in this case writing about the problem.

    Regards, Jelle

    Sophos XG210-HA (SFOS 18.0.4) on SG210 appliances with Sandstorm and 1x AP55
    Sophos Central with Intercept X Advanced, Device Encryption, Phish Threat, Mobile Control Advanced

    If a post solves your question use the 'This helped me' link.

  • 0 in reply to Jelle

    What was the route that you added?  I. Having a similar problem.

Reply Children
  • 0 in reply to K_K_S

    Hi,

    I had to tell the PBX router where to send packages for the normal LAN.

    Route:

    IP address of the LAN ending with .0, e.g. 192.168.1.0

    Appropriate mask, e.g. 255.255.255.0

    Router / gateway: IP address of LAN interface in PBX network, e.g. 192.168.2.10

    Regards, Jelle

    Sophos XG210-HA (SFOS 18.0.4) on SG210 appliances with Sandstorm and 1x AP55
    Sophos Central with Intercept X Advanced, Device Encryption, Phish Threat, Mobile Control Advanced

    If a post solves your question use the 'This helped me' link.

Unfiltered HTML