× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



First, let me say that I've never done dial-up TCP/IP from an iSeries.  I
use FreeBSD machines for that, and have been doing so since before
SLIP/PPP existed on the iSeries.

However, having said that, the IP layer usually doesn't know or care what
the physical transport layer is.  It's a basic philosophy of TCP/IP -- it
can be run over any sort of transport (Ethernet, Token-Ring, Modem, Serial
Cable, ISDN, CSU/DSU, etc, etc) and software shouldn't need to know
anything about that physical layer.

Therefore, wouldn't the commands to add/remove routes be ADDTCPRTE,
RMVTCPRTE, CHGTCPRTE, etc?   And the API be ioctl()?

I know that on Unix or Windows systems I can modify the routing table for
a dial-up interface using the standard routing commands.  Although I've
never tried it, I would sure expect OS/400 to work the same way.


On Wed, 21 Apr 2004, Ian Patterson wrote:

> We use originators TCPPTP connection profiles for outgoing connections with
> PPP dial-up
> These are created with Ops Nav. (OS400 is 5.1)
>
> We would like to programatically change part of the profile via an API or
> similar, but can not find any references to this. Nor can we find any CL
> commands other than simple add or remove. The ADDTCPPTP command does not
> allow input for TCP routing info.
>
> Does anyone know if it is possible to change these profiles - in particular
> the section dealing with default / static routes.
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.