SCE 8000 Bittorrent Classification Problem

[emarkarov]

Hi!

I have SCE 8000 and try to limit bandwith for test user.

My user has test Package with

- Primary BWC UP/DOWN CIR 0 kbps PIR 2048 kbps,

- Default BWC UP/DOWN CIR 0 kbps PIR 2048 kbps,

- Bittorent BWC UP/DOWN  CIR 0 kbps PIR 256 kbps,

- Download over HTTP UP/DOWN  CIR 0 kbps PIR 512 kbps.

SCE generate Real-Time Subscriber Usage RDR for test user.

There are two problems:

- average bandwith of bittorrent is ~ 320 kbps, max up to 440 kbps, not 256 kbps

- there are peers (uTorrent 2.2, uTorrent 2.0.2) traffic from which is not classify as Bittorrent. In report I saw "Other UDP"

Did you ever resolve this?

SCE SW version: 3.6.0, Protocol Pack 22 Build 19

[lamersons]

Pretty much the same problem here. Same version(3.6) and same PP(22) only sce2000.

What im trying to do is to cut p2p from a service. If a torrent client is set to full encryption + random ports, sce starts to classify it as other tpc/udp,default service and so on. Once in a while it will cut download speed to zero, but then again some new peers whould do the job. Basicly it just takes longer to download a torrent file and it ruines the whole meaning of blocking p2p. Also i've tryed to limit bandwith to 1kbps - doesnt work.

So i'm joining your thread in a search for some kind of work around to this problem.

Thank you in advance.

[Jaime Soto Valenzuela]

Hi,

I have the same problem with Bittorent classification in a SCE 2020 (version 3.5.5 and PP22).

Did you find any solution on this?

Regards,

Jaime.