Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Dhaval Patel" <dhaval@patel.sh>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Wonder Shaper problem?
Date: Thu, 03 Jan 2002 16:59:09 +0000	[thread overview]
Message-ID: <marc-lartc-101007714917245@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100998859627061@msgid-missing>

you can have your firewall set the tos for ftp to something like 0x08 and keep
only low bandwidth high priority things like ssh as 0x10.

"Jason A. Pattie" <pattieja@pcxperience.com> said:

> So then is there a way to modify the packet on the way out of squid to 
> force it to be the TOS we want that will cause it to go to 20: instead 
> of 10: ?  Maybe modification of squid is in order? to keep it from 
> changing the TOS field?  (We have the source!  :) )
> 
> Or is there some other way to make it so that SSH traffic itself is 
> bumped to higher priority than just the generic 0x10 TOS packets?  Maybe 
> match on destination or source port 22?
> 
> Dhaval Patel wrote:
> 
> >i could be wrong its been some time since i did this but i think that 0x10 is
> >for quick response time 0x08 is for high throughput  0x04 is for a more
> >guranteed service or something like that. 
> >
> >hope this helps.
> >
> >"Jason A. Pattie" <pattieja@pcxperience.com> said:
> >
> >>Found the TOS field was being set to 0x10 for "ftp" traffic and 0x08 for 
> >>"http" traffic.  What significance does that play?  And it is either 
> >>being done by Squid or by Mozilla, don't know how to tell which, though.
> >>
> >>Michael T. Babcock wrote:
> >>
> >>>On Wed, Jan 02, 2002 at 12:04:28PM -0600, Jason A. Pattie wrote:
> >>>
> >>>>Where in the output of tcdump does the TOS field appear?  I did the 
> >>>>'tcpdump -n -v -v' on the firewall and dumped the output to a file as I 
> >>>>started the Linux kernel download.  Is it appropriate to attach the 
> >>>>output (I stopped it after around 250 packets)?
> >>>>
> >>>In the version I have of tcpdump TOS only shows up when its set to
> >>>something special.
> >>>
> >>-- 
> >>Jason A. Pattie
> >>pattieja@pcxperience.com
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>LARTC mailing list / LARTC@mailman.ds9a.nl
> >>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
> >>
> >
> >
> >
> 
> -- 
> Jason A. Pattie
> pattieja@pcxperience.com
> 
> 
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
> 



-- 




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

      parent reply	other threads:[~2002-01-03 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 16:20 [LARTC] Wonder Shaper problem? Jason A. Pattie
2002-01-02 17:09 ` bert hubert
2002-01-02 17:44 ` Jason A. Pattie
2002-01-02 18:04 ` Jason A. Pattie
2002-01-02 19:22 ` Michael T. Babcock
2002-01-02 20:39 ` Jason A. Pattie
2002-01-03 16:25 ` Jason A. Pattie
2002-01-03 16:59 ` Dhaval Patel [this message]

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=marc-lartc-101007714917245@msgid-missing \
    --to=dhaval@patel.sh \
    --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