Anonymous web server - This shows that the gateway was set to
Tuesday, July 31st, 2007This shows that the gateway was set to the remote PPP server (198.62.1.1), as well as showing the other interfaces running on my computer. There are two ppp0 entries. The first shows the destination as a host (UH). The second shows the destination as a gateway (UG). All addresses that can t be resolved on the local LAN are directed to the gateway address. Check that the name servers are set If you are able to ping a remote computer by IP address, but are not able to resolve any addresses, your DNS servers may not be set correctly. As root user from a Terminal window, open the /etc/resolv.conf file and check that there are lines identifying one or more DNS servers in this file. These should be supplied to you by your ISP. Here are some examples (the numbers are fictitious): nameserver 111.11.11.111 nameserver 222.22.22.222 Check the chap-secrets or pap-secrets files PPP supports two authentication protocols in Red Hat Linux: Challenge Handshake Authentication Protocol (CHAP) and Password Authentication Protocol (PAP). Here is what each protocol does to authenticate: CHAP The server sends the client a challenge packet (which includes the server name). The client sends back a response that includes its name and a value that combines the secret and the challenge. The client name and secret are stored in your /etc/ppp/chap-secrets file. PAP The client sends its name and a password (clear text) for authentication. The client name and secret are stored in your /etc/ppp/pap-secrets file. By default, PPP in Red Hat Linux will authenticate if the server requests it, unless it has no secrets to share. If it has no secrets, PPP (or, more specifically, the PPP daemon pppd) will refuse authentication. It is likely that if you look in these files you will find the user names and passwords you provided when you set up your PPP connection (Red Hat assumes that you may be using CHAP or PAP authentication). The chap-secrets and pap-secrets file formats are the same. Each authentication line can contain the client name, the server name, and the secret. The server name can be represented by an * (to allow this secret to be used to authenticate any server). This is useful if you don t know what the server name will be. Also, remember that case is significant (that is, Myserver is not the same as myserver). Tip For more details about PAP and CHAP in PPP for Linux, see the pppd man page (type man pppd). In any case, here s an example of what a chap-secrets file may look like: # Secrets for authentication using CHAP # client server secret IP addresses 0300584919390921 * JckMLt4CwZiYo03/bkNTpLmU * Caution The pap-secrets and chap-secrets files should not be accessible by anyone but the root user. Anyone gaining this information could use it to access your Internet account. (To close permission, type chmod 600 /etc/ppp/*-secrets.) You need to obtain your own client name and secret from your ISP. The ones shown here are just examples. Look at the ifcfg-ppp0 file The ifcg-ppp0 file (/etc/sysconfig/network-scripts/ifcfg-ppp0) contains options that are passed to the pppd daemon for features that are negotiated with the remote PPP server. Most of the problems that can occur with
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.