Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Ramin Alidousti <ramin@cannon.eng.us.uu.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ssh versus scp
Date: Mon, 25 Nov 2002 21:27:25 +0000	[thread overview]
Message-ID: <marc-lartc-103825987205148@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103825161927999@msgid-missing>

Hi,

You are out of luck here. There is no distinction between ssh and scp
at IP, TCP or the application layer for that matter. Basically scp is
a wrapper which uses ssh as the transfer method...

Ramin

On Mon, Nov 25, 2002 at 08:12:07PM +0100, Sebastian 'spax' Pape wrote:

> hi!
> 
> I'd like to priorize ssh traffic, but of course I don't like scp to
> get priorized, too. In the "actual script" of the howto priorization
> is done with this:
> 
> | # TOS Minimum Delay (ssh, NOT scp) in 1:10:
> | tc filter add dev $DEV parent 1:0 protocol ip prio 10 u32 \
> |      match ip tos 0x10 0xff  flowid 1:10
> 
> I'm not sure if I got all of it, but it seems to me, that there is no
> port match - it seems to me that this rule matches all packets with a
> Minimize-Delay 16 (0x10) TOS value.
> 
> I watched some packets with tcpdump and it also seems that scp packets
> all have the Maximize-Throughput 8 (0x08) TOS value, but all "pure
> ssh" packets have Normal-Service 0 (0x00). It's no problem to match
> these packets with iptables (just drop me a note if you want to have
> the iptables syntax). But the question I have is:
> 
> Are these TOS-values standard for ssh and scp or do all
> ssh/scp-clients use the values they like? I searched the net, but
> haven't found anything usefull, yet.
> 
> best regards
> 
> 		Sebastian
> 
> -- 
> Sebastian 'spax' Pape          | A diplomat is someone who can tell you to go
> mailto: sebastian@p-a-p-e.de   | to hell in such a way that you will look
> gpg: http://p-a-p-e.de/gpg.asc | forward to the trip.
>          --- Do you want to know more? http://www.p-a-p-e.de/ ---
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-11-25 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 19:12 [LARTC] ssh versus scp Sebastian 'spax' Pape
2002-11-25 21:27 ` Ramin Alidousti [this message]
2002-11-25 21:44 ` Robert Penz
2002-11-25 22:11 ` Martin A. Brown
2002-11-25 22:28 ` M.F. PSIkappa
2002-11-25 22:34 ` Sebastian 'spax' Pape
2002-11-25 22:42 ` Sebastian 'spax' Pape
2002-11-26  4:15 ` Kenneth Porter

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-103825987205148@msgid-missing \
    --to=ramin@cannon.eng.us.uu.net \
    --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