Sorry I haven't been updating. I'm also still unable to use Vent, and am experiencing what feels like data coming in irregular bursts in MMOs (everyone freezes for half a second while my client waits for data. It's a killer in PvP in can tell ya).
It's a Catch 22 for me unfortunately because un-reliable vent got me benched by my team so haven't had much opportunity to test. Also not been playing as much over the last couple of weeks. And I'd don't wanna moan if I can't back it up with real world stats.
However, here are some other community threads that suggest the issues is still current for more than just a few of us.
I'm gonna log a ticket for myself probably this weekend because we haven't heard any more requests for data from Orcon in this thread. I think it's the right thing to do since Geekzone isn't really their official support channel. Not sure if there's anything else we can do as a community to help make it better.
I was thinking of asking if they can turn interleaving back on for me and take the latency hit for possible increased stability. I will also try to do some Skype testing as it is a similar type of app. And of course I will try yet another clean install of Vent itself.
I've been trying out isposure as suggested by Mauricio here. Seems pretty good to me so far Now I only have a few days data, so this isn't fair, but wanted to see if you guys also had similar results. Maybe this test is another tool we can use to quantify the experiences we have shared regarding gaming and voice packets. Not really sure how it is calculated though (e.g. If it is somehow measuring actual online gameplay, or just pinging some local server).
Anyway, whilst my line speed compares favourable, and most other tests are close enough to not be too concerning at this point, my gaming speed test looks like this when compared with most plans...
That example is compared to ICONZ ADSL8 plan. However most other ISPs seem to be delivering in the 20 -32 round-trips range as well (Vodafone was up at 40, put only had 1 data point so..) If anyone else is particpating it would be great to see your data after a few days (or more) of testing. Also any informed opinions are welcome as to what this data means, and if it relevant to our discussion of latency and unstable gaming/voice experiences.
Some fresh tracerts for Orcon troubleshooting (Thanks James!)
1) My Vent server 2) WoW 3) Google.co.nz
1) Ventrillo tracert 69.12.97.70 Tracing route to CHROMIUM [69.12.97.70]over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.2.1 2 19 ms 19 ms 21 ms lo-1.erx02.nct.orcon.net.nz [60.234.8.18] 3 18 ms 18 ms 17 ms ge-0-3-0-200.cr1.nct.orcon.net.nz [60.234.9.1] 4 18 ms 19 ms 17 ms ge-2-2-0.gw4.akl1.asianetcom.net [203.192.166.69] 5 18 ms 18 ms 18 ms gi9-3.gw1.akl1.asianetcom.net [202.147.55.209] 6 171 ms 170 ms 170 ms po8-3.gw1.sjc1.asianetcom.net [202.147.55.206] 7 169 ms 170 ms 170 ms po1-0.gw2.sjc1.asianetcom.net [202.147.50.166] 8 159 ms 159 ms 160 ms ge-6-2-1.mpr1.sjc7.us.above.net [64.125.13.101] 9 161 ms 160 ms 169 ms so-1-0-0.mpr2.sjc2.us.above.net [64.125.30.178] 10 251 ms 236 ms 235 ms so-1-0-0.mpr1.lga5.us.above.net [64.125.26.142] 11 237 ms 253 ms 240 ms so-0-0-0.mpr2.lga3.us.above.net [64.125.30.22] 12 218 ms 218 ms 219 ms 208.184.48.181.speakeasy.net [208.184.48.181] 13 232 ms 226 ms 226 ms CHROMIUM [69.12.97.70] Trace complete.
2) WoW Tracing route to 12-129-225-12.attens.net [12.129.225.12]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 68 ms 20 ms 21 ms lo-1.erx02.nct.orcon.net.nz [60.234.8.18] 3 18 ms 18 ms 19 ms ge-0-3-0-200.cr1.nct.orcon.net.nz [60.234.9.1] 4 19 ms 18 ms 17 ms ge-2-2-0.gw4.akl1.asianetcom.net [203.192.166.69] 5 22 ms 21 ms 19 ms gi9-3.gw1.akl1.asianetcom.net [202.147.55.209] 6 209 ms 208 ms 208 ms po0-0.gw1.sjc1.asianetcom.net [202.147.50.129] 7 210 ms 209 ms 207 ms 12.126.40.25 8 179 ms 178 ms 179 ms tbr1.sffca.ip.att.net [12.122.81.102] 9 177 ms 178 ms 178 ms cr1.sffca.ip.att.net [12.122.19.25] 10 180 ms 178 ms 178 ms cr1.la2ca.ip.att.net [12.122.3.122] 11 179 ms 178 ms 179 ms tbr1.la2ca.ip.att.net [12.122.19.146] 12 179 ms 177 ms 179 ms 12.127.3.185 13 179 ms 178 ms 177 ms 12.122.255.74 14 178 ms 177 ms 178 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 15 179 ms 179 ms 179 ms 12.129.209.99 16 178 ms 179 ms 180 ms 12-129-225-12.attens.net [12.129.225.12] Trace complete.
3) google.co.nz Tracing route to google.co.nz [64.233.161.104]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 20 ms 19 ms 19 ms lo-1.erx02.nct.orcon.net.nz [60.234.8.18] 3 18 ms 17 ms 19 ms ge-0-3-0-200.cr1.nct.orcon.net.nz [60.234.9.1] 4 21 ms 18 ms 18 ms ge-2-2-0.gw4.akl1.asianetcom.net [203.192.166.69] 5 18 ms 18 ms 18 ms gi9-3.gw1.akl1.asianetcom.net [202.147.55.209] 6 169 ms 169 ms 170 ms po8-3.gw1.sjc1.asianetcom.net [202.147.55.206] 7 180 ms 180 ms 180 ms 74.125.49.97 8 171 ms 179 ms 177 ms 216.239.46.192 9 241 ms 228 ms 232 ms 66.249.95.212 10 247 ms 247 ms 277 ms 72.14.238.137 11 259 ms 251 ms 253 ms 64.233.175.111 12 258 ms 258 ms 256 ms 216.239.48.190 13 241 ms 243 ms 240 ms od-in-f104.google.com [64.233.161.104] Trace complete.
(9880ish kbps. My best ever at this time of day!)
Behaviour observed = sitting in Vent idling right now and still getting disconnected automatically at random times. When in conversation it breaks up and comes in chunks of talking delivered well behind the actual conversation (1 or 2 minutes behind)
Zub: Behaviour observed = sitting in Vent idling right now and still getting disconnected automatically at random times. When in conversation it breaks up and comes in chunks of talking delivered well behind the actual conversation (1 or 2 minutes behind)
Yea exact same issue I have with vent, rejoin its fine for maybe 20-30 secs then breaks up and disconnects most times. I will look at isposure when i get home and see what kind of results I get.
Quick update: Orcon still working on the issues covered in this thread... No requests for testing from the community at the moment so this thread will be quiet for a bit longer
2nd July 2008 - Ticket update "The latency with vent is something our networking team is aware of and are actively investigating a fix for it, the issue is that we have yet to find a way to tell if a packet is sent from vent in our network which means it gets deprioritized like P2P traffic, once we resolve this we will be able to deliver vent packet more easily.
It is a similar situation with AoC with regards to recognising the packets while the issue with WoW should be solved within the next week."
Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.
Well this week I have generally been recieving very good download speeds. My Vent has been stable for an hour. Haven't been playing AoC due to latency issues but this give me incentive to open that ccount back up and give it another try.
Never heard back on my ticket so not sure what changed, but am glad to give Orcon credit and say thanks for putting in the extra bandwidth or whatever it took.
So I'm going to leave this thread to time-out and lock unless you guys still need to post data regarding outstanding gamer/voip latency issues you are still experiencing.
Thanks to all for the support and focussed technical responses on this thread.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
(9880ish kbps. My best ever at this time of day!)
