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

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

Sophos XG Home edition and Battle.net

Moved to Sophos XG from a Fortigate, all seems to work OK but the battle.net client. It won't connect. Disbaled SSL inspection, no change. Created a new rule for the PC, disabled all inspection, IPS and the like and put rule at top, issue still remains.

I see in the logs it hitting the rule, so it's using it.

Change my gateway to old Fortigate IP and battle.net client connects.

It's something on Sophos, but logs look OK, and allow all traffic.....any thoughts?



This thread was automatically locked due to age.
Parents
  • the neverending story with sophos generally.

    horror with microsoft exceptions, also many other programms.

    for blizzard / battlenet I have the following urls in exceptions configured:

    ^([a-zA-Z0-9.-]*\.)?origin-[A-Za-z]\.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?eaassets([0-9])*-[A-Za-z]\.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?blizzard\.com/

    ^([a-zA-Z0-9.-]*\.)?blzddist1-a.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?battle\.net/

Reply
  • the neverending story with sophos generally.

    horror with microsoft exceptions, also many other programms.

    for blizzard / battlenet I have the following urls in exceptions configured:

    ^([a-zA-Z0-9.-]*\.)?origin-[A-Za-z]\.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?eaassets([0-9])*-[A-Za-z]\.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?blizzard\.com/

    ^([a-zA-Z0-9.-]*\.)?blzddist1-a.akamaihd\.net/

    ^([a-zA-Z0-9.-]*\.)?battle\.net/

Children