|
It's not too bad of a configuration. You need to create a PTP profile with WRKTCPPTP. The manual has some good examples - find one that's close and modify it. You'll need a PPP line description - the controller and device should autocreate. I can send you configs off list if you want. On 1/25/07, jmmckee@xxxxxxxxxxxxxx <jmmckee@xxxxxxxxxxxxxx> wrote:
A modem is used to establish a TCP/IP connection to a specific destination , much like a home computer dialing (I still do this - vanishing breed) an ISP. Once the ISP modem answers, a SLIP connection is established. Point of using P-t-P is that a (relatively) secure connection is established between two specific points. We currently use ZMODEM over an async modem. But, the other party is having difficulty with their phone system. They feel a change is needed. ZMODEM provides the capability to transmit and receive files. Difference between ZMODEM and P-t-P connection is that standard FTP can be used, and the connection is a direct connection. I would think this would be slightly more secure than a straight, unencrypted FTP connection, as the route is more direct. In looking at the setup, it appears that at a minimum, a controller description would be required as that would be the mechanism where the disliag process would be initiated. With ZMODEM, a line/controller/device is also created. The actual dialing process is controlled by commands within ZMODEM, specifically, the DIAL command. With a P-t-P connection the dialing (has to be a more modern word) is initiated when the configuration items are varied on. With a P-t-P connection, the default route is NOT the standard gateway, but the dialup connection. At least, that is my understanding. John McKee Quoting Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>: > >> What are commands needed to establish a Point-to-Point FTP connection? > > Do you mean a point-to-point TCP/IP connection? in other words, SLIP or > PPP? Or do you mean something like PPTP? Or PPoE? > > FTP is just a program that runs over TCP/IP. It doesn't matter whether > that TCP connection was established via SLIP/PPP, or whether it uses any > of the hundreds of other ways of establishing a TCP/IP connection. > (Etherhet, Token Ring, FDDI, ISDN, etc, etc, etc.) FTP doesn't know or > care which underlying physical media is used to transport the TCP/IP > packets. It just uses TCP/IP. Let the operating system worry about how to > transport the packets! > > This is true of all TCP/IP software, of which FTP is only one. Others > (TELNET, E-MAIL, WEB, etc, etc) will also work over the same PTP > connection. > >> I am assuming that a line description. controller, and device >> description are needed and must be manually created before ADDTCPPTP can >> be used. The iSeries already has functioning access to the internet. > > I'm lost. If you already have internet access, why do you need a > point-to-point connection? > > >> Not sure where to look for the answers and appreciate all assistance. >> > > A quick Google search found this: > http://tinyurl.com/35bun8 > > It has lots of links to information about configuring and troublehsooting > SLIP and PPP. Of course, I'm not exactly sure if that's what you're > looking for... > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
