[ Previous | Next | Contents | Search ]
AIXLink/X.25 1.1 for AIX: Guide and Reference

PAD for AIXLink/X.25 1.1.2 Running on AIX Version 4

There are three basic PAD features that are controlled by four new PAD configuration files located in the /etc/sx25pad directory:

The x29d daemon must be running for these features to work. You can start the daemon with flags for use with these features.

The four PAD configuration files are:

tty Defines TTY attributes. Default TTY attributes are in the "cooked" mode (for example, local echo, editing, etc.).
profile Defines PAD parameters. The default is transparent with some changes.
address Selects features based on address. The default uses the "cooked" tty mode and the default profile.
user Selects features based on user name. The default uses the "cooked" tty mode, the default profile, and all outgoing calls for all users.

Automatic Login

The automatic login feature is implemented by defining the login_user attribute in the address file with a value of an existing user name. When a call is received from a matching address, the call is automatically logged in as that user, instead of being presented with the normal system authentication method. For example:

31*:
   login_user = user1

automatically logs in any calls from an address beginning with 31 as user1 .

Automatic TTY and PAD Parameter Selection

The tty and profile files are used to define sets of parameters by name. These are then pointed to by the in_tty and in_profile attributes, respectively, in the user and/or address files. This allows the selection of any combination of host TTY and remote PAD parameters based on calling address, login user, or both. For example, if the following stanza exists in the tty file:

tty1:
   echo  = off
   vmin  = 1
   vtime = 1

and the following stanza exists in the user file:

user1:
   in_tty = tty1

any call that logs in as user1 has its TTY parameters set according to the values defined in the tty1 stanza in the tty file.

Since the in_tty and in_profile attributes can appear in either the user or address files, it is necessary to decide which should take priority if both are defined. By default, the user attribute has priority. For example, if both the matching address and user entries define in_tty or in_profile, the value is taken from the user file. However, this default prioritization can be changed by explicitly setting the priority of the attribute as follows:

attribute = value;priority

where priority is a decimal number, with lower numbers being more favored and 0 being the most favored priority. For example, assume the user file has the following stanza:

user1:
   in_tty = tty1

and the address file has the following stanza:

addr1:
   in_tty = tty2

If a call is received from addr1 and logs in as user1 , the TTY would be set according to the tty1 definition in the tty file. If, however, the address stanza looks like:

addr1:
   in_tty = tty2;0

all calls received from addr1 get the tty2 settings, regardless of which user they log in as.

Restriction of Outgoing Calls

The out_allow and out_deny attributes can be defined in the user file to control which addresses specific users can place PAD calls to. The attribute values can consist of patterns so that a complex set of addresses can be specified. In order for a call to succeed, the called address must match the out_allow attribute for the calling user, and it must not match the out_deny attribute.

For example, if the following stanza exists in the user file:

user1:
   out_allow = 31*
   out_deny  = 31[3-5]*

user1 is allowed to call any address starting with 31 , except for those starting with 313 , 314 , or 315 .

Note: The user file is shipped with the default stanza having the out_allow attribute set to  *  (the asterisk character), which permits all users without explicit entries in the user file to place calls to any address.
[ Previous | Next | Contents | Search ]