Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 857 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

WOW HTTPS Inspection Could not associate packet to any connection.

QeLeMenU1
Hi community, 
Battle.net application and updater is fine with https inspection.
But with https inspection active the wow application itself the connection cannot be established.
followin web exceptions have been set.
([A-Za-z0-9.-]*\.)?blizzard\.vo\.llnwd\.net/
^([A-Za-z0-9.-]*\.)?akamaihd\.net/
^([A-Za-z0-9.-]*\.)?battle\.net/
^([A-Za-z0-9.-]*\.)?blizzard.com\.edgesuite\.net/
^([A-Za-z0-9.-]*\.)?blizzard\.com/
^([A-Za-z0-9.-]*\.)?blizzard\.vo\.llnwd\.net/
^([A-Za-z0-9.-]*\.)?blzmedia-a\.akamaihd\.net/
^([A-Za-z0-9.-]*\.)?worldofwarcraft\.com\.edgesuite\.net/
Best regards


This thread was automatically locked due to age.
  • 0
    Firewall
    2021-01-16 16:12:26
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    37.244.28.104
    57158
    80
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:26
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    178.79.221.45
    57159
    1119
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:26
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    37.244.28.104
    57158
    80
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:26
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    178.79.221.45
    57159
    1119
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:30
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    37.244.28.104
    57158
    80
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:28
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    37.244.28.104
    57158
    80
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:28
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    178.79.221.45
    57159
    1119
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:27
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    37.244.28.104
    57158
    80
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
    Firewall
    2021-01-16 16:12:27
    Invalid Traffic
    Denied
    N/A
    0
    192.168.1.20
    178.79.221.45
    57159
    1119
    TCP
    0
    01001
    Open PCAP
    Could not associate packet to any connection.
  • 0

    Hello,

    Are you currently on v17.5 or v18 ?

    If you're still on 17.5, I suggest you to upgrade to v18 MR4 and use the new DPI Engine instead of the Web Proxy.

    Thanks!

  • 0

    Do you use DPI Engine? 

    Because i guess, i figured out, what World of warcraft is doing.

    Before the initial logging request is started, it seems to connect to a IPaddress.

    After adding this IP to the local exclusion list, its working with the exceptions, you are using.

    Looking into Central Firewall reporting, using Intercept X on the endpoint, you can see, this requests are caused by blizzard: