From: Daniel Chemko <dchemko@smgtec.com>
To: Fajar Priyanto <fajarpri@arinet.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: I thought ssh is port #22 ?!!
Date: Wed, 31 Mar 2004 17:57:40 -0800 [thread overview]
Message-ID: <406B7714.4050202@smgtec.com> (raw)
In-Reply-To: <200404010832.10293.fajarpri@arinet.org>
32873 is the SOURCE port of the connection, not the DESTINATION port,
which defaults to 22
Fajar Priyanto wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi guys,
>I'm not really sure about this. I thought ssh is made in port #22?
>When I made a ssh session into my server, /var/log/messages showed this:
>Apr 1 09:20:20 server2 sshd[2711]: Accepted password for root from
>192.168.0.234 port 32873 ssh2
>
>Why did it use port #32873?
>Is there something wrong with my ssh or firewall?
>TIA,
>- --
>Fajar Priyanto | Reg'd Linux User #327841 | http://linux.arinet.org
>08:31:42 up 36 min, Mandrake Linux release 9.2 (FiveStar) for i586
>public key: https://www.arinet.org/fajar-pub.key
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.3 (GNU/Linux)
>
>iD8DBQFAa3EYkp5CsIXuxqURAluBAKCNiyg8+KXYDu/JuZghSVMXvfrjMgCdG7O2
>Bb4SQcbOiAqALl1o9yQ5H1k=
>=4uUZ
>-----END PGP SIGNATURE-----
>
>
>
>
next prev parent reply other threads:[~2004-04-01 1:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 1:32 I thought ssh is port #22 ?!! Fajar Priyanto
2004-04-01 1:57 ` Daniel Chemko [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 2:10 cldavis
2004-04-01 15:14 Martinez, Michael
2004-04-01 15:28 ` Antony Stone
2004-04-01 17:20 Daniel Chemko
2004-04-01 18:27 ` Tony Earnshaw
2004-04-01 21:27 ` Cedric Blancher
2004-04-01 21:38 ` Antony Stone
2004-04-01 19:41 Daniel Chemko
2004-04-01 19:55 ` Antony Stone
2004-04-01 20:22 T. Horsnell (tsh)
2004-04-01 20:39 ` Antony Stone
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=406B7714.4050202@smgtec.com \
--to=dchemko@smgtec.com \
--cc=fajarpri@arinet.org \
--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.