Ventrilo 3.0 (Port 3211)

[#1]

Seem to be having issues with this new version at different times of the day when connecting to a server using this port. It is fine until about 3pm then the ping hits 5k+ which basically means it chops up then disconnects me constantly.
I've checked its not an issue on my end by forwarding any relevant ports, not that this was necessary before, but still tried with no success.
I have raised a ticket with no reply for over 24 hours now which is pretty slow so thought i'd post here.
Is it possible that plus.net are somehow shaping the data or slowing it down? I have pinged the IP address and run tracerts outside of ventrilo which show a steady 40-50 ping, however when on ventrilo itself, when connecting to port 3211, it says 5000+ ping.
Any help appreciated, cheers.
Matt

[#2]

hmm, i just used that port - i use it and have no problems and ive been on it alot today

[#3]

Tracing route to saint.pure-voice.net [88.198.26.240]
over a maximum of 30 hops:
  1    2 ms    2 ms    2 ms  192.168.1.1
  2    21 ms    25 ms    35 ms  lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
  3    37 ms    26 ms    21 ms  ge0-0-0-504.pte-gw2.plus.net [84.92.4.90]
  4    30 ms    21 ms    30 ms  LINX1.LON-2.uk.lambdanet.net [195.66.224.99]
  5    40 ms    38 ms    45 ms  FRA-1-pos313.de.lambdanet.net [82.197.136.25]
  6    41 ms    37 ms    42 ms  FRA-3-eth100.de.lambdanet.net [217.71.96.70]
  7    42 ms    44 ms    51 ms  NUE-2-eth100.de.lambdanet.net [217.71.96.74]
  8    41 ms    42 ms    52 ms  lambdanet-gw.hetzner.de [213.239.242.214]
  9    40 ms    41 ms    40 ms  hos-bb2.juniper1.rz4.hetzner.de [213.239.240.140
]
10    43 ms    40 ms    54 ms  et.1.16.rs3k9.rz5.hetzner.de [213.239.244.40]
11    57 ms    46 ms    58 ms  static.88-198-26-240.clients.your-server.de [88.
198.26.240]
Trace complete.

[#4]

Pcoventry: you connected to a ventrilo using that port?

[#5]

Hi,
I'm currently looking into this as there's a couple of people reporting issues, I've raised it as an internal problem (47948), so far checking the flows for yourself the traffic is being picked up correctly, are you using a different server now to when it was a problem?

[#6]

Just to add that my Ventrilo ping is also bad sometimes during the evenings since changing to version 3. 2.5k to 4k. Used to it being between 30 and 70

[#7]

In fact just logged into mine now and its sitting at 5300ms.
87.117.195.90:4234

[#8]

Came here just wondering if this was a problem on my side: you guys are describing exactly what I get on my setup.
port 4333 here - can post more if needed.

[#9]

Yes.
When i was on sky we always had this it was the vent servers playing up - it happened for so long we moved over to teamspeak in the end, as vent was just too unstable

[#10]

Personally i dont have any issues with Ventrilo. Been solid as a rock.
Anyway, I still have an awful, unusable ping during Plusnet peak time. Please fix asap as its going my head in.
Obviously something has changed in the Vent traffic and plusnet isn't giving it priority since version 3 went live.

[#11]

apart fro on PRO where it would be put down as Gold.

[#12]

Raised a ticket and was asked to run Wireshark.
Going through the PLusnet guide to wireshark, it does look like Ventrilo 3 packets are being identified as Bronze traffic, which would explain the bad ping.

[#13]

Have looked at this and passed the information to Net Ops to get this fixed first thing tomorrow morning (Mon - Fri for P2 problems (47948)).  Sorry for the inconvenience this may be causing you all.

[#14]

Hi,
Net Ops have made the changes I asked them to do.  Live monitoring shows we are matching flows with the new signature.
FYI - you will need to disconnect/re-connect to your ventrilo server.

[#15]

Thx a lot.
It was much better last night.