Configuration Error Messages

The following configuration error messages are displayed if errors are encountered when the PPP path configuration file ppp.conf is parsed. In all cases, you should modify the file to correct the error and restart Solstice PPP to correct the problem.

expect_chap_name "name" ends in CR/LF

Indicates that the specified CHAP name is terminated with a carriage return (CR) or line-feed (LF) escape sequence.

expect_chap_name "name" ends in NUL

Indicates that the specified CHAP name is terminated with a NULL character.

default_route: no path defined

Indicates that the specified default_route keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

host IP address not found: hostname

Indicates that the parser was unable to resolve specified hostname to find the IP address. For a synchronous path, the hostname must be associated with an IP address in the file /etc/hosts on the local machine. For an asynchronous path, the hostname may appear in the file /etc/hosts, or be specified by some other naming system.

inactivity_timeout string not recognized

Indicates that the specifies string is not a valid value for the inactivity_timeout parameter. You must enter an integer.

inactivity_timeout: no path defined

Indicates that the specified inactivity_timeout keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

interface number n not recognized

Indicates that the specified number does not correspond to any of the IP interfaces defined in the configuration file.

invalid ip_interface: string

Indicates that the specified string does not correspond to a valid point-to-point (ipdptpn) or point-to-multipoint (ipdn) IP interface.

ip_interface: no path defined

Indicates that the specified ip_interface keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

ipcp_compression value string not recognized

Indicates that the specifies string is not a valid value for the ipcp_compression parameter. Valid values are vj (enabled) and off (disabled).

ipcp_compression: no path defined

Indicates that the specified inactivity_timeout keyword appears in the configuration file, but is not associated with any dialup path definition.

ipd or ipdptp keyword expected

Indicates that the ip_interface keyword appears without specifying a valid point-to-point (ipdptpn) or point-to-multipoint (ipdn) IP interface.

lcp_async_map value string not recognized

Indicates that the specifies string is not a valid value for the lcp_async_map parameter. You must enter a hexadecimal value between 0x0 and 0xffffffff.

lcp_async_map: no path defined

Indicates that the specified lcp_async_map keyword appears in the configuration file, but is not associated with any dialup path definition.

lcp_compression value string not recognized

Indicates that the specifies string is not a valid value for the lcp_compression parameter. Valid values are on (enabled) and off (disabled).

lcp_compression: no path defined

Indicates that the specified lcp_compression keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

lcp_max_restart value string not recognized

Indicates that the specifies string is not a valid value for the lcp_max_restart parameter. You must enter an integer between 1 and 255.

lcp_max_restart: no path defined

Indicates that the specified lcp_max_restart keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

lcp_mru value string not recognized

Indicates that the specifies string is not a valid value for the lcp_mru parameter. You must enter an integer between 1 and 255.

lcp_mru: no path defined

Indicates that the specified lcp_mru keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

lcp_restart_timer value string not recognized

Indicates that the specifies string is not a valid value for the lcp_restart_timer parameter. You must enter an integer.

lcp_restart_timer: no path defined

Indicates that the specified lcp_restart_timer keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

link_monitor value string not recognized

Indicates that the specifies string is not a valid value for the link_monitor parameter. Valid values are on (enabled) and off (disabled).

link_monitor: no path defined

Indicates that the specified link_monitor keyword appears in the configuration file, but is not associated with any synchronous path definition.

link_monitor_retries value string not recognized

Indicates that the specified string is not a valid value for the link_monitor_retries parameter. You must enter an integer.

link_monitor_retries: no path defined

Indicates that the specified link_monitor_retries keyword appears in the configuration file, but is not associated with any synchronous path definition.

link_monitor_timer value string not recognized

Indicates that the specified string is not a valid value for the link_monitor_timer parameter. You must enter an integer.

link_monitor_timer: no path defined

Indicates that the specified link_monitor_timer keyword appears in the configuration file, but is not associated with any synchronous path definition.

malformed ip address: string

Indicates that the specified string is not a valid IP address, entered in Internet dot notation. IP addresses should have the form: xxx.xxx.xxx.xxx

must specify chap_own_secret

Indicates that the send_authentication keyword has been used to enable CHAP authentication when requested by a remote host, but that the mandatory CHAP parameter chap_own_secret has not been set.

must specify chap_peer_secret

Indicates that the send_authentication keyword has been used to enable CHAP authentication when requested by a remote host, but that the mandatory CHAP parameter chap_peer_secret has not been set.

must specify expect_chap_name

Indicates that the expect_authentication keyword has been used to request CHAP authentication from a remote host, but that the mandatory CHAP parameter expect_chap_name has not been set.

must specify send_chap_name

Indicates that the send_authentication keyword has been used to request CHAP authentication from a remote host, but that the mandatory CHAP parameter send_chap_name has not been set.

no paths defined in filename

The PPP path configuration file ppp.conf must contain at least one synchronous or asynchronous path definition. See "Editing the PPP Path Configuration File (ppp.conf)" for detailed instructions.

off, pap, or chap required: string

Indicates that the specified string is not a valid value for the expect_authentication parameter. Valid values are off (no authentication), pap (authentication using PAP), chap (authentication using CHAP), or pap|chap (authentication using both PAP and CHAP).

ppp_link_name: no path defined

Indicates that the specified ppp_link_name keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

remote_host too long: string

Indicates that there was not enough memory available to store the value of the remote_host parameter. This error message may indicate a more serious system error.

remote_host: no path defined

Indicates that the specified remote_host keyword appears in the configuration file, but is not associated with any dialup path definition.

remote_ip_addr: no path defined

Indicates that the specified remote_ip_addr keyword appears in the configuration file, but is not associated with any dialup path definition.

request_ip_addr value string not recognized

Indicates that the specifies string is not a valid value for the request_ip_addr parameter. Valid values are on (enabled) and off (disabled).

unix_device: no path defined

Indicates that the specified unix_device keyword appears in the configuration file, but is not associated with any synchronous or dialup path definition.

wildcards (* | ?) not legal for ipd

You cannot use wildcards to specify point-to-multipoint (ipdn) interfaces. In particular, you cannot use an asterisk (*) to specify a dynamic IP interface.