• About us…

  • The archives

  • RSS The Gaming Session

  •  Better and faster with IPv6

  • ipv6 ready

Well, another session with Snowglobe, and yet another uncontrolled network flood. This time, though, I was able to isolate the traffic that was flooding the connection from the other hurly-burly that happens on the wire during routine operation and SL sessions.

It was Vivox. 400 megabytes of traffic blown through in minutes. And I’m a non voice-user, on a non-voice-enabled parcel. Since I’m on a capped connection (as most users outside North America are), this was naturally of great concern to me. On the highest bandwidth plan available to me, I can only have about 600MB during the day, peak, which must then be divided among the whole family.

Quite what started it, I’m not sure. It’s something that gets worse with time, as increasing amounts of traffic from one particular Vivox host appeared on the wire. Once I saw Vivox’s hostname in the packet traces, I reached for my preferences. Of course – I normally don’t even turn voice on, but it’s enabled by default every time I install a new viewer version (thanks a lot for that, Lab).

But hey, I’m not on a voice-enabled parcel – so why is it even trying to talk to Vivox so enthusiastically?

No idea.

Disable voice in preferences, the flooding stops. Re-enable? The flooding starts again.

Disable it again and log out?

Vivox is still sending me packets. Much smaller ones and at a lower rate, but it’s still trying to talk to me for a full 30 minutes after I logged out, and maybe 35-40 minutes after I disabled voice. Still forlornly trying to communicate with my system.

I don’t know why this should only happen with Snowglobe. Maybe the voice component is a little different. Maybe the interface between the viewer and the voice component is a bit buggy. I don’t know.

After a few messy edits, I’ve updated the JIRA with what happened. It’s a good, clean repro for me. I can trigger it every time. I just don’t want to.

Got a news tip or a press-release? Send it to news@taterunino.net.
Read previous post: