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

Issue with uplink balancing and Sophos Wifi AP

Hello everyone,

we have two SG330 appliances (clustered) with UTM 9.705-3 and we use internet uplink balancing with two ISPs connected to the UTM cluster (both with fixed IP addresses). Also we have a couple of Sophos Wifi APs (AP55) that provide multiple Wifi SSIDs/Networks for different purposes.

Everything works fine with all attached devices and "local" networks, expect that we are not able to route traffic coming from the Sophos Wifi APs connected to the SG-Cluster through the secondary ISP/Interface. Whichever multipath rule we apply (or don't), the wifi clients are not able to get internet access when secondary ISP is chosen either by load balancing automatically or via a dedicated MP rule. On all "LAN" connected networks load balancing and even dedicated MP rules pointing to the secondary interface/ISP are working.

Where should I start troubleshooting? 

Best regards

 Jens 



This thread was automatically locked due to age.
Parents
  • Hallo Jens,

    then please show us your detailed definitions in "Uplink balancing" and "Multipath rules"

    Has your masquerading been modified after setting up the second ISP-Uplink?

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

Reply
  • Hallo Jens,

    then please show us your detailed definitions in "Uplink balancing" and "Multipath rules"

    Has your masquerading been modified after setting up the second ISP-Uplink?

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

Children
  • Hello Philipp,

    thank you for your answer! Masquerading was obviously what I was overlooking, it seems that someone in the past configured masquerading explicitly for the Wifi networks only to work with ISP 1. Im sure this wasn't always the case, but we have had a network outage some time ago and I assume it happened back there. 

    Best regards

    Jens