dial-on-demand

[Lawrence Strydom]

Hi,
I am new to tru64 and need some help please.
The setup we require is like this:
The application wil try to connect to a given ip address. pppd should then be initiated and based on the ip addres called, a connection should be made to a specific dial in server.

I was thinking about using chat scripts and command aliasing the ftp commands to calling the specific chat scripts,
alias ftp 10.1.1.1=chat etc/ppp/chat.10.1.1.1
but unfortunately the application tries to establish a direct ftp connection.

This meens I need some kind of dial-on-demand daemon to listen for attempted ftp connectios to a specific ip address. Does tru64 unix support the pppconfig utility? and if not, what other dial-on-demand options are availlable.
Thanks
Lawrence

[Al Licause]

Tru64 supports pppd for both incoming and outgoing connections. A good place to start is with the man pages for pppd and chat.

You'll need to dedicate an async port to this function and have an entry in /etc/inittab which sets up a device association.

It's been a while since I've dealt with ppp issues, but they often take some time to play with to get the correct options which yield acceptable throughput.

I'll post an old howto we have for ppp setup. Don't worry about the v4.0 stuff....it's pretty much the same for V5.1* Tru64, but again, you may need to do some adjusting.

Good luck....
============================================

--------------------------------------------------------------------------------
HOW TO CONFIGURE PPP ON TRU64_UNIX V4.0
--------------------------------------------------------------------------------

The following instructions are intended to supplement the online or hardcopy
documentation on PPP configuration, not to replace it.

Please read thru these instructions completely before beginning.

**NOTE: These instructions assume that you have already configured and tested
a modem connection on your system. If this has not been done, refer to the
the man pages on uucpsetup, the modem configuration procedure for Digital Unix.

(To test modem using tip)
1) make sure you have added a line to your /etc/remote file
such as : modem:dv=/dev/ttyd0:br#9600:pa=none:
Then issue the command #tip modem
atdt 5925555 (number of remote modem)
DO NOT PROCEED until you have made a successful connection to the remote modem.

Step 1: Verify that PPP support has been built into your kernel by issuing
the command:
#sysconfig -s | grep ppp
If ppp has not been built into your kernel, issue the command:
#sysconfig -c ppp

Step 2: Gather the following necessary information:
local host ip address
remote system ip address
network mask
tty device name (same one you tipped to)
baud rate (as in the /etc/remote file)
level of authentification

OUTGOING PPP CONNECTIONS (for incoming connections, skip to step 7 below)

Step 3: Insure that PPP passive is an enabled port characteristic if
connecting to a terminal server. Please refer to your terminal server configuration
documentation for the necessary setup instructions.
If connecting to a remote host, insure that that system has been
configured for dial in modem access, and has ppp support built into
its kernel. DO NOT PROCEDE until modem connectability has been
successfully tested on your remote terminal server port or host tty.

Now we can start up a ppp session!

Step 4: Establish a modem dial in session into your target system via tip.
Log into the remote machine and invoke the ppp daemon on
the remote system by issuing the command #pppd passive
(if the remote sysetm is a terminal server, issue the command:
local>connect ppp)





Step 5: In another window on the local system, issue the following command:
#pppd ttyd1 9600 16.66.80.205:16.66.80.205 netmask 255.255.255.0
(dev)(speed) (local ip:local ip) (mask)
NOTE: local ip address is used for both source and destination
address only when remote host is a terminal server. If the
remote host is a system, the syntax is as follows:
#pppd ttyd1 9600 16.66.80.205:16.66.80.42 netmask 255.255.255.0
(dev)(speed) (local ip:remote ip) (mask)

If you are dialing into an internet service provider that uses
pap for authentication, use the following ppp command:

# pppd +ua /passwdfile locip remip netmask /dev/ttyd1 38400

The +ua option tells pppd to use pap, and the /passwdfile is the file
that contains your username/password info. If the ISP is using DHCP,
you can leave off the locip, remip, and netmask.

It should be noted that with the next major release of Digital Unix
the +ua qualifier will no longer be supported. This switch allowed
the user to specify a username and password for logging into a
remote system or Internet Service Provider (ISP).

To specify a username and password the following example will show
the use of the /etc/ppp/pap-secrets file as the preferred method
for access control. The script below shows an example of the use
of the name keyword to work in conjunction with an entry in a
pap-secrets file. This name should also
be listed in the /etc/ppp/pap-secrets or /etc/ppp/chap-secrets file
depending on whether the remote system uses pap or chap security:

pppd /dev/tty00 19200 connect 'usr/ucb/chat -v "" "atdt{phone number}"
"CONNECT"' name smith defaultroute

The corresponding pap-secrets file would contain one or several entries
for various users:

miller * millers'_password
smith * smiths'_password
johnson * johnsons'_password

The man pages for pppd discuss the various forms that the fields in
the pap-secrets file can represent. These fields will contain
combinations of usernames, hostnames, host address and other strings.


Step 6: In the 'tip' window, do a ~. to kill the tip session. The ppp
session will remain active.

Optionally, you can use a 'chat script' to initate the tip session, start up the
remote ppp daemon, and initiate the pppd connect from the local system.
Included below is an EXAMPLE of what a chat script might look like.


#!/bin/sh
/usr/sbin/pppd connect '/usr/ucb/chat -v "" "atdt5925555" "CONNECT" "\r" "\#"
"secret" "ocal>" "c\sppp"' /dev/ttyd1 9600 -detach defaultroute 16.66.80.205
:16.66.80.205 netmask 255.255.255.0
exit 0


To verify that this ppp connection is working, netstat -i will show incoming
and outgoing ppp packets. You'll notice that there will be NO outgoing ppp
packets until you ping a remote node. You may have to add an entry into your
route table for the system you're pinging, to force it thru the modem line.
Or, when you issue your pppd connection initally, you can use the 'defaultroute'
option. Syntax would be as follows:
#pppd ttyd1 9600 defaultroute 16.66.80.205:16.66.80.42 netmask 255.255.255.0

INCOMING PPP CONNECTIONS

Step 7: Start a getty on the tty by adding an entry to /etc/inittab such as:

ppp:23:respawn:/usr/sbin/getty /dev/ttyd1 M9600 vt100

After editing /etc/inittab, have the system read the new entry by doing:

# init q

You should see a getty process on the tty.

Step 8: Dial in from the remote system, log in as a normal user, then:

$ pppd passive

This will start ppp on the tty. You can then start ppp on the remote
system to establish the connection.

Alternatively, if you are dialing into Digital UNIX from a system which
uses pap for ppp authentication (such as Windows 95) you will not want
to run a getty. Instead, start pppd from /etc/inittab, and leave it running
all the time:

ppp:23:respawn:/usr/sbin/pppd +pap -detach /dev/ttyd1 38400 login passive

The +pap option on pppd tell it to use pap for authentication, and the
login option tells it to use the /etc/passwd file for password
information (instead of /etc/ppp/pap-secrets). The -detach flag is
necessary to prevent init from respawning the process excessively.

Step 9: Now you can fill in the UNIX account information (username,
password) in the Dial-Up Networking/Connection dialog box in Windows 95, and
connect to the UNIX system. When you disconnect, the UNIX system will
respawn pppd and wait for another connection.

If you are having trouble establishing the ppp connection, you can
enable debugging by adding an entry to /etc/syslog.conf:

local2.debug /var/adm/syslog.dated/daemon.log

Then find the /usr/sbin/syslogd process and send it a hangup signal:

# ps ax | grep syslog
153 ?? S 0:35.88 /usr/sbin/syslogd
16986 ttyqc S + 0:00.01 grep syslog
# kill -1 153

Now you can start pppd with a "-d" flag and look in daemon.log for
messages.

For additional pppd options please review the online or hardcopy documentation
on ppp configuration.

If you have followed these instructions and still cannot establish a ppp link,
please refer to the ppp troubleshooting portion of the Network Administration
Guide, chapter 13.

If you are still encountering difficulties, please call the Digital Customer
Support Center at 1-800-354-9000 and ask for Unix Networking Assistance.

--------------------------------------------------------------------------------
Below is a sample ppp connection setup on a digital unix V4.0 system connecting
into a digital ds700 terminal server using a DECmodem V32 at 9600 baud.


============================================================================
!!! on the terminal server port, we see the following..
============================================================================
Local> show internet

Internet Address: 16.66.80.50
Subnet Mask: 255.255.255.0


Local> show port 3
Port 3:MYNAME Server: OSDMP3

Character Size: 8 Input Speed: 9600
Flow Control: CTS Output Speed: 9600
Parity: None Modem Control: Enabled
Stop Bits: Dynamic

Access: Local Local Switch: None
Backwards Switch: None Name: PORT_3
Break: Disabled Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT Default Menu: None

Preferred Service: None

Authorized Groups: 0
(Current) Groups: 0

Enabled Characteristics:
Autoconnect, Broadcast, Failover, Input Flow Control, Lock,
Loss Notification, Message Codes, Output Flow Control, Password, PPP,
SLIP, Verification

Local>
Local> show port 3 ppp ipcp
Port 3: MYNAME Server: OSDMP3

IPCP Characteristics:

IPCP: Enabled
Passive Open: Disabled
Restart Timer: 3 seconds
Max Configure: 10 transmissions
Max Terminate: 2 transmissions
Max Failure: 10 transmissions

IPCP Options: Local:

Negotiate Address: Disabled
Remote IP Address: 0.0.0.0
Compress Header: Disabled
Compress States: 16


Local>
Local> show port 3 ppp lcp char
Port 3: MYNAME Server: OSDMP3

LCP Characteristics:

LCP: Enabled
Passive Open: Disabled
Restart Timer: 3 seconds
Max Configure: 10 transmissions
Max Terminate: 2 transmissions
Max Failure: 10 transmissions

LCP Options: Local:

MRU: 1500
Character Map: FFFFFFFF
Authentication: Disabled
Link Quality: Disabled
Magic Number: Disabled
PF Compress: Disabled
ACF Compress: Disabled
FCS Size: 16 Bit


Local>
Local> change port 3 ppp ipcp host address 16.66.80.205


============================================================================
in window #1 of the digital unix system, we do the following...
============================================================================

# !tip
tip modem
connected
atdt5925555
CONNECT 9600

#
Network Access SW V1.4 for DS700-08 (BL91-32)

(c) Copyright 1994, Digital Equipment Corporation - All Rights Reserved

Please type HELP if you need assistance

Local> c ppp
Local -561- Starting SLIP or PPP datalink session~}#@!}!} } }$}-o~~}#@!}!}!} }$Q
5~


============================================================================
in window #2 fo the digital unix system, we do the following...
============================================================================

(note: a few previous informational command are given to show changes...
prior to starting up the pppd deamon)

# ifconfig ppp0
ppp0: flags=10

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ln0 1500 08:00:2b:3e:2e:3a 206319 0 215821 0 33
ln0 1500 DLI none 206319 0 215821 0 33
ln0 1500 16.66.96.96 16.66.96.105 206319 0 215821 0 33
sl0* 296 0 0 0 0 0
lo0 1536 19399 0 19399 0 0
lo0 1536 127 127.0.0.1 19399 0 19399 0 0
ppp0* 1500 250 12 1403 3 0

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.255.0
Inet 255.255.225.224

Route Tree for Protocol Family 2:
default 16.66.96.100 UG 11 139251 ln0
16.66.96.96 16.66.96.105 U 53 83193 ln0
127.0.0.1 127.0.0.1 UH 1 0 lo0

# pppd ttyd1 9600 16.66.80.205:16.66.80.205 netmask 255.255.255.0

# ifconfig ppp0
ppp0: flags=51
inet 16.66.80.205 --> 16.66.80.205 netmask ffffff00 ipmtu 1500

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ln0 1500 08:00:2b:3e:2e:3a 206487 0 215939 0 33
ln0 1500 DLI none 206487 0 215939 0 33
ln0 1500 16.66.96.96 16.66.96.105 206487 0 215939 0 33
sl0* 296 0 0 0 0 0
lo0 1536 19406 0 19406 0 0
lo0 1536 127 127.0.0.1 19406 0 19406 0 0
ppp0 1500 257 12 1403 3 0
ppp0 1500 16.66.80 16.66.80.205 257 12 1403 3 0

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.255.0
Inet 255.255.225.224

Route Tree for Protocol Family 2:
default 16.66.96.100 UG 11 139260 ln0
16.66.80.205 16.66.80.205 UH 1 0 ppp0
16.66.96.96 16.66.96.105 U 55 83306 ln0
127.0.0.1 127.0.0.1 UH 1 0 lo0

# route add -net 16.66.80 16.66.80.205 1
old usage of trailing digit, assuming route via gateway
add net 16.66.80: gateway 16.66.80.205

# ping 16.66.80.2
PING 16.66.80.2 (16.66.80.2): 56 data bytes
64 bytes from 16.66.80.2: icmp_seq=0 ttl=254 time=304 ms
64 bytes from 16.66.80.2: icmp_seq=1 ttl=254 time=303 ms
64 bytes from 16.66.80.2: icmp_seq=2 ttl=254 time=302 ms


----16.66.80.2 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 302/303/304 ms

# traceroute 16.66.80.2
traceroute to 16.66.80.2 (16.66.80.2), 30 hops max, 40 byte packets
1 osdmp3 (16.66.80.50) 203 ms 203 ms 202 ms
2 tsc (16.66.80.2) 206 ms 206 ms 204 ms
#

_____________________________________________________________________
If you have further questions or problems, please contact HP Customer
Support Center at 1-800-354-9000.
_____________________________________________________________________