Article View: comp.protocols.tcp-ip
Article #7949Re: Determining Port Numbers & The RPC Portmapper
From: Maritza Ramirez
Date: Fri, 22 Jan 1993 00:42
Date: Fri, 22 Jan 1993 00:42
74 lines
3394 bytes
3394 bytes
In article <1993Jan21.155457.27880@panther.mot.com>, ronf@panther3.panther.mot.com (Ron Feigen) replies:
|>
|> [text deleted, see earlier posting]
|>
|>
|> registerrpc will register a prog#/ver# with portmapper. Portmapper assigns the
|> port #. svc_unregister() removes the entry. pmap_getport() looks up a prog#/
|> version# on a host. You must of course know the host name, prog# and version#
|> in advance. Be careful about having the same prog# with different version #s.
|> Portmapper returns the port of a program with a match on prog #, but will give
|> you the latest (I believe) version # if it doesn't find an exact match.
|>
|>
|> [text deleted, see earlier posting]
|>
|> Ron
|>
I was just wondering if it is possible to connect and send commands to the
RPC portmapper without using RPC calls (svc_xxx or pmap_xxx) but tli or
socket calls. That approach of connecting and sending commands is possible
when working with some services. For example, I have some source code that
sends commands to an ftp server after establishing a connection with it on
its well known port 21. That program follows the same approach as when we
use a telnet connection to send control commands to ftp (see example).
--o--
Example:
___________________ ftp's well known port
/
$ telnet itsname 21
Trying 128.96.133.64 ...
Connected to itsname.
Escape character is '^]'.
220 itsname FTP server ready. _____________ ftp server accepts connection
USER maritza
331 Password required for maritza.
PASS mypass123
230 User maritza logged in.
HELP
214-The following commands are recognized (* =>'s unimplemented).
USER PORT RETR MSND* ALLO DELE SITE* XMKD CDUP
PASS PASV STOR MSOM* REST* CWD STAT* RMD XCUP
ACCT* TYPE APPE MSAM* RNFR XCWD HELP XRMD STOU
REIN* STRU MLFL* MRSQ* RNTO LIST NOOP PWD
QUIT MODE MAIL* MRCP* ABOR NLST MKD XPWD
QUIT
221 Goodbye.
Connection closed by foreign host.
$
Note that when using this approach, the commands that the ftp server
recognize are the low level commands described on the RFC959 (e.g.,
PORT, PASV, RETR, STOR).
--o--
The question is: Is it possible to connect and send commands to the RPC
portmapper using tli or socket calls ?
The protocol specifications for the portmapper (appendix A of the RFC1057)
does not say anything about the low level commands that the portmapper
recognizes.
Does anyone knows which low level commands must be given to the portmapper
server after a connection is established to (1) register an application,
and (2) get the assigned port from a client application ?
Thanks,
Maritza
Technical Details
Message-ID:
<1993Jan22.004203.5030@walter.bellcore.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!walter!espresso!maritzaReferences:
<1993Jan20.162611.25831@walter.bellcore.com> <1jki9vINNmr9@aludra.usc.edu> <1993Jan21.155457.27880@panther.mot.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.protocols.tcp-ip Path: arc1-ca.pugleaf.net!sparky!uunet!walter!espresso!maritza From: maritza@espresso.bae.bellcore.com (Maritza Ramirez) Subject: Re: Determining Port Numbers & The RPC Portmapper Message-ID: <1993Jan22.004203.5030@walter.bellcore.com> Sender: news@walter.bellcore.com Nntp-Posting-Host: espresso.bae.bellcore.com Organization: Bell Communications Research References: <1993Jan20.162611.25831@walter.bellcore.com> <1jki9vINNmr9@aludra.usc.edu> <1993Jan21.155457.27880@panther.mot.com> Date: Fri, 22 Jan 93 00:42:03 GMT Lines: 74