Re: Traffic managed on downstream not upstream
 

That would be the collection of people who bit.

Anyway has anyone else seen this behaviour where only one direction is policed?

It would be good to see!

Re: Traffic managed on downstream not upstream
 

Anyway...there are legal torrents also...
Anyone going to answer the question & stick to the topic ? :O

Re: Traffic managed on downstream not upstream
 

I would like to know, I am going to keep trying it, I never knew about the 888 thing, I might try that :)

Re: Traffic managed on downstream not upstream
 

Lol I can see people franticly smacking their '8' buttons over and over to get their next torrent fix....

Re: Traffic managed on downstream not upstream
 

Just checked on the VM forum and this is correct.

Re: Traffic managed on downstream not upstream
 

Is it possible to do this online or over VOIP? I have a virgin phone line but my handset is broken :(

Re: Traffic managed on downstream not upstream
 

Subscriber Traffic Management on DoCSIS 1.1 and above Service Flows is uni-directional, such that if you breach in the Upstream direction it is the upstream speed that the penalty is applied to and vice versa.

It just happens that if it is an upstream breach it will slow the downstream by way of throttling acks etc.;)

Re: Traffic managed on downstream not upstream
 

Given that Virgin at least previously applied a penalty profile which affected both directions the capability is kinda irrelevant.

Have they now started penalising in one direction only? Is this the official policy now?

Re: Traffic managed on downstream not upstream
 

When STM was introduced on the VXRs all devices were using DoCSIS 1.0 Profiles and therefore QoS Profiles.
STM on QoS Profiles applied the penalty to both directions as default.

Once they started to move to D1.1/D2/D3 they introduced Service Classes

STM with Service Class is uni-directional by design.

So the fact that it was bi-directional was only because there was no other way of implementing.

As is now the case there is no way to run STM with Services Class other than uni-directional - So VM don't have a choice;)

Re: Traffic managed on downstream not upstream
 

Not worried about the capabilities of the individual software versions, there's no need to quote release notes or whatever else you have been reading recently as you presumably have a contract with Virgin again.

Nice easy question, back to the original post's question - have the enforcement rules been changed recently?

It's always been uni-directional if configured that way, QoS profiles and SIDs. If it were purely about the DOCSIS change anyone on a 10k / BSR would have seen this as soon as they were migrated over so assuming this is intended behaviour someone has changed the configurations.

Re: Traffic managed on downstream not upstream
 

VM moved all cable modems that were capable of supporting D1.1 working onto service flows and therefore that changed the way that STM worked.

So the enforcement rules have not been changed - It is just the way that the penalty is applied that has changed.

Design position for QoS based STM was bi-directional.

It is far more difficult to achieve the same with Service Flows so uni-directional put in place.

It has not been done recently - It has always been that way on the 10Ks and subsequently the BSRs - more recently the VXRs had 1.1 Service Flows applied so that may have been more noticable.

p.s. How are you getting on with Application Based Traffic Management?

Re: Traffic managed on downstream not upstream
 

Personally as I'm not a customer of VM I've nothing to complain about.

Anecdotally it was a disaster and remains so. Were you involved in its' deployment? Were you the guy who went on the sick straight after it went live? :)

---------- Post added at 16:30 ---------- Previous post was at 16:26 ----------

Oddly I remember reading many reports from people on the overlay who were enforced in both directions, maybe they were on BSRs.

Re: Traffic managed on downstream not upstream
 

When I was a customer and STM was introduced it was both ways.

I know, I was there and left. I only came back as I moved and there was no other viable option.

If it helps I was in Bolton then.

Re: Traffic managed on downstream not upstream
 

Yeah it would have been when it was first introduced. More interesting would have been if it was affecting customers in both ways still on the new overlay network - Bolton is a 10k site.

Re: Traffic managed on downstream not upstream
 

Funnily enough I know someone who will be more than willing to put it to the test in the Bolton area as he will allow me to acess his PC while he is at work with his permission.

I'll give him a bell.