SummaryWhen trying to run Guild Wars 2 on a network, the traffic might be seen as classified as other objects, which could impact running the game.
OverviewWhen running Guild Wars 2 (a Massively Multiplayer Online game for the PC), it is possible that users will experience lag or drops from the game due to how the Exinda is behaving.
In ExOS versions predating v7.4.2, Guild Wars 2 does not have a dedicated L7 application classification in the Exinda. The original Guild Wars does, but the definition for the original does not work for the second game. Even after making one manually, it is seen that the Guild Wars 2 traffic is still being erroneously classified as:
- Warcraft 3
CauseThe reason for the Bittorrent classification is that Guild Wars 2 uses some P2P protocols in order to facilitate the connections in game. On 'medium' or 'high' levels of Bittorrent sensitivity, where the system takes a more heavy handed approach to potential Bittorrent traffic and erring on the side of caution, classifies it as such, some of this P2P traffic from Guild Wars 2 gets classified as Bittorrent. This traffic will then fall under any 'Bittorrent' policies in place in the Exinda. If these policies are set to throttle, choke or otherwise discard Bittorrent traffic, this Guild Wars 2 traffic will be lost and connections will fail.
The reason for the Warcraft 3 classification is that Guild Wars 2 utilizes TCP 6112 for the majority of its conversations. TCP 80 and 443 are also used for showing web pages and 'latest news' in the game. TCP 6112 is a port that is also used by Warcraft 3 (a game released in 2001) for its multiplayer system. The definition for Warcraft 3 currently in the Exinda uses TCP 6112, and unless it is deleted from that definition and added to a specific Guild Wars 2 application, any traffic using TCP 6112 will be classified as Warcraft 3.
WorkaroundIn order to stop the Bittorrent classification, a workaround currently is to set the Bittorrent sensitivity to 'Low'. This will stop the false positive for the game traffic, though it might allow through some legitimate Bittorrent traffic that would otherwise be stopped. This can be done by going to Configuration > System > Setup, under the 'Monitoring' tab. The 'Bittorrent Sensitivity' option can be toggled between low / medium / high.
For the Warcraft 3 classification, it is possible to delete the TCP 6112 port from the Warcraft 3 definition (it uses a range of TCP 6112-6119 by default) and add the port to a Guild Wars 2 definition instead. This can be done by going to Configuration