QOS: how can one identify heavy side of an TCP connection?
How can I determine which side of the TCP or UDP connection (upload or download) is larger?
Re: QOS: how can one identify heavy side of an TCP connection?
dont understand your question, excuse me
Re: QOS: how can one identify heavy side of an TCP connection?
he means, if user connects, for example, to the web server, he wants to determine whether user mainly downloads or uploads via that connection.
unfortunately, I can't see a way to do that. rmichael, what to you want to do with that heavy side?
unfortunately, I can't see a way to do that. rmichael, what to you want to do with that heavy side?
Re: QOS: how can one identify heavy side of an TCP connection?
I want to choke heavy downloads on the upload (ack) side.
Re: QOS: how can one identify heavy side of an TCP connection?
its very easy 
search forum or wiki for connection bytes and conn rate for mangle
and then chocke it in QT
search forum or wiki for connection bytes and conn rate
for mangleand then chocke it in QT
Re: QOS: how can one identify heavy side of an TCP connection?
he wants to limit ACK responses, as I understand... I'm hot sure if it's really possible...
Re: QOS: how can one identify heavy side of an TCP connection?
It also doesn't sound very wise. Dropping an ACK is as good as dropping two packets that were actually delivered, maybe more. It is counter-productive. If you want to limit a download, limit the download. If you want to screw up your network, drop ACKs.
And then there is the fact that UDP doesn't have such a thing as an ACK. ACK is a TCP protocol feature.
And then there is the fact that UDP doesn't have such a thing as an ACK. ACK is a TCP protocol feature.
Re: QOS: how can one identify heavy side of an TCP connection?
I think there's a way to do it with connection size and dst limit but I'm still trying to figure it out 
Re: QOS: how can one identify heavy side of an TCP connection?
please if you can find the way, please tell us. i'm working on it too..