View Single Post
  #7   (View Single Post)  
Old 16th May 2010
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default

Hi wokko,

I'm guessing the blue light being on only means your modem is connected to the ISP modem, but the modem can't know if a proper PPP connection has been established (unless of course the remote side hangs up).

One place to look is in /var/log/messages for pppd(9)'s blow-by-blow account of things. Here's what mine looks like for a successful connection (I've munged the IP's):

Code:
May 16 11:11:44 throne pppd[289]: pppd 2.4.4 started by root, uid 0
May 16 11:12:13 throne pppd[289]: Serial connection established.
May 16 11:12:13 throne pppd[289]: Using interface ppp0
May 16 11:12:13 throne pppd[289]: Connect: ppp0 <--> /dev/modem
May 16 11:12:15 throne pppd[289]: CHAP authentication succeeded:
May 16 11:12:15 throne pppd[289]: CHAP authentication succeeded
May 16 11:12:15 throne pppd[289]: local  IP address xx.xx.xxx.xx
May 16 11:12:15 throne pppd[289]: remote IP address yyy.yy.yyy.yy
May 16 11:12:15 throne pppd[289]: primary   DNS address nnn.n.n.nnn
May 16 11:12:15 throne pppd[289]: secondary DNS address mmm.m.mmm.mmm
If you don't see something like that, there's a problem with your pppd configuration or chat script. In that case you might want to enable the "debug" parameter for pppd and check whatever debug log file is being used. Note the last 2 lines about DNS won't be there if you didn't use the "usepeerdns" parameter or your ISP doesn't support it. If usepeerdns does work, pppd will write those DNS addresses into /etc/ppp/resolv.conf. Note, this file is not the one in /etc that is used by DNS, you must take steps to use the results if you wish.

Another thing to check is your ppp0 interface when you think you might be up and running; as root, do:

Code:
# ifconfig ppp0
ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1524
        inet xx.xx.xxx.xx -> yyy.yy.yyy.yy netmask 0xff000000
        inet6 fe80::250:baff:fe26:b0a3%ppp0 ->  prefixlen 64 scopeid   0x3
And also check if packets are being routed through the interface:

Code:
# route show  -inet
Routing table

Internet:
Destination        Gateway            Flags
default            yyy.yy.yyy.yy      UG
loopback           127.0.0.1          UGR
localhost          127.0.0.1          UH
my.ip.name         xx.xx.xxx.xx       UH
Maybe you can provide your output to the above commands if it looks suspicious?

As s0xxx said, check your /etc/resolv.conf carefully. Another thing to check, though it's probably OK by default, is your /etc/nsswitch.conf file. There should be a line that looks something like

Code:
hosts:          files dns
in it. It could also say "dns files" on the right, just be sure dns is listed there.
Reply With Quote