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

Issues with Battle.Net Services

I'm currently running Sophos UTM 9 (9.408-4) and it's been working great except for some recent issues with battle.net services.

A few months ago Blizzard changed their in game voice service and I can no longer connect to it. Digging through the logs it seems like it's SIP related but I can't seem to make heads or tails of where it's being blocked. In the last week the launcher has also been failing to connect to my friends list but I can sign in and play games but I haven't made any changes.

Everything else is working fine including other chat clients like Discord, Mumble, Teamspeak, etc.

I've tried narrowing it down to a specific Sophos service that's blocking but it doesn't seem to matter what I turn on or off or if I add my desktop to the bypass group.
Worse I don't see anything interesting in any of the logs to help me debug this.

At this point I'm super confused and not sure how to troubleshoot this. I realize there isn't much info to go on but I was wondering if anyone has any ideas?

Thanks.



This thread was automatically locked due to age.
  • Which version are you on? I'm currently at 9.409-9.

    For what it's worth I don't have any NAT rules specifically configured to send traffic to my gaming machine.

  • The same.  9.409-9. 

    Not sure how to proceed at this point... may have to go back to PFSense.  Sophos is a better product in almost every way, but this is a long-term dealbreaker.  The inconsistency is problematic... if it wasn't working for anyone (or didn't work in repeatable firewall configurations) then that would be one thing, but having two different outcomes from the same version / configuration is tough.

    I've even enabled ICMP response, as I see an ICMP packet coming back from the Blizzard SIP/Voice server, but no change. 

    I *am* seeing a burst of STUN packets coming back from the Blizzard SIP server right after the request that get dropped.  Not very familiar with that protocol, so I need to do some quick research.