Re: Traffic managed on downstream not upstream
 

this can go some way into explaining why jitter has got worse. Previously one could get upload throttled fairly quickly by downloading too muh, so eg. a torrenter doing heavy both ways would get upload throttled quickly. Now it will just be the download and will take at least a few hours for the upload to get throttled (assuming evading the protocol shaping).

Re: Traffic managed on downstream not upstream
 

And how would a torrenter evade the traffic shaping? Most VPN providers either exclude torrenting (due to bandwidth needed) or charge extra to price it out.

For a serious torrenter a seedbox is the better option which won't impact on he network until the HTTP/FTP download from it which isn't covered with the shaping.(is this what you meant?)

Re: Traffic managed on downstream not upstream
 

a few on here have openly stated they use VPN to evade shaping.

I assume on VM I could use port 443 encrypted for torrents to evade the shaping.

Re: Traffic managed on downstream not upstream
 

Lol.. No not me.. If you remember last time I was around I told you DPI etc was nothing to do with me.. Purely DoCSIS/CMTS.

Not 100% on how CTM on the BSRs invokes the penalty.. Will check and let you know.

Re: Traffic managed on downstream not upstream
 

Sorry Chrys you are confusing torrent traffic with newsgroups.

Re: Traffic managed on downstream not upstream
 

Thanks.

Maybe you can answer one question, why 6.4MHz channels, why not bond 3.2s? Laser load?

Re: Traffic managed on downstream not upstream
 

Are you guys getting all techie on us?

Re: Traffic managed on downstream not upstream
 

And why not use 12.8Mhz Flux Capacitors instead? :D

Re: Traffic managed on downstream not upstream
 

Ooooooooooooo Flux capacitors!!!!!!!!!!!!!!!1

I'm feeling randy now!!!!!!!!!!!!

Re: Traffic managed on downstream not upstream
 

pip true the VPN's are mostly used for newsgroups but p2p shaping can still be evaded.

Re: Traffic managed on downstream not upstream
 

To answer the OP: I have a lot of friends on the 20meg service and asked around a little during management times and what not.

It appears that upload speeds are not affected. Wtih two out of three asked reporting 5mb down and 2mb up whilst the other had 6 down and 2 up.

Re: Traffic managed on downstream not upstream
 

O.o

Re: Traffic managed on downstream not upstream
 

VM havent until very recently had the CMTS hardware to do Upstream Channel Bonding.. Still don't on Motorola.
Will be coming along over the coming months.
So only way to maximise upstream in the short term was 6.4Mhz 16QAM

Re: Traffic managed on downstream not upstream
 

I saw second half of 2011 targetted for upstream bonding on the BSR and not on the 2/8 cards that VM have used thusfar. I guess a move to the RX48 teamed with the TX32 is on the 'to do' list.

From this I take it it is the 10k being used on the 200/20+ trials.

Getting any MC3GX60Vs in to play with?

Re: Traffic managed on downstream not upstream
 

Already using TX32 for downstream, but yes RX48 for upstream channel bonding.

The 200/20 is using CMTS from A.N.Other Vendor ;-)

Got 3G60s going into test.