Re: Minicom and PPP (fmr: Unidentified Subject!)

[Kalum Somaratna aka Grendel <kalum lintux cx>]

On Fri, 9 Jun 2000, Erik Brown wrote:

> 
> following your directions, I logged onto my ISP via minicom, exited (without
> resetting) and then at the prompt typed:
> 
> [root] [indiana]~# /usr/sbin/pppd /dev/ttyS2 crtscts 38400 lock debug
> noipdefault noauth silent nodetach
> Using interface ppp0
> Connect: ppp0 <--> /dev/modem
<snip>

> local  IP address 208.148.193.208
> remote IP address 208.148.192.30

Ok..so it appears that there is no problem with your modem. See PPPD has
succesfully connected and you have got your local IP addressSo this bit
is OK.

I think you maybe having your problem because you haven't specified a
nameserver.

please read on...

> 
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:208.148.193.208  P-t-P:208.148.192.30
> Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10

again it appears to me that you have established a good connection, so
your modem is ok.

> 
> so, I hope that gives you an idea of what's going on with my modem.  In
> terms of doing things with my connection, once I got pppd running, I
> couldn't telnet or use netscape.

Ok..What I think is hapenning is that maybe you haven't specified a
nameserver.

a nameserver is what translates google.com to 312.434.3cxx which the
machine needs to work.

You have to specifiy the nameserver in the /etc/resolv.conf file,


for example hears my /etc/resolv.conf file

nameserver 127.0.0.1

As you can see my nameserver is 127.0.0.1 


So please check your /etc/resolv.conf and see whether there is anysuch
thing in it

so you can try adding a address of your ISP's nameserver or try using your
own nameserver, just add the above line and see whether it works if you
want to try using your own nameserver. you should have the named daemon up
and running for it to work.

BTW Could you please tell me what exactly do you mean when you say "can't
use netscape or telnet", what are the error messages they printout.


> But, I guess that was the purpose of this exercise.

Personally I think that it is a nameserver problem, since from the output
that you posted, if your modem was able to get that far, it is highly
unlikely that it could be a modem problem.


> Anyway, I appreciate any help you can give, and I also appreciate all the
> help I have received to this point,

Don't worry there are quite a lot of great people on this list, your
problem will be sson sorted out Erik, so hangon.

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)