Re: PPP Configuration: Getting Hooked Up to my ISP
It does seems as a domain name related problem. A possible solution would be to install the BIND package. > 5. I cannot ping anything that is not localhost or the gateway (see below) > Ex. 'ping sunsite.unc.edu' > > 6. DNS configuration does not seem configured properly. I am inferring this > by comparing my output of ifconfig() and route () with the output example > in the PPP-HOWTO document. > # ping 209.142.30.4 <-- ISP Gateway machine works fine > PING 209.142.30.4 (209.142.30.4): 56 data bytes > 64 bytes from 209.142.30.4: icmp_seq=0 ttl=255 time=404.9 ms > 64 bytes from 209.142.30.4: icmp_seq=1 ttl=255 time=370.0 ms > 64 bytes from 209.142.30.4: icmp_seq=2 ttl=255 time=350.2 ms > 64 bytes from 209.142.30.4: icmp_seq=3 ttl=255 time=380.0 ms > > # ping sunsite.unc.edu<-- Without DNS lookup, this puppy is lost > -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
Re: PPP Configuration: Getting Hooked Up to my ISP
With a private net IP number (192.168.x.y) you cannot access anyone other than your ISP unless he is masquerading you. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia voice +61 8 9316 248632.0125S 115.8445Evk6lj Debian Unix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Fri, 13 Mar 1998, M. Fong wrote: > Status: Stage 2: Further along, running into DNS issues > > Thanks for the suggestions thus far: > I had a shell script which didn't have the correct 'executable' > permissions. Something like rw-rw-rw instead of chmod 777 > /etc/ppp/. > > Here is how far I have progressed: > 1. Executing pppd now dials out (I never got this far in Stage 1 becaues a > script file did not have execute > permissions hence it was unable to call chat()) > 2. Logging into the ISP successfully > 3. PAP authentication works fine > 4. I can ping the ISP's gateway machine. > > << BRICK WALL>> > 5. I cannot ping anything that is not localhost or the gateway (see below) > Ex. 'ping sunsite.unc.edu' > > 6. DNS configuration does not seem configured properly. I am inferring this > by > comparing my output of ifconfig() and route () with the output example > in the > PPP-HOWTO document. > > > - > # pppd& <--- Logs in fine and the connection is up. > > # ifconfig > loLink encap:Local Loopback > inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 > UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 > RX packets:387 errors:0 dropped:0 overruns:0 > TX packets:387 errors:0 dropped:0 overruns:0 > ppp0 Link encap:Point-Point Protocol > inet addr:192.168.1.1 P-t-P:209.142.30.4 Mask:255.255.255.0 > UP POINTOPOINT RUNNING MTU:1524 Metric:1 > RX packets:16 errors:0 dropped:0 overruns:0 > TX packets:37 errors:0 dropped:0 overruns:0 > > # ping 209.142.30.4 <-- ISP Gateway machine works fine > PING 209.142.30.4 (209.142.30.4): 56 data bytes > 64 bytes from 209.142.30.4: icmp_seq=0 ttl=255 time=404.9 ms > 64 bytes from 209.142.30.4: icmp_seq=1 ttl=255 time=370.0 ms > 64 bytes from 209.142.30.4: icmp_seq=2 ttl=255 time=350.2 ms > 64 bytes from 209.142.30.4: icmp_seq=3 ttl=255 time=380.0 ms > > # ping sunsite.unc.edu<-- Without DNS lookup, this puppy is lost > > # > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 209.142.30.40.0.0.0 255.255.255.255 UH0 01 ppp0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 07 lo > 0.0.0.0 209.142.30.40.0.0.0 UG0 0 15 ppp0 > > > > > > > > > > > > -- > E-mail the word "unsubscribe" to [EMAIL PROTECTED] > TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] > > -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
Re: PPP Configuration: Getting Hooked Up to my ISP
"M. Fong" <[EMAIL PROTECTED]> writes: > Status: Stage 2: Further along, running into DNS issues > > Thanks for the suggestions thus far: > I had a shell script which didn't have the correct 'executable' > permissions. Something like rw-rw-rw instead of chmod 777 > /etc/ppp/. > > Here is how far I have progressed: > 1. Executing pppd now dials out (I never got this far in Stage 1 becaues a > script file did not have execute > permissions hence it was unable to call chat()) > 2. Logging into the ISP successfully > 3. PAP authentication works fine > 4. I can ping the ISP's gateway machine. > > << BRICK WALL>> > 5. I cannot ping anything that is not localhost or the gateway (see below) > Ex. 'ping sunsite.unc.edu' > > 6. DNS configuration does not seem configured properly. I am inferring this > by > comparing my output of ifconfig() and route () with the output example > in the > PPP-HOWTO document. Well, from the transcript you included, I can't tell if problem 6 is causing problem 5, or vice versa. Since 'route -n' actually seems to give reasonable values, could you try 'ping 206.170.168.35'? (That address was one of the DNS servers listed in your original post). Also, try removing the "domain" statement from /etc/resolv.conf. "domain" and "search" keywords are mutually exclusive. -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
Re: PPP Configuration: Getting Hooked Up to my ISP
Status: Stage 2: Further along, running into DNS issues Thanks for the suggestions thus far: I had a shell script which didn't have the correct 'executable' permissions. Something like rw-rw-rw instead of chmod 777 /etc/ppp/. Here is how far I have progressed: 1. Executing pppd now dials out (I never got this far in Stage 1 becaues a script file did not have execute permissions hence it was unable to call chat()) 2. Logging into the ISP successfully 3. PAP authentication works fine 4. I can ping the ISP's gateway machine. << BRICK WALL>> 5. I cannot ping anything that is not localhost or the gateway (see below) Ex. 'ping sunsite.unc.edu' 6. DNS configuration does not seem configured properly. I am inferring this by comparing my output of ifconfig() and route () with the output example in the PPP-HOWTO document. - # pppd& <--- Logs in fine and the connection is up. # ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:387 errors:0 dropped:0 overruns:0 TX packets:387 errors:0 dropped:0 overruns:0 ppp0 Link encap:Point-Point Protocol inet addr:192.168.1.1 P-t-P:209.142.30.4 Mask:255.255.255.0 UP POINTOPOINT RUNNING MTU:1524 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 TX packets:37 errors:0 dropped:0 overruns:0 # ping 209.142.30.4 <-- ISP Gateway machine works fine PING 209.142.30.4 (209.142.30.4): 56 data bytes 64 bytes from 209.142.30.4: icmp_seq=0 ttl=255 time=404.9 ms 64 bytes from 209.142.30.4: icmp_seq=1 ttl=255 time=370.0 ms 64 bytes from 209.142.30.4: icmp_seq=2 ttl=255 time=350.2 ms 64 bytes from 209.142.30.4: icmp_seq=3 ttl=255 time=380.0 ms # ping sunsite.unc.edu<-- Without DNS lookup, this puppy is lost # # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 209.142.30.40.0.0.0 255.255.255.255 UH0 01 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 07 lo 0.0.0.0 209.142.30.40.0.0.0 UG0 0 15 ppp0 -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
Re: PPP Configuration: Getting Hooked Up to my ISP
Ian Perry writes: > If your ISP requires pap authentication, you need to uncomment the +pap > line in your options file. Don't do this. '+pap' tells pppd to require that your isp authenticate himself to you. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
Re: PPP Configuration: Getting Hooked Up to my ISP
If your ISP requires pap authentication, you need to uncomment the +pap line in your options file. Also he may not require you to run a script.. You might try taking out the login and password references in your script, as ppp authentication should take care of it. My ISP does it this way. Try adding "debug" to your options file as well, to get some more meaningful error messages in your syslog, and have a look at your ppp.log file as well. 56800 will not work in your options file as the next setting above 38400 is 57600. Hope this helps... Ian -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]
PPP Configuration: Getting Hooked Up to my ISP
HELP: Configuring PPP on a Basic Debian Linux 1.3.1 System - ABSTRACT: The simplest of cnfigurations, a standalone Linux system with an external modem going across a regular phone line to a well-behaved ISP cannot get dial-up capability. Hdw: Pentium 133MHz system (w/ Cyrix 686-type CPU) Logicode External 56K modem on /dev/cua1 (COM2) (mouse on 1st serial port /dev/ttyS0 (COM1), no other serial devices on (COM3 or COM4)) Normal config: Adaptec SCSI adapter, SCSI drives, SOHO Ethernet card, S3/Verge generic graphics card, ... Sw: OS: Debian 1.3.1 (secondary os, Windows 95 for connectivity) Services: JPS Net (dial-in Internet Service Provider) attributes: 56K modem support with X2 or 56flex enforces PAP (Password Authentication Protocol) well documented technical settings on their webpage such as DNS numbers, dial-in numbers, etc Problem: Cannot get pppd(8) configured correctly. The physical connection works fine. Steps: 1. Verified kernel support for ppp 2. Matched device /etc/cua1 with the correct serial port. 3. Verified physical connection between modem and serial port. 4. Used Kermit to manually test the connection (The document PPP-HOWTO is very good about successfully passing through each step successfully. Unfortunately, it is heavily biased towards BSD style Linuxes; Debian happens to be ATT Sys5 style.) Here is where I start to break down. I experimented with ezPPP, the PPP-HOWTO and help from archived individuals. I'm may be in a tangle with unnecessary config files or misconfigured files. CONFIGURATION FILES: -- /etc/ppp/options # /etc/ppp/options # # Prevent pppd from forking into the background #-detach debug /dev/ttyS1 # If you are using a STATIC IP number, edit the 0.0.0.0 part of the # following line to your static IP number. # 0.0.0.0: # # use the modem control lines 38400 <-- I tried using 56800 but pppd didn't like that modem # use uucp style locks to ensure exclusive access to the serial device lock # use hardware flow control crtscts connect /etc/ppp/ppp-connect # create a default route for this connection in the routing table defaultroute # do NOT set up any "escaped" control sequences asyncmap 0 # use a maximum transmission packet size of 552 bytes # mtu 552 # use a maximum receive packet size of 552 bytes # mru 552 # # force pppd to use your ISP username as your 'host name' during the # authentication process # technically 'user' is bettern than 'name' but ppp understands both # and 'name' works for CHAP as well. # name fred <-- my ISP username here # # If you need to force PAP or CHAP authentication on the server, # uncomment the appropriate one of the following lines. #+chap #+pap # # If you are using ENCRYPTED secrets in the /etc/ppp/pap-secrets # file, then uncomment the following line. #+papcrypt -- /etc/resolv.conf domain jps.net search jps.net nameserver 206.170.168.35 nameserver 208.25.63.252 -- /etc/ppp/pp-connect #!/bin/sh /usr/sbin/chat -v -t 60 -f /etc/ppp/ppp-chat -- /etc/ppp/ppp-chat ABORT "BUSY" ABORT "NO CARRIER" "" AT&F\r OK AT&D2&C1\r OK ATD423-0023\r ogin: fred\r sword: mywilma\r -- /etc/ppp/pap-secrets # This is a pap-secrets file to be used with the AUTO_PPP function of mgetty # mgetty-0.99 is preconfigured to startup pppd with the login option which # will cause pppd to consult /etc/passwd after a user has passed this file # Dont be disturbed therfore by the fact that this file defines logins with # any password for users. /etc/passwd will catch passwd mismatches. # # This file should block ALL users that should not be able to do AUTO_PPP! # AUTO_PPP bypasses the usual login program so its necessary to list all # system userids with regular passwords here! # # ATTENTION: The definitions here can allow users to login without a # password if you dont use the login option of pppd! # The /etc/ppp/options file installed has the login option enabled # INBOUND connections # Every regular user can use PPP and has to use passwords from /etc/passwd * os "" # UserIDs that cannot use PPP at all. Check your /etc/passwd and add any # other accounts that should not be able to use pppd! #guest os "*" - master os "*" - #root os "*" - support os "*" - stats os "*" - # OUTBOUND connections # Here you should add your userid password to connect to your providers via # pap. The * means that the password is to be used for ANY host you connect # to. Thus you do not have to worry about the foreign machine name. Just # replace password with your password. # If you have different providers with different passwords then you better # remove the following line. os * password fred* mywilma
