From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ssh versus scp
Date: Mon, 25 Nov 2002 22:11:53 +0000 [thread overview]
Message-ID: <marc-lartc-103826242308109@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103825161927999@msgid-missing>
For posterity:
Data gathered with the following tcpdump command:
# tcpdump -nnqti eth0 port 22 and host y.y.y.y
ssh session:
<session setup snipped, no special ToS value; normal>
x.x.x.x.48101 > y.y.y.y.22: tcp 48 (DF) [tos 0x10]
y.y.y.y.22 > x.x.x.x.48101: tcp 0 (DF)
y.y.y.y.22 > x.x.x.x.48101: tcp 48 (DF) [tos 0x10]
y.y.y.y.22 > x.x.x.x.48101: tcp 80 (DF) [tos 0x10]
x.x.x.x.48101 > y.y.y.y.22: tcp 0 (DF) [tos 0x10]
scp session:
<session setup snipped, no special ToS value; normal>
y.y.y.y.22 > x.x.x.x.48103: tcp 48 (DF)
x.x.x.x.48103 > y.y.y.y.22: tcp 64 (DF) [tos 0x8]
y.y.y.y.22 > x.x.x.x.48103: tcp 48 (DF) [tos 0x8]
x.x.x.x.48103 > y.y.y.y.22: tcp 0 (DF) [tos 0x8]
y.y.y.y.22 > x.x.x.x.48103: tcp 48 (DF) [tos 0x8]
So, one *should* be able to do something like this:
# iptables -t filter -A FORWARD -m tos --tos 0x08 -j scpchain
# iptables -t filter -A FORWARD -m tos --tos 0x10 -j sshchain
http://iptables-tutorial.frozentux.net/iptables-tutorial.html
I haven't done it.....Good luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-25 22:11 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
2002-11-25 21:44 ` Robert Penz
2002-11-25 22:11 ` Martin A. Brown [this message]
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-103826242308109@msgid-missing \
--to=mabrown-lartc@securepipe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.