|
|
|
Lurch:
Thanks for that but as I mentioned in a previous post wowtunnels etc is not resolving the problem. Specific rule isn't working ??? Only change I've made is switching to Big Time from Adventure... straight away you notice the difference. Lag spikes, high latency.... unplayable.
doozy:
There's been a specific rule for WoW since late december, I would recommend Smoothping or WoWTunnels to anyone on any plan on any ISP playing WoW though, works wonders!
Ragnor:doozy:
There's been a specific rule for WoW since late december, I would recommend Smoothping or WoWTunnels to anyone on any plan on any ISP playing WoW though, works wonders!
Depends how the rule was defined (port/protocol/ip address ranges), things may have changed which may mean it's not matching all wow traffic or all servers etc.
Wow uses TCP port 3724 for game data and TCP port 1119 for battle.net authentication.
Wowtunnels ssh tunnel uses TCP port 22 I believe.
doozy:
Changes to ports/protocols wouldnt matter in this instance and am in touch with Blizzard to ensure the rule works for all WoW players on Big Time, being one, of course I want it to work as well (which it is, clearly see a number of connections at all times of the day/night to Blizzard's servers).
As for Wowtunnels ... should really see if we can have a local provider of this service ... would be able to ensure it works all the time and upstream changes don't impact people down this end of the pipe.


DravidDavid: I just switched a few days ago.
[snip]
There is also a plan available that Telecom does not advertise. My friend called one night to complain and they just said they would put him on an unlimited plan without traffic shaping. When I asked about it they claimed it did not exist.
[snip]
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
|
|
|