Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: nix4me <nix4me@cfl.rr.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ftp shaping and excluding ls packets
Date: Sat, 05 Nov 2005 13:26:40 +0000	[thread overview]
Message-ID: <436CB310.6060902@cfl.rr.com> (raw)
In-Reply-To: <436C0373.7080804@cfl.rr.com>

Toby wrote:

>nix4me wrote:
>  
>
>>I have examined the packets leaving and i can't seem to pin point which 
>>are the listings.  I ran ethereal and then continually requested lists, 
>>the only packets i see leaving are coming from port 60000 which is the 
>>control port.
>>    
>>
>
>As far as I know listings don't go through the control port, they go
>through one of the data ports, as if you were downloading a file.
>
>That's why you cannot differentiate them from regular downloads, unless
>the server software uses a different data port or different TOS flags or
>something.
>
>
>Toby
>
>  
>
Yes, I see them now.  They are indeed leaving on a shaped port range.  
And the packets are larger than the ACK size that I am putting at the 
head of the que.

They seem to be 1450 in length.

Mark
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-11-05 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05  0:57 [LARTC] ftp shaping and excluding ls packets nix4me
2005-11-05 11:21 ` Toby
2005-11-05 13:26 ` nix4me [this message]
2005-11-05 14:00 ` Andreas Unterkircher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=436CB310.6060902@cfl.rr.com \
    --to=nix4me@cfl.rr.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox