This chapter contains reference information for all available Solstice X.25 parameters. All of the parameters described here can be set by using x25tool, or by editing the configuration files.
Whenever possible, configure X.25 links and applications using the x25tool. Directly editing the files makes it more likely that errors will accidentally be added to the configuration files.
The parameters are grouped together functionally, according to the x25tool window that they are located in. The name of the corresponding configuration file or files is also included.
The name used to identify the parameter in x25tool is given as a header, with the keyword used by the configuration file included in brackets. In some cases no key word is used, but the configuration file itself will contain information on editing the parameters.
For a list of parameter values, refer to Appendix B, Parameter Values Quick Reference.
The parameters described in this section are located in the Link Editor window in x25tool.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
These parameters are used to configure a physical link.
A number that identifies the link (which is a connection over a specific network interface). This can be either a PSDN or LAN. Each link must have a unique number. This number is used to identify which link is being configured in various parts of x25tool.
This is an optional field. Enter an alphanumeric string of 80 or fewer characters. Spaces are allowed.
Table 7-1 lists the available values:
Table 7-1 Link Type values
Value |
Meaning |
---|---|
WAN (1988) |
A connection to a WAN conforming to the 1988 version of the X.25 Recommendations. |
WAN (1984) |
A connection to a WAN conforming to the 1984 version of the X.25 Recommendations. |
WAN (1980) |
A connection to a WAN conforming to the 1980 version of the X.25 Recommendations. |
LAN |
A connection to a LAN. |
MLP n - links |
A multi-link protocol connection using n physical links. |
The name of the link level device. Table 7-2 lists the available types:
Table 7-2 Device Types
Value |
Meaning |
---|---|
ZSH |
One of the onboard serial ports. |
HSI |
High Speed Interface. A serial port on the Solstice HSI/S SBus card. |
EXPX |
A serial port on the SCiiExpress-X card. |
WLOOP |
The loopback driver. |
LE |
An Ethernet interface on a SPARCstation. |
IE |
An Ethernet interface on a SPARCstation. |
BE |
A fast Ethernet interface. |
QE |
The SBus Quad Ethernet card. |
SMC |
A PC Ethernet interface. |
EL |
A PC Ethernet interface. |
ELX |
An Ethernet interface on the 3Com Etherlink III card. The default Ethernet interface type for a PC. |
SMCE |
A PC Ethernet interface. |
SMCEU |
A PC Ethernet interface. |
IEE |
A PC Ethernet interface. |
HEE |
A PC Ethernet interface. |
IEEF |
A PC Ethernet interface. |
EEPRO |
A PC Ethernet interface. |
NEI |
A PC Ethernet interface. |
RI |
A PC Ethernet interface. |
XP |
A PC Ethernet interface. |
PCN |
A PC Ethernet interface. |
FDDI |
An FDDI interface. |
TR |
A Token Ring interface. |
For the x86 version of the product, the device type depends on the type of Ethernet card used by your PC. The default ELX-0 applies to the 3Com Etherlink III card. If IP is running, you can find out what device type your PC uses by entering the following command: Included in the information returned by this command is the name of the device that IP is running over. Use this same device type for X.25.
hostname% ifconfig -a
The list of device types available for the x86 version of the product is constantly being updated. Therefore, your PC may use a device that is not shown in Table 7-2. If this is the case, you can add the new device to the device types list in the Boards Definition window. See "Definition" for more information.
The port number of the LAN or WAN device used beneath X.25. The Device Type plus the Port Number must form a unique identifier for each link.
Set this to either External, or specify the appropriate bit rate (in x25tool, you select the bit rate from the drop down menu). If you choose External, both the transmit clock and receive clock are set to external This means that the clocking speed is provided by a synchronous modem or modem eliminator.
If you specify a bit rate, this means that the local machine supplies the clocking, so make certain that the bit rate you select matches the transmission rate of the local machine.
Window sizes can be in the range 1 to 7 for modulo 8 networks, or 1 to 127 for modulo 128 networks. The default must be less than or equal to the maximum.
This applies to WAN connections only. Choose between DTE and DCE. If you are connecting to a PSDN via a modem, the machine running the Solstice X.25 software is the DTE and the modem acts as the DCE. If you are connecting two machines back-to-back, make one the DTE and the other the DCE.
This applies to WAN connections only. Choose between LAP, LAPB and LAPBE. Almost all PSDNs use LAPB.
For WAN interfaces this is your DTE or DCE address, normally an X.121 address, consisting of a DNIC, NTN, and, optionally, a subaddress. Your service provider should notify you of what this address is. A small number of public networks require that the calling address in an outgoing packet not contain the full X.121 address (for example, Transpac only requires the sub-address). In such a case, enter the "short" version of your X.121 address (as specified by your service provider) in this field. Your service provider will inform you if you need to do this.
For LAN interfaces, this is a six-byte (12 hexadecimal) digit address. The default of twelve zeroes tells Solstice X.25 to use your machine's default MAC address. To use the MAC address stored on an interface controller card (such as the address on the FDDI/S SBus card) enter the address as twelve consecutive hexadecimal digits or as pairs of hexadecimal digits, with colons between each pair and leading zeroes within pairs omitted.
The version of the X.25 Recommendation that your PSDN conforms to--1980, 1984, or 1988.
Sets the packet size for all priority call requests and incoming calls. Possible values are: Default, 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096.
In the configuration file, packet sizes are expressed as powers of 2. For example, to specify 128, enter 7.
Consult your service provider to find out the correct logical channel ranges to use. For each type of virtual circuit you use, you must set the channel ranges so that they match the range of numbers specified by your PSDN. For back-to-back or LAN connections, you must match the logical channel numbers used by the remote hosts with which you intend to communicate. Mismatches between logical channel number ranges are frequently the cause of inability to establish connections. A common symptom of an LCR mismatch is that connections operate in one direction only.
You can access the LAPB and WAN Parameters window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
Use the LAPB and WAN Parameters screen to configure the datalink and physical layer parameters used by a LAPB link.
The LAPB layer parameters are:
The period, in tenths of a second, during which the LAPB software expects to receive an acknowledgment to an outstanding I-frame or during which LAPB expects a response to a sent unnumbered frame. The valid range for values of this parameter is between 1 and 3000.
The period, in tenths of a second, during which the LAPB software expects to receive a frame with the F-bit set to 1 in response to a command with the P-bit set to 1. This value should be less than that specified for the Ack Timer. The valid range for values of this parameter is between 1 and 3000.
The period, in tenths of a second, during which the LAPB software expects to receive a reply to a sent Reject frame. The valid range for values of this parameter is between 1 and 10000.
The period, in tenths of a second, during which the LAPB software waits for an indication of the clearance of a busy condition at the other end of the link. The valid range for values of this parameter is between 1 and 30000.
The period, in tenths of a second, during which the LAPB software expects to receive a frame from the other end of the link. If this timer expires, the Poll/Final cycle--which might result in link disconnection--is initiated. A zero value disables this function. The valid range for values of this parameter is between 0 and 32000.
The maximum delay, in tenths of a second, before transmitting a delayed Receiver Ready. The value for this parameter must be significantly lower than the Ack Timer value. The valid range for values of this parameter is 0 to 3000.
The maximum number of times that an I-frame (information frame) is sent following the expiration of the Ack Timer, the P-bit Timer, or the Reject Timer. It also limits the number of times Receive Ready with P-bit set is sent when the remote side is busy and the Busy Timer expires. The valid range for values of this parameter is 1 to 255.
The maximum number of unacknowledged I-frames that can be received before the Receive Ready acknowledging those I-frames must be sent. The valid range for values of this parameter is 0 to 127 for modulo 128, and 0 to 7 for modulo 8.
The position within a window at which the LAPB software sends an I-frame with the P-bit set, to ask for an acknowledgment from the receiver. The valid range for values of this parameter is 0 to 127.
This parameter appears in the LAPB and WAN Parameters window when the Link Type is set to MLP in the Link Editor Window. In this instance, to access the LAPB and WAN Parameters window, you must call up the MLP Parameters window, then double click on the SLP you want to configure. For more information, see "MLP Parameters".
This parameter defines how many unacknowledged frames can be sent on one line before the next line is used. Setting this correctly forces traffic to be distributed between the lines in an MLP link. The values you set depend on the absolute speed of each line, and on the relative speeds of your lines. In general, don't set an MLP Priority of less than 3. If your lines operate at 64kbps, or more, you should increase the MLP Priority.
The following combinations of values provide efficient (90%) line use in two-line MLP configurations:
For two 64Kbps lines, set the MLP Priority for each line to 10. In the MLP Parameters window, set the MLP Window and MLP Guard to 25. See "MLP Parameters" for more information.
For one 512Kbps line and one 128Kbps line, set the MLP Priorities to 30 and 5, respectively. In the MLP Parameters window, set the MLP Window to 40. See "MLP Parameters" for more information.
When the connection is in an Error state, ignore any Unnumbered acknowledgment frames received.
When the connection is in an Error state, retransmit a Frame Reject if one is received.
When the connection is in an Error state, transmit a Frame Reject if an invalid Frame Response is received.
If an S-frame is received without the P-bit set, send a Frame Reject.
Do not transmit a DM on entry to the ADM state.
Abandon X.32 registration if a SABM is received.
Run the link so that it is conforms exactly to the specifications in the ISO 8882 standard.
When the Solstice X.25 software comes up, the link is off. To switch it on subsequently, use the linkstart command.
When this is set to Yes, an X.32 identity and signature can be configured for a subnetwork. X.32 authentication procedures are used with dial-up configurations to prevent people from dialing in without permission This is a client-only implementation of X.32.
An X.32 signature of up to 32 hexadecimal characters. Do not use whitespace.
An X.32 identity of up to 32 hexadecimal characters. Do not use whitespace.
The physical layer parameters for a single LAPB link are:
The type of calling procedure to use: None or V25bis.
Set this if you are using the V.25 Calling Procedures. This timeout is only needed if the network does not support call fail indications. The valid range for values for this parameter, in tenths of a second, is between 60 and 300.
You can access the LLC2 Parameters window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
The parameters described in this section configure the datalink and physical layers of a LAN link.
The period, in tenths of a second, during which the LLC2 software expects to receive an acknowledgment to an outstanding I-frame. The valid range for values of this parameter is between 1 and 3000.
Maximum number of times the LLC2 software sends a PDU following the expiration of the Ack Timer, the P-bit Timer, or the Reject Timer. The value of this parameter also limits the number of times Receive Ready with P-bit set is sent when the remote side is busy and the Busy Timer expires. The valid range for values of this parameter is between 1 and 255.
The period, in tenths of a second, during which the LLC2 software expects to receive a frame with the F-bit set to 1 in response to a command with the P-bit set to 1. This value should be less than that specified for the Ack Timer. The valid range for values of this parameter is 1 to 3000.
The maximum number of unacknowledged I-frames that can be received before the Receive Ready acknowledging those I-frames must be sent. The valid range for values of this parameter is 0 to 127.
The period, in tenths of a second, during which the LLC2 software expects to receive a reply to a sent Reject frame. The valid range for values of this parameter is 1 to 10000.
The position within a window at which the LLC2 software sends an I-frame with the P-bit set, to ask for an acknowledgment from the receiver. The valid range for values of this parameter is 0 to 127.
The period, in tenths of a second, during which the LLC2 software waits for an indication of the clearance of a busy condition at the other end of the link. The valid range for values of this parameter is 1 to 3000.
The period, in tenths of a second, during which the LLC2 software expects to receive a frame from the other end of the link. If this timer expires, the Poll/Final cycle is initiated. A zero value disables this function. The valid range for values of this parameter is 0 to 32000.
The maximum delay, in tenths of a second, before transmitting a delayed Reset Request. The value for this parameter must be significantly lower than the Ack Timer value. The valid range for values of this parameter is between 0 and 3000.
This determines the receive window size. That is, the maximum number of unacknowledged I-frames that the remote end of the link can send. The valid range for values of this parameter is 1 to 127.
This indicates the number of times the LLC2 software tries to find stations with duplicate MAC addresses. A value of 0 means no attempt is made. The valid range for values of this parameter is 0 to 255.
The period, in tenths of a second, during which incoming XID response frames are checked for a duplicate response to the station LSAP. A value of 0 tells the LLC2 software not to perform the duplicate address check. The valid range for values of this parameter is 0 to 3000.
You can access the MLP Parameters window from the Link Editor. The MLP Parameters window is divided into two sections. The first section contains parameters that apply to the multiple link in general. The second section contains a list of the physical ports that are associated with each link.
You can access the MLP Parameters window only when the Link Type is set to MLP in the Link Editor window.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
The parameters described in this section configure the additional datalink parameters for an MLP link.
The maximum number of outstanding unacknowledged frames allowable. This should be larger than the total of the MLP Priority values. The valid range for this parameter is 0 to 4095.
All of the machines connected to the same network must use the same MLP Window size. If you are connecting to a PSDN, check with your service provider to find out the appropriate MLP Window size to use. This may restrict the MLP Priority values that you can set, as the total of the MLP Priority values must not be greater than the MLP Window size.
The maximum number of times that MLP attempts to send a frame to an SLP without receiving an acknowledgment. The valid range for this parameter is 1 to 255.
The time, in tenths of a second, during which MLP expects to receive an acknowledgment to an outstanding frame. The valid range for this parameter is 1 to 3000.
The time, in tenths of a second, during which MLP waits for system resources, for example buffer space, to become available before declaring a frame as blocked and dropping it. The valid range for this parameter is 1 to 3000.
The length of the timer, in tenths of a second, that determines how long the DTE waits for confirmation from the DCE that it has reset. The valid range for this parameter is 1 to 3000.
In x25tool, the physical ports associated with the link are displayed in the bottom half of the MLP Parameters window. Double clicking on a port here brings up the LAPB and WAN Parameters window described in "LAPB and WAN Parameters". You need to configure the parameters for each SLP that is associated with the link.
To access the Addressing parameters window from x25tool, click on the Addressing button in the Link Editor window. The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
Choose None (the default), OSI, or non-OSI. This is the type of extended address you use in the network to which the link you are configuring is attached. Not available for WAN (1980) link types.
Enter a hexadecimal address of 40 digits or fewer. Not available for WAN (1980) link types.
The following parameters apply to LAN addresses, only.
This applies to LAN connections, only. It is a one-byte (two-hexadecimal-digit) address. The default of 7e is the standard SAP for LLC2 under X.25.
This applies to LAN connections only. It is a one-byte (two-hexadecimal-digit) address. The default of 70 is the standard loopback SAP for LLC2.
It is the maximum number of simultaneous connections to be made over this link.
You can access the Closed User Groups and Facilities window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
Choose any of the settings, listed below, that correspond to the CUG options to which you subscribe.
CUG, no other access
Preferential CUG
CUG, with outgoing access
CUG, with incoming access
Reject incoming CUG calls
Choose either Basic or Extended.
Choose any of the settings, listed below, that correspond to PSDN facilities to which you subscribe.
Bar TOA/NPI Addressing
Bar Outgoing during X.32 registration
Choose Request size negotiation or Disallow size negotiation or neither.
If you select Request size negotiation, outgoing calls automatically contain packet and window size negotiation. Incoming calls are negotiated if they contain packet and window size negotiation.
If you select Disallow size negotiation, incoming calls containing packet and window and size negotiation are rejected.
If you select neither option, outgoing calls will not contain any packet or size negotiation information. However, incoming calls with packet and size negotiation information will still be accepted.
The options for Fast Select are With no restriction on response and With restriction on response. You can select one or both options. With no restrictions allows incoming fast select calls with no restriction on response. With restrictions allows incoming fast select calls with restriction on response. When these options are selected together, all incoming fast select calls are allowed.
You can access the Link Modes parameters window from the Link Editor window.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
These parameters deal with options and requirements of the PSDN to which you are connecting.
Allow the omission of the diagnostic byte in incoming Restart, Clear and Reset Indications.
Force the use of the diagnostic byte in incoming Restart, Clear and Reset Indications.
Restrict the length of a Clear Indication to 5 bytes and Clear Confirm to 3 bytes. This parameter only applies to 1980 networks.
Disallow the use of the diagnostic byte in incoming Restart, Clear, and Reset Indications.
Some PSDNs use channels other than zero to transmit diagnostic information. This parameter lets you discard this information, should you need to.
Use this parameter if you want to be able to use addresses that do not conform with the X.121 specification.
Only the superuser can start a process, like the PAD daemon, that "listens".
This parameter is for test purposes only.
Includes X.121 address in X.25 packet.
Inserts the X.121 address into Call Indications.
Apply the rules used by the 1976 Datapac recommendations to calls.
Some networks let you give priority to international calls. If you set this parameter, you need to set Priority Encoding. See Table 7-3 for information.
The value of this parameter determines Solstice X.25's action with respect to prioritizing international calls.
Table 7-3 lists the available choices:
Table 7-3 Priority Encoding
Priority Encoding Parameter |
Parameter Value |
Meaning |
---|---|---|
No special action |
0 |
Solstice X.25 performs no special encoding. |
1 |
The software encodes the priority request using the DATAPAC Priority Bit (1976 version). |
|
2 |
Priority request encoded using the DATAPAC Traffic Class (1980 version using the Calling Network facility marker). |
The value of this parameter determines how outgoing international calls are handled.
Table 7-4 lists the available choices:
Table 7-4 Outgoing International Call Parameters
Outgoing International Call Parameter |
Parameter Value |
Meaning |
---|---|---|
Not distinguished: |
0 |
No special action taken for international calls. |
1 |
Solstice X.25 compares the DNIC in the called address to the local DNIC. The software assumes that a mismatch indicates an international call. |
|
Prefix digit of 1 |
2 |
The software assumes a called address with a prefix of 1 indicates an international call. |
Prefix digit of 0 |
3 |
The software assumes a called address with a prefix of 0 indicates an international call. |
Enter your national DNIC number. You must enter this code if you choose Check National DNIC in the Outgoing International calls menu.
This sets the packet size for all priority call requests and incoming calls. The possible values are: Default, 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096.
In the configuration file, the packet sizes are expressed as powers of 2. For example, to specify 128, enter 7.
Determines the value inserted in the calling address field of outgoing call requests over a WAN link. It does not apply to LAN links.
The choices as shown in Table 7-5 are:
Table 7-5 Source Address Control Parameters
Source Address Control Parameter |
Parameter Value |
Meaning |
---|---|---|
No special action |
0 |
Solstice X.25 puts the calling address in the outgoing call request exactly as it receives it from an application making the call. |
Omit calling address |
1 |
Solstice X.25 sets the calling address to null in the outgoing call request, regardless of what was specified by the calling application. |
Default to local address |
2 |
Solstice X.25 uses the local address as the calling address if no calling address is supplied by the application. |
Force use of local address |
3 |
Solstice X.25 uses the local address as the calling address, even if a calling address is supplied by the application. |
The term local address refers to the value of the Local Address parameter in the Interface Configuration window.
If you plan to use one or more permanent virtual circuits (PVCs) you can specify different local and remote packet and window sizes for each PVC.
The PVC options are only available for LAPB links. You only need to use them if you plan to use one or more permanent virtual circuits (PVCs) to connect to your X.25 network and you require different packet and window sizes for the PVCs than those used for switched virtual circuits on the same link.
You can access the PVC Options window from the Link Editor.
The PVC parameter values are stored in the configuration file /etc/opt/SUNWconn/x25/pvcmapconf.
In x25tool, to access the PVC window you must first enter values for PVC minimum and maximum in the Logical Channel Range section of the Link Editor, and then click on Apply.
The PVC Options window displays a list of PVC numbers for the currently selected link. To add a PVC, click on Add, then edit the options. Once you have configured the options to meet your requirements, click on Apply. The parameters for the PVC will be added to the displayed list.
To modify an existing PVC, click on the appropriate PVC number in the displayed list of PVC parameters. Edit the options as required and click on Apply.
The number of the PVC you want to configure.
The local packet size. Choose from 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096. In the configuration file, the packet sizes are expressed as powers of 2. For example, to specify 128, enter 7.
The remote packet size. Choose from 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096. In the configuration file, the packet sizes are expressed as powers of 2. For example, to specify 128, enter 7.
The local window size. Enter a number in the range 1 to 7 for modulo 8 networks, or 1 to 127 for modulo 128 networks.
The remote window size. Enter a number in the range 1 to 7 for modulo 8 networks, or 1 to 127 for modulo 128 networks.
You can access the Throughput Class and Packet Sizes window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
The Throughput Class and Packet Sizes window allows you to set values for throughput class parameters and to set Layer 3 (network layer) window and packet sizes.
The standard range for throughput class, as specified in ISO 8208, is 3 through 12, corresponding to a range of 75 to 48000 bps. However, Solstice X.25 supports 0 through 15, allowing for non-standard X.25 network implementations. If you connect to a non-standard network, use the throughput class options in the Special Parameters window (see "Special Parameters") to specify values for that network. If you need to use non-standard values, your service provider should tell you what they are.
Allows for configuration for non-standard X.25 networks, such as TELENET (a US network). The default (No) is the appropriate choice for the vast majority of network connections. When set to No, negotiation is towards mutually acceptable minima, rather than the default values.
This determines the maximum size (in bytes) to which packets with the M (more data) bit set can be concatenated. This parameter has a range of values from 1 to 32000. The default maximum size is 256.
Set to modulo 8 or modulo 128 according to whether your network uses packet sequence numbers ranging from 1 to 7 or 1 to 127.
You need to specify the Default and Maximum packet sizes for the local and remote networks. Window sizes can be in the range 1 to 7 for modulo 8 networks or 1 to 127 for modulo 128 networks. The default must be less than or equal to the maximum.
You can access the Timers and Counters window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
These parameters set CCITT-defined timers. The values are:
This timer starts when the DTE issues a Restart Request. It terminates when the DTE receives a Restart Confirmation or a Restart Indication. If neither is received in the time allowed, the DTE retransmits the Restart Request. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The recommended value is 1800.
This timer starts when the DTE issues a Call Request. It terminates when the DTE receives a Call Connected, Clear Indication or Incoming Call. If none of these are received in the time allowed, the DTE issues a Call Request. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The recommended value is 2000.
This timer starts when the DTE issues a Reset Request. It terminates when the DTE receives a Reset Confirmation or a Reset Indication. If neither is received in the time allowed, the DTE retransmits the Reset Request or sends a Clear Request. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The recommended value is 1800.
This timer starts when the DTE issues a Clear Request. It terminates when the DTE receives a Clear Confirmation or Clear Indication. If neither is received in the time allowed, the DTE retransmits the Clear Request. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The recommended value is 1800.
This timer does not exactly match the DTE Window Status Transmission Timer, T24. Instead, it specifies the maximum time for which data received from the remote side can remain unacknowledged due to a flow control condition. After expiration of this timer, any outstanding acknowledgments are carried by an X.25 Receive Not Ready packet. This timer makes sure that the remote side not receiving an acknowledgment does not cause resets within the virtual circuit. This timer should be about half the value of Window Rotation (see next section). The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The default value is 600.
This timer starts when the DTE transmits a data packet, or the DTE's window is rotated, but there are still outstanding data packets. It terminates when there are no outstanding data packets in the window. If this does not happen within the allowed time, the DTE initiates an error procedure by transmitting a Reset Request with diagnostic 0x92. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The default value is 2000.
This timer start when the DTE sends an Interrupt packet. It terminates when the DTE receives an Interrupt Confirmation. It this is not received in the time allowed, the DTE transmits a Reset Request. The valid range for values of this parameter, in tenths of a second, is 0 to 32000. The default value is 1800.
The ISO Registration Request timer. The valid range for values of this parameter, in tenths of a second, is 0 to 32000.
Specifies the maximum time during which a pending acknowledgment is withheld. Solstice X.25 tries to suppress the generation of Layer 3 Receiver Ready control packets. Acknowledgment carried by data or multiple acknowledgments is preferred to each data packet being explicitly and separately acknowledged. The valid range for values of this parameter, in tenths of a second, is 1 to 32000.
The period in which the DTE/DCE resolution should be completed. This prevents two packet-level entities failing to resolve their DTE/DCE roles. When this timer expires, the link connection is disconnected and all pending connections aborted. The valid range for values of this parameter, in tenths of a second, is 0 to 32000.
The period, in tenths of a second, over which Solstice X.25 maintains an idle link-level connection. For a WAN dial-up, the idle disconnect period should not be set to zero. For LANs, the default is 600.
The number of Restart Requests that will be sent before the link is assumed to be down. The allowable range is 1 to 255. The default is 1. Make sure you set a value that is high enough to cope with lost traffic and network delays, but low enough to resolve problems with little disruption to users.
The number of Clear Requests that will be sent before the link is assumed to be down. The allowable range is 1 to 255. The default is 1. Make sure you set a value that is high enough to cope with lost traffic and network delays, but low enough to resolve problems with little disruption to users.
The number of Reset Requests that will be sent before the link is assumed to be down. The allowable range is 1 to 255. The default is 1. Make sure you set a value that is high enough to cope with lost traffic and network delays, but low enough to resolve problems with little disruption to users.
The number of Registration Requests that can be sent without acknowledgment. The allowable range 1 to 255. The default is 1.
The maximum period in milliseconds by which transmission can be delayed due to internal processing. The allowable range is 0 to 32000 milliseconds. The default is 5.
The maximum period in milliseconds by which transmission can delayed due to the effects of line transmission rate. The allowable range is 0 to 32000 milliseconds. The default is 5.
You can access the Special Parameters window from the Link Editor.
The parameter values are stored in the link configuration files /etc/opt/SUNWconn/x25/config/link_config_nnnn.cfg, where nnnn is the four-digit number that indicates the link number (for example, the file link_config_0004.cfg contains the parameters for link number 4).
Use these parameters to set values for D-bit options and throughput class. The throughput class parameters are only for those X.25 networks that do not use standard X.25 packet and window size negotiation.
The following parameters are available:
Determines Solstice X.25's response when it receives a Call Accept packet with the D-bit set and end-to-end acknowledgment was not requested. The options are:
Leave D-bit set
Clear call
Zero D-bit
Determines Solstice X.25's response when it sends a Call Accept packet with the D-bit set and receives a packet from the remote side with the D-bit turned off. The options are:
Leave D-bit set
Clear call
Zero D-bit
Determines Solstice X.25's response when it receives a Data packet with the D-bit set. The options are:
Leave D-bit set
Reset call
Zero D-bit
Determines Solstice X.25's response when an application tries to send a data packet with the D-bit set. The options are:
Leave D-bit set
Reset call
Zero D-bit
The values are:
Normal Negotiation
Use Low Nibble of Map
Use High Nibble of Map
Use Both Nibbles of Map
If you are connecting to a non-standard X.25 network and the map entry of 0 is not appropriate for your X.25 network, choose a value between 1 and 15.
The range for valid packet sizes is 16 to 4096.
In the configuration file, packet sizes are expressed as powers of 2. For example, to specify 128, enter 7.
A number in the range from 1 to 127.
An X.32 identity of up to 32 hexadecimal characters. Do not use whitespace.
Solstice X.25 can route IP if you set up a mapping between IP and X.25 (X.121) addresses. In x25tool, the parameters for IP over X.25 configuration are divided into two windows: the IP Interface Configuration window and the Remote IP Host to X.25 Address Map. To access one of these windows, from the Services menu, click on IP and select either IP Interface or IP Mapping.
The parameter values are stored in the configuration files /etc/opt/SUNWconn/x25/ipconf and /etc/opt/SUNWconn/x25/ixemapconf.
Enter an IP address in either name or numeric form.
Choose between point-to-multipoint, or point-to-point.
For point to multipoint networks, this is "IP Subnet Mask"; for point-to-point networks, the item is "Remote IP Address".
For IP Subnet Mask: The mask number used in the specified IP network, expressed in IP dot notation. For example: 255.255.255.0, indicates a Class C subnetwork mask. Enter + to use the local default.
For Remote IP Address: The IP address, in name or numeric form, for the host at the remote end of the point-to-point connection.
This sets the maximum transmission unit size for the network service access point that the IP protocol will use to transmit data over X.25.
The MTU value you set here must be smaller than the NSDU value specified under Packet Size in the Throughput window.
The following X.25 parameters are related to the IP interface. In most cases you will not need to modify the default values.
Specifies the pattern of digits Solstice X.25 uses to match the called address on incoming calls for IP. The options are:
Starts with: Solstice X.25 accepts calls from callers that have called addresses that have leading digits that match the string of hexadecimal digits you enter here.
Matches: Solstice X.25 accepts calls from callers that have called addresses that exactly match the string of hexadecimal digits you enter here.
Don't care: Solstice X.25 accepts calls from any caller, regardless of its called address.
If you choose Starts with or Matches, enter a string of digits to be matched.
Choose between CCITT, DDN Basic and DDN Standard. These options are alternative ways of mapping between IP and X.25 addresses.
Specifies the pattern of digits Solstice X.25 uses to match the Call User Data on incoming calls for IP. X.25 software uses the first 2 digits of the call user data (CUD) field to distinguish between PAD and IP calls. The CUD field of a PAD call always begins with 01. The CUD field of an IP call always begins CC. If you want to add any further CUD to be used in outgoing PAD calls, make sure you append it to the 01. Do not delete the 01--if you do, the X.25 software receiving the call will not know which application to pass it to and the call will fail.
The options are:
Starts with: Solstice X.25 accepts calls from callers that have CUD fields that have leading digits that match the string of hexadeciaml digits you enter here. The default of "Starts with" CC is the standard Call User Data value for IP over X.25 as specified in RFC 877.
Matches: Solstice X.25 accepts calls from callers that have CUD fields that exactly match the string of hexadeciaml digits you enter here.
Don't care: Solstice X.25 accepts calls from any caller, regardless of its CUD field.
If you choose Starts with or Matches, enter a string of hexadecimal digits to be matched.
This is the time in seconds that a connection must have been open before it can be closed (pre-empted). If all X.25 virtual circuits available to IP are in use and an IP packet arrives for transmission to a new destination, Solstice X.25 closes one of the existing connections--the one that has been idle the longest. The pre-emption timer determines the minimum time a connection must be open before it can be pre-empted in this way.
When setting this timer, take into account the amount of traffic on your link and the speed your link runs at. The default is suitable for links running at 9600 bps.
The minimum amount of time, in seconds, to wait before re-trying a call to a host after an unsuccessful call.
This is the time, in tenths of a second, that a connection to a given network can remain idle before being closed. This timer is configurable for each X.25 network to which you connect. When the disconnection timer expires, if there is no data on a connection, the virtual circuit to the X.25 network is closed. If data arrives from IP after this, the circuit is reopened.
When setting this timer, take into account the amount of traffic on your link and the speed your link runs at. The default is suitable for links running at 9600 bps.
The options are:
Acknowledge and discard: Acknowledge Reset Request packet and discard it.
Disconnect: Causes a Clear Request packet to be sent to remote host.
For expedited data, the menu options are defined as follows:
Acknowledge and discard: Acknowledge expedited data and discard it.
Disconnect: Disconnect connection in response to expedited data.
Reset connection: Reset connection in response to expedited data.
To restrict access, adding a measure of security, you can choose not to accept calls from unknown hosts, that is hosts who addresses are not in the Remote Host to X.25 Address Map.
Enter a link number specifying the link over which you reach the IP network specified in the IP Subnet Mask/Remote IP Address.
The IP address of the remote IP host, in either hostname or numeric form.
Set to either SVC (switched virtual circuit) or PVC (permanent virtual circuit). If this parameter is set to SVC, you will need to include the remote X.25 address. If this parameter is set to PVC, you will need to set the PVC number.
The X.25 (X.121) address of the specified remote host. If you are attached to the DDN, the X.25 address is generated using the IP address. You do not need to enter it here, although if you do other information you enter can be taken into account. If you do want to enter the X.25 address, you need to calculate it in the same way as the DDN software.
If you are using extended addressing, choose either OSI or non-OSI. Otherwise, choose None.
If you are using extended addressing, enter the OSI NSAP address or non-OSI address extension. An OSI NSAP address is 40 or fewer hexadecimal digits.
The size of the X.25 packet that will carry IP datagrams. In accordance with RFC 877, when IP datagrams are longer than the X.25 packet size, Solstice X.25 uses the M-bit to transmit the datagrams as complete packet sequences. Fragmentation of IP datagrams occurs only if the size of an IP packet exceeds the maximum transmission unit (MTU) size for a given subnetwork.
This parameter applies to calls in both directions and should not be larger than the window size value you specified for X.25.
Determines whether the software will request reverse charging when proposing calls to the remote host.
A four-digit number that provides networks between you and the remote host with additional routing information. You can have up to four RPOA numbers. If you have multiple RPOA numbers, enter them together in the same sequence of digits, with no spaces between.
Possible values are none, multi-user and bilateral CUG.
If your host is a member of a multi-user or bilateral CUG, enter the CUG number.
In x25tool, the parameters for the PAD Hosts Database can be accessed through the Services menu.
The parameter values are stored in the configuration files: /etc/opt/SUNWconn/x25/padmapconf, /etc/opt/SUNWconn/x25/x29profile, and /etc/opt/SUNWconn/x25/xhosts.
The PAD Hosts Database contains information about remote hosts that makes it easier for users to make PAD calls to them.
Default values for these parameters can be configured on a per-call basis. See Solstice X.25 9.2 PAD User's Guide. The parameters are:
The DTE or LSAP address of the remote host. A DTE address is of 15 or fewer decimal digits. An LSAP is 14 hexadecimal digits in length. In most cases, the last two digits of an LSAP (the SAP) are 7e. The x25tool program accepts ARP-style notation, with colons separating the bytes within an LSAP address. Within a colon-delimited byte, you can omit a leading zero.
Choose None (the default), OSI, or non-OSI. This is the type of extended address you use in the network to which the link you are configuring is attached. Extended Addressing is not available if your call is traversing a 1980-type WAN.
Enter a hexadecimal address of 40 digits or fewer. This feature is not available if your call is traversing a 1980-type WAN.
A PAD user can substitute any aliases entered here for the host name of a remote host when making a PAD call.
Choose Automatic or Specified. Automatic uses the Solstice X.25 routing (link selection) feature. If you choose Specified you must specify the link number yourself.
The link over which PAD makes calls to the specified remote host. This parameter only applies if you have multiple links.
Profile names refer to specific sets of PAD (X.3) parameter settings. If the Simple profile (the default) is not appropriate for the specified remote host, choose one of the other named profiles. Your network provider should tell you which profile you need to use.
If none of the seven profiles provided with the product suits your needs, you can modify some or all of the 22 parameters defined in the 1988 CCITT X.3 recommendation. See "X.3 Parameters" for more information.
A string of up to 124 ASCII characters that the PAD software will include in Call Request packets.
This is a number determined by the requirements of your remote host and PSDN. If your packet sizes are different from the default of 512, press MENU in the Local (or Remote) Packet Size button and select the packet size appropriate for your remote host.
This is determined by the requirements of your PSDN and your remote host.
If your host is a member of a Closed User Group, choose the appropriate CUG type.
If your host is a member of a multi-user or bilateral CUG, type the CUG number here.
Specifies the year of the X.29 recommendation supported by the remote host. Default means that you use the X.25 type specified for a given link.
Determines whether Fast Select is in effect for the calls to the specified host. If you enter more than 12 characters of Call User Data, the PAD software automatically uses Fast Select, regardless of the setting here. For more information on Call User Data, see "Call User Data".
In 7-bit mode (the default), characters are seven bits long and parity is filtered. In 8-bit mode, characters are eight bits long with no parity.
Determines whether the PAD software can make reverse charge calls.
A four-digit number that provides networks between you and the remote host with additional routing information. You can have up to four RPOA numbers. If you have multiple RPOA numbers, enter them together in the same sequence of digits, with no spaces between.
In x25tool, the parameters for the PAD Data Listen Database can be accessed through the Services menu.
The parameter values are stored in the configuration file: /etc/opt/SUNWconn/x25/paddconf.
The PAD daemon handles incoming PAD calls. Some parameters are available on a per-host basis as well as globally. The per-host parameters override any global settings.
When set to Yes, information about each PAD call made is logged to the file /var/opt/SUNWconn/x25/x29serverlog. This file can become very large. If you have problems with disk space, check the size of x29serverlog and, if necessary, delete it.
Setting this to No prevents this system from accepting incoming PAD calls. The system can still make outgoing calls.
The command that the PAD daemon invokes automatically when a connection is established with an incoming PAD caller. By default, the initial command is /bin/login.
A string that the PAD daemon displays to incoming PAD callers. Enter 80 or fewer alphanumeric (including whitespace) characters. If you do not set a string, the default is Solstice X.29 Terminal Services. The new Welcome Banner comes into effect the next time you restart the PAD Daemon.
In native mode the default parameter settings are: echoing disabled, data forwarding timeout enabled, no line folding, and local editing disabled. If you set this to Customize in PAD Daemon Listen Database, the X.3 Parameters window is activated. See "X.3 Parameters" for more information.
In non-native mode the default parameter settings are: echoing on, data forwarding disabled, no line folding, and editing disabled. If you set this to Customize in PAD Daemon Listen Database, the X.3 Parameters window is activated. See "X.3 Parameters" for more information.
Specifies the pattern of digits the PAD daemon uses to match the called address on incoming PAD calls. The options as shown in Table 7-6 are:
Table 7-6 Called and Calling Address Parameters
Parameter |
Meaning |
---|---|
Starts with |
The PAD daemon accepts calls from PAD callers that have called addresses that have leading digits that match the string of digits you enter here. |
Matches |
The PAD daemon accepts calls from PAD callers that have called addresses that exactly match the string of digits you enter here. |
Don't care |
This is the default parameter. The PAD daemon accepts calls from any PAD caller, regardless of its called address. You do not enter a string of digits with this parameter. |
Pattern |
Allows the use of standard wildcard characters in order to match on part of an address. Select this option to use the style of addressing used by SunNet X.25 7.0. |
If the Called Address is not set to Don't Care, you also need to use the Address is parameter to specify the type of called address.
Specify the type of the called address. If the called address is not a DTE address (the default), click on NSAP.
Specifies the pattern of digits the PAD daemon uses to match the calling address on incoming PAD calls. The options are explained under Called Address, above. You also need to use the Address is: parameter to specify the type of the calling address. If the Called Address is not set to Don't Care, you also need to set the Address is: parameter to DTE or NSAP extension.
Specifies the pattern of digits the PAD daemon uses to match the Call User Data on incoming PAD calls. By convention this is 01. Do not delete the 01 that appears in this field unless you are sure that your network uses a different value to distinguish incoming PAD calls. If this field is blank, or if the value entered is invalid, your machine will not be able to receive PAD calls.
The command that the PAD daemon invokes automatically when a connection is established with an incoming PAD caller. By default, the initial command is /bin/login.
A string that the PAD daemon displays to incoming PAD callers. Enter 80 or fewer alphanumeric (including whitespace) characters. If you do not set a string, the default is Solstice X.29 Terminal Services. The new Welcome Banner comes into effect the next time you restart the PAD Daemon.
The X.3 Parameters window is accessed when you select User-Defined from the PAD Profile window in the PAD Hosts Database, or when you select Customize under PAD Parameters in the PAD Daemon Listen Database.
If none of the seven profiles provided with the product suit your needs, you can modify some or all of the 22 parameters defined in the 1988 CCITT X.3 recommendation. Your network provider should tell you which values you need to set. The parameter numbering is in accordance with the X.3 Parameter standard.
Setting this parameter lets you configure a character to use to switch from the data transfer state to recall the PAD. Table 7-7 lists the possible values.
Table 7-7 Recall character values
Decimal Value |
Character Used |
---|---|
0 |
none |
1 |
DLE (Ctrl-P) |
32 - 126 |
user defined character |
Decimal values 2 to 31 (inclusive) have no effect.
If this is set to On, the PAD echoes characters back to the terminal, in addition to processing them.
The Dataforwarding characters tell the PAD that it has received a complete packet sequence, which it should assemble and forward. Possible values are:
A-Z, a-z, 0-9
CR
ESC, BEL, ENQ, ACK
DEL, CAN, DC2
ETX, EOT
HT, LF, VT, FF
Control characters not listed above
If your PSDN has supplied you with a numerical value, you need to find out which character sequence it defines.
Determines the interval PAD waits for after receiving at character. If no character is received by the end of this interval, the PAD assumes it has received a whole packet, and forwards it.
Determines the type of flow control used by the PAD on incoming data from the terminal. Make sure that this is the same type as is used by the terminal.
Set the decimal value according to the way you want PAD service signals to be handled. Table 7-8 lists the values and possible actions.
Table 7-8 PAD service signals
Decimal Value |
Action |
---|---|
0 |
no service signals transmitted to start-stop mode DTE |
1 |
service signals, other than the Prompt PAD service signal, are transmitted in standard format |
4 |
prompt PAD service signal transmitted in standard format |
8 - 15 |
PAD service signals transmitted in a network-dependent format |
Determines the action taken when the PAD receives a break signal. Choose from the list of available options. If your PSDN has supplied you with a numerical value, you need to find out which break action it represents.
Choose the value you want.
This lets you set the PAD to insert padding characters in the character stream after the occurrence of a carriage return. This lets the terminal process the carriage return correctly.
Determines how often the PAD inserts a Line Feed followed by a Carriage Return. In effect, this sets the line length for your terminal.
This displays the speed of the line connecting the PAD and the terminal. You cannot change this parameter.
Defines the type of flow control used by the terminal on incoming data from the PAD.
Determines when the PAD will insert a Line Feed character. This is only relevant when the PAD is in data transfer state. If your PSDN has supplied you with a numerical value, you need to find out which action it represents.
This lets you set the PAD to insert padding characters in the character stream after the occurrence of a line feed. This lets the terminal process the carriage returns correctly.
This provides for local editing during the data transfer state as well as during the command state.
This determines the ASCII character used as the Character Delete key. Enter the appropriate ASCII number.
This determines the ASCII character used as the Line Delete key. Enter the appropriate ASCII number.
This determines the ASCII character used to redisplay a line. Enter the appropriate ASCII number.
Specify whether you are using a video or hardcopy terminal. This affects how the PAD handles deletions.
Choose the appropriate echo mask. Possible values are:
All
Not CR
Not LF
Not VT, HF, FF
Not BEL, BS
Not ESC, ENQ
Not ACK, NAK, STX, SOH, EOT, ETB, ETX
Not chars from P16, P17, P18
Not <DEL> or other Ctrl chars
If your PSDN has supplied you with a numerical value, you need to find out which mask it represents.
Set the parity to None, Checked, Generated, or Checked and generated.
The PAD halts the display after the number of lines you specify here. Pressing the space bar displays the next page of data.
In x25tool, the parameters for the PAD Printer can be accessed through the Services menu.
The parameter values are stored in the configuration file: /etc/opt/SUNWconn/x25/xtpmapconf.
You can install a printer over an X.25 network so that users logged in remotely can print to their local printer.
Before you can print through PAD, you must use admintool to set up the printer. Do this as you normally would, but make certain that you set it up as a Local Printer, and specify an X25 printer port that also includes a unique printer number, for example /dev/xtp7. See User Account, Printers and Mail Administration for more information about using admintool.
Enter the name of the printer.
This is the printer port number. For example, if you entered /dev/xtp7 for the printer port in admintool, then the device number is 7.
Specify the link to use for the outgoing printer connection. If you set this to 255, the link number will be selected automatically.
Enter the destination X.121 address to use for establishing the virtual connection.
If Clear Flag is set to Yes, then a Clear Invitation packet will be sent at the end of the data transfer, and the connection will then be cleared by the remote PAD after all of the data is received. This ensures that all data have reached the remote PAD, but can lead to connection staying up if the remote does not support this feature.
If Clear Flag is set to No, then a Clear Invitation packet will not be sent at the end of the data transfer. If the remote PAD does not support Clear Invitation, you should set Clear Flag to No and enter a value for the Timeout.
This is the amount of time, in seconds, that the X.25 server will keep the connection open after the last print packet has been sent. Setting a timeout value can help prevent loss of print data, however, you will have to use your own knowledge of the network to determine how long the connection needs to stay open.
You only need to set a timeout if Clear Flag is set to No.
This is the call user data used to establish the virtual connection. Before this information is included, it should have been agreed upon by both sides of the connection.
In x25tool, the parameters for the NUI Mapping can be accessed through the Services menu.
The parameter values are stored in the configuration file: /etc/opt/SUNWconn/x25/nuimapconf.
The Network User Identifier parameters are used to create a mapping between Network User Identifiers and facilities. When a call is made using NUI override, the facilities set here override any other facilities that might otherwise apply to the call.
The Network User Identifier, a string of up to 64 alphanumeric characters.
Enter a number value for the throughput class to use for incoming (Remote) and outgoing (Local) calls. These can be different.
The sizes to use for incoming (Remote) and outgoing (Local) packets. These can be different.
Choose between Normal and Extended.
The window size to use for incoming (Remote) and outgoing (Local) calls. These can be different.
Whether Closed User Groups are in use. Choose between None, Normal and Outgoing.
Choose Basic or Extended.
In x25tool, you can configure the routing parameters in the Routing window, which can be accessed through the Services menu.
The parameter values are stored in the configuration file: /etc/opt/SUNWconn/x25/routes.
If you have multiple links, Solstice X.25 automatically selects a link for outgoing calls based on address information in a Call Request packet. The parameters for configuring this are:
Table 7-9 lists the available route types:
Table 7-9 Route Types
Type |
Meaning |
---|---|
Associates the complete X.121 address of a remote host with a link. This type of entry can include a MAC address. |
|
Associates the leading digits (one or more) of an X.121 address with a link. This type of entry can include a MAC address. |
|
Contains a link and an optional MAC address. This entry (there can be only one) is used if no match is found between a called address and any X.121 host or prefix entries. |
|
Associates the complete extended address (such as an OSI NSAP address) of a remote host with a link. This type of entry can include an X.121 address or a MAC address, and a protocol id. |
|
Associates the leading digits (one or more) of an extended address with a link. This type of entry can include an X.121 address or a MAC address, and a protocol id. |
|
Contains a link and, optionally, an X.121 or a MAC address, and a protocol id. This entry (there can be only one) is used if no match is found between a called address and any AEF host or prefix entries. |
The link number to be associated with a host address, an address prefix, or a default entry. This is the same number as you specified it in the Link Number item in the Link Editor window in x25tool.
For an X.121 host-type entry, enter a complete X.121 host address, as it would be specified in the called address portion of a Call Request packet. For an X.121 prefix-type entry, enter the leading digits (for example, the DNIC) of an X.121 address. For the optional portion of an AEF routing entry, enter a complete X.121 address.
For an AEF host-type entry, enter a complete extended address, such as an OSI NSAP address. For an AEF prefix-type entry, enter the leading digits (at least one) of an extended address.
A protocol id of no more than five bytes (10 decimal digits). A protocol id is an optional addition to an AEF host, prefix, or default entry. Enter a protocol id as a string of consecutive digits.
The MAC address to which the call will be routed if the link is a LAN link.
Enter a six-byte (twelve-digit) hexadecimal value, such as an Ethernet or FDDI address. You can enter the address as consecutive digits or with colons separating bytes. For example, both 080020110233 and 08:0:20:11:2:33 are valid entries. When you save a routing entry with a colon-delimited MAC address, x25tool removes and subsequently displays the address without colons and with leading zeroes within bytes.
Used for dial-up configurations, this is the telephone number of the point of attachment to the PSDN. In most cases, this is a modem.
You can add an optional comment.
In x25tool, the parameters for Call Filtering can be accessed through the Services menu.
The parameter values are stored in the configuration files: /etc/opt/SUNWconn/x25/x25secuconf and /etc/opt/SUNWconn/x25/x25secupid.
Use X.25 Call Filtering to define which incoming calls will be authorized.
Select PAD, TCP-IP, CLNP, OSI, Other, or None to indicate from which service you want to accept incoming calls.
Select Matches, Starts with, or Don't Care to indicate which callers to accept calls from. If you select Matches, or Starts with, you will also need to type in the data.
Specify a time period when calls will be accepted. You can set this up so it is repeated Weekly, Daily, or One Time only.
You can restrict which networks you will accept calls from by specifying the Link Number you will accept calls from. If the link number is set to 255, then X.25 will accept calls over any link.
This is the address of the machine that initiated the call. Set this to Starts with, Matches, Ends with, or Don't Care.