From: Tony Earnshaw <tonye@billy.demon.nl>
To: netfilter@lists.netfilter.org
Subject: RE: I thought ssh is port #22 ?!!
Date: Thu, 01 Apr 2004 20:27:34 +0200 [thread overview]
Message-ID: <1080844053.26229.111.camel@localhost> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF567928A@alderaan.smgtec.com>
tor, 01.04.2004 kl. 19.20 skrev Daniel Chemko:
> > Here's how it works. The server listens on port 22. The client opens a
> > connection to the server, and tells the server which return port to use.
> > If you do "netstat -an" you will see the server talking on port 22, and
> > the client talking on some high numbered port like 32873. The high
> > number port used is random. It will change from one session to the next.
> >
> > This is true not just for ssh - it is true for most tcp applications.
> Unfortunately I have the "privilage" of maintaining a customer TCP
> protocol which cans you if your source and destination ports aren't as
> specified by their fcked up protocol!!
Nevertheless, that's how TCP works, for every customer in the Universe.
Sack your customer, and get another?.
It would be better if you learned not to top post and to quote
correctly.
--Tonni
--
mail: billy - at - billy.demon.nl
http://www.billy.demon.nl
next prev parent reply other threads:[~2004-04-01 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 17:20 I thought ssh is port #22 ?!! Daniel Chemko
2004-04-01 18:27 ` Tony Earnshaw [this message]
2004-04-01 21:27 ` Cedric Blancher
2004-04-01 21:38 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 20:22 T. Horsnell (tsh)
2004-04-01 20:39 ` Antony Stone
2004-04-01 19:41 Daniel Chemko
2004-04-01 19:55 ` Antony Stone
2004-04-01 15:14 Martinez, Michael
2004-04-01 15:28 ` Antony Stone
2004-04-01 2:10 cldavis
2004-04-01 1:32 Fajar Priyanto
2004-04-01 1:57 ` Daniel Chemko
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=1080844053.26229.111.camel@localhost \
--to=tonye@billy.demon.nl \
--cc=netfilter@lists.netfilter.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.