Bill-- Bless your heart; you've anticipated my question.  Last night,
using "pon," I was able to run "ftp" (because unlike wvdial, pon gives me
a prompt), and actually reached both debian.org & sunsite.unc.edu, and
successfully transferred a couple of README files.  Oh, joy! Oh, rapture!
I also ran route -n and ifconfig the same way.  The responses I got were
similar to those you posted. (The differences are shown below within []).


     Since receiving your message, I tried "ping debian.org."  It
responded with a chronological output list, like this: 

"64 bytes from 209.81.8.242: icmp_seq=0 ttl=53 time=310.3ms
 64 bytes from 209.81.8.242: icmp_seq=1 ttl=53 time=250.1ms"
 etc,
just like in my Linux Reference guide (Matt Welsh).  Once again, however,
I'm only able to do this from within pon-poff.  I haven't tried adding a
default route as yet, because I'm not sure if I need to, but obviously,
something's missing here.
 
    Even though I've configured exim, it doesn't by itself arouse pppd,
and so it doesn't actually send the messages.  Neither does elm+me.  All
commands run outside of pon-poff (even to my ISP) result in "hostname
unknown," except for wvdial, which connects me with the ISP, but gives me
no prompt.  I've looked at the host.conf file, the hostname file,
chatscripts, chat-secrets, pap-secrets, ppp, and resolv.conf, and they
all apparently match what's recommended.  

    I'm looking to find a site from which I might download *nix Netscape
by ftp, if that's possible.  This is like peeling an onion-- another
problem just underneath the last one.  Many thanks for your help. -- Max 

On Sun, 18 Jul 1999 18:40:18 -0400 Bill Leach <[EMAIL PROTECTED]>
writes:
>Hi Max;
>
>The "route -n" response is OK UNTIL you are "on-line".  Online you 
>should have something like:
>
Kernel IP routing table
Destination     Gateway        Genmask         Flag Met. Ref  UseIface
[207.149.159.3] 0.0.0.0        255.255.255.255 UH   0    0    0 ppp0
[127.0.0.0      0.0.0.0        255.0.0.0       U    0    0    0 lo]
0.0.0.0       [207.149.159.1]  0.0.0.0         UG   0    0    0 ppp0
>
>Where that last entry is the "default route" entry and is necessary so
that your computer will send any packets for which it does not know "how
to handle" to that interface.
>
>First step is to manually confirm what is wrong so...
>After you have gone online issue:  /sbin/ifconfig and you should see
something like:
  lo      Link 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:[0] errors:0 dropped:0 overruns:0 frame:0
>         TX packets:[0] errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 [txqueuelen:0]-(I don't receive this.) 
>
ppp0   Link encap:Point-to-Point Protocol  
       inet addr:[207.149.159.123]P-t-P:[207.149.159.1]
Mask:255.255.255.0
       UP POINTOPOINT RUNNING        MTU:[1524]  Metric:1
       RX packets:[13] errors:0 dropped:0 overruns:0 frame:0
       TX packets:[13] errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 [txqueuelen:10]- (I don't recv this) 
       [Memory: 504038-504c04]

>The important entry for our purposes right now is the "ppp0" entry.
>Notice that the P-t-P entry is the same as the first "Destination 
>entry in my example machine's route -n response and that it is the
"Gateway" entry for the "Default" route (the one with a destination of
0.0.0.0).
>
>Try (as root) doing a:
>route add default gw <P-t-P value from ifconfig> metric 1
>
>Check the route -n response again to ensure that your change is 
>included. Try a ping to something known (the most obvious being the IP
address for the P-t-P):
 ping <ip address>
>if successful shows that your routing is good.
>and then try:
>ping <some system name like ftp.debian.org>
>if successful shows that you name resolution is also OK.
>
>Finally, IF all of this works then we need to find out what happened.
>Assuming that it does work then it is likely that for some reason
>your ppp initiation is not setting a default route.
>
>----------
>You should have a mail system on your machine and it should be 
>running.
>It does sound to me though that you might be better off for now to
>ignore your machine's mail system and use the netscape mail or one of
>the other solutions.
>
>Netscape is the easiest as its' setup is virtually the same as on 
>Windoz
>or as it is on Windoz for other mailers.  You just enter the name or
>ip address for your ISP provided mail server and choose to use the
>POP3 protocol (I believe that you again have to enter the mail server
>because there is no inherent requirement that you receive and post 
>mail
>to the same machine--except under windoz).

___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.

Reply via email to