On 7/25/05, Xtian <[EMAIL PROTECTED]> wrote: > > Bill and Scott: > > Many thanks for the info and the field descriptions. Right, I was doing about > 105KBps down (on my 1Mbps down, 384Kbps up DSL) which is everything, and then > initiated an SSH session and latency was as high as ever. Then I looked in > the rules and saw nothing for SSH. So I assumed it didn't know about SSH. That > ACKs in general are prioritized makes sense. I tried to make a queue > specifically for port 22 traffic, and wanted to elevate that above the > default queue, and thats where I was at a loss as to what I should put in > those schedule fields. I assumed that what Monowall handles with pipes is > what got put into scheduler options, but I was just not groking the logic > behind it.
You might try creating an SSH rule and put it in a higher priority queue if you're facing ACK starvation. The only queue with higher priority than ACKs is the VOIP queues though so be warned. Also matching on port for ssh will mean that SSH bulk traffic (scp/sftp) will match and get put in the higher priority queue. You would need to do port 22 and tos lowdelay (although I'm not sure the SYN packet will set that). --Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
