HTTP on low priority

[swordfish1]

Ok, I finally experienced myself the problem few people mentioned - either download or browse but not both.

So it seems that if you are using some crapy P2P app like Morpheus (because the good ones don't work) in background and it is not downloading almost anything at the moment, and you try to browse, it does not work, but if you close the P2P app then the HTTP works again .. voila!

So simple conclusion I can make from this, is that P2P traffic got higher priority than HTTP, hence P2P kills HTTP!

According to their web site, isn't it suppose to be the oposite? I was expecting my web browsing to kill P2P, not the oposite!

So anyway, as far as I know I can do the prioritisation with Iptables, just have to figure out how, so then I can set it up properly on my side, as the WBS techies are obviously proving their incompetence over and over again!

 

[slimothy]

i think you need to go pick up a book about packet prioritisation

 

[bwana]

Sounds to me like your p2p is using port 80 to get around the shaping.

 

[ic]

i think you need to go pick up a book about packet prioritisation

Any recommendations there Slimothy? Which books do you think WBS techies have been reading? - we should get the same ones...

 

[jmn]

Any recommendations there Slimothy? Which books do you think WBS techies have been reading? - we should get the same ones...

Google

Couldn't resist...

 

[ic]

Google

Couldn't resist...

Sure, but somehow I don't think Google knows which books the WBS techies have been reading, and this should be a no brainer for Slimothy .