Re: PPP scripting on linux PDA - PPP

This is a discussion on Re: PPP scripting on linux PDA - PPP ; On Sat, 05 Jul 2003 17:42:24 +0000, Vicky wrote: Removing the last "" from the chat-uklinux file did the trick. The pda dialled up ok, but when I tried to ping a web site, there was no response. This occurred ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: PPP scripting on linux PDA

  1. Re: PPP scripting on linux PDA

    On Sat, 05 Jul 2003 17:42:24 +0000, Vicky wrote:

    Removing the last "" from the chat-uklinux file did the trick. The pda
    dialled up ok, but when I tried to ping a web site, there was no
    response. This occurred whether I used the URL or the IP address. From
    the browser (Konqueror), I got 'host unkown'.

    The information in /var/log/messages was:
    Jul 9 16:49:35 openzaurus daemon.notice pppd[1142]: pppd 2.4.1 started by root, uid 0
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: abort on (NO CARRIER)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: abort on (ERROR)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: abort on (NO DIALTONE)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: abort on (BUSY)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: abort on (NO ANSWER)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: send (ATZ^M)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: expect (OK)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: ATZ^M^M
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: OK
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: -- got it
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: send (ATDT08456042086^M)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: expect (CONNECT)
    Jul 9 16:49:36 openzaurus local2.info chat[1144]: ^M
    Jul 9 16:50:00 openzaurus local2.info chat[1144]: ATDT08456042086^M^M
    Jul 9 16:50:00 openzaurus local2.info chat[1144]: CONNECT
    Jul 9 16:50:00 openzaurus local2.info chat[1144]: -- got it
    Jul 9 16:50:00 openzaurus daemon.info pppd[1142]: Serial connection established.
    Jul 9 16:50:00 openzaurus daemon.debug pppd[1142]: using channel 4
    Jul 9 16:50:00 openzaurus daemon.info pppd[1142]: Using interface ppp0
    Jul 9 16:50:00 openzaurus daemon.info pppd[1142]: Connect: ppp0 -> /dev/modem
    Jul 9 15:50:00 openzaurus user.notice /etc/hotplug/net.agent: assuming ppp0 is already up
    Jul 9 16:50:01 openzaurus user.notice pppd[1142]: sent [LCP ConfReq id=0x1 ru 576> syncmap 0x0> agic 0x8e4bd1d7>
    omp> ccomp>]
    Jul 9 16:50:03 openzaurus user.notice pppd[1142]: rcvd [LCP ConfReq id=0x30 syncmap 0xa0000> uth chap MD5> agic 0
    a54ed56f> comp> ccomp> rru 1524> ndpoint 13 09 01 42 54 4d 44 49 50>]
    Jul 9 16:50:03 openzaurus user.notice pppd[1142]: sent [LCP ConfRej id=0x30 rru 1524>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: rcvd [LCP ConfReq id=0x31 syncmap 0xa0000> uth chap MD5> agic 0
    a54ed56f> comp> ccomp> ndpoint 13 09 01 42 54 4d 44 49 50>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: sent [LCP ConfAck id=0x31 syncmap 0xa0000> uth chap MD5> agic 0
    a54ed56f> comp> ccomp> ndpoint 13 09 01 42 54 4d 44 49 50>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: sent [LCP ConfReq id=0x1 ru 576> syncmap 0x0> agic 0x8e4bd1d7>
    omp> ccomp>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: rcvd [LCP ConfNak id=0x1 ru 1500>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: sent [LCP ConfReq id=0x2 syncmap 0x0> agic 0x8e4bd1d7> comp> cc
    mp>]
    Jul 9 16:50:04 openzaurus user.notice pppd[1142]: rcvd [LCP ConfAck id=0x2 syncmap 0x0> agic 0x8e4bd1d7> comp> cc
    mp>]
    Jul 9 16:50:04 openzaurus kern.notice pppd[1142]: rcvd [CHAP Challenge id=0x82 68aba6382e5a3ee0c032b2e4c3807c>, n
    me = "BTMDIP"]
    Jul 9 16:50:04 openzaurus daemon.warn pppd[1142]: Warning - secret file /etc/ppp/chap-secrets has world and/or gr
    up access
    Jul 9 16:50:04 openzaurus daemon.warn pppd[1142]: sent [CHAP Response id=0x82 c69611e7e71cb76b5d0d0e7db3b97ef>, n
    me = "vbyford"]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [CHAP Success id=0x82 ""]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: sent [IPCP ConfReq id=0x1 ddr 0.0.0.0> ompress VJ 0f 01> s-dns
    0.0.0.0> s-dns3 0.0.0.0>]
    Jul 9 15:50:05 openzaurus daemon.err modprobe: modprobe: Can't locate module ppp-compress-26
    Jul 9 15:50:05 openzaurus daemon.err modprobe: modprobe: Can't locate module ppp-compress-24
    Jul 9 15:50:05 openzaurus daemon.err modprobe: modprobe: Can't locate module ppp-compress-26
    Jul 9 15:50:05 openzaurus daemon.err modprobe: modprobe: Can't locate module ppp-compress-24
    Jul 9 16:50:05 openzaurus daemon.err pppd[1142]: sent [CCP ConfReq id=0x1 sd v1 15>]
    Jul 9 16:50:05 openzaurus daemon.err pppd[1142]: rcvd [IPCP ConfReq id=0x1a ddr 213.121.147.12>]
    Jul 9 16:50:05 openzaurus daemon.err pppd[1142]: sent [IPCP ConfAck id=0x1a ddr 213.121.147.12>]
    Jul 9 16:50:05 openzaurus daemon.err pppd[1142]: rcvd [IPCP ConfRej id=0x1 ompress VJ 0f 01>]
    Jul 9 16:50:05 openzaurus daemon.err pppd[1142]: sent [IPCP ConfReq id=0x2 ddr 0.0.0.0> s-dns1 0.0.0.0> s-dns3 0.
    ..0.0>]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [LCP ProtRej id=0x32 80 fd 01 01 00 07 15 03 2f]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [IPCP ConfNak id=0x2 ddr 194.247.48.174> s-dns1 194.247.4
    ..47> s-dns3 194.247.40.126>]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: sent [IPCP ConfReq id=0x3 ddr 194.247.48.174> s-dns1 194.247.4
    ..47> s-dns3 194.247.40.126>]
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [IPCP ConfAck id=0x3 ddr 194.247.48.174> s-dns1 194.247.4
    ..47> s-dns3 194.247.40.126>]
    Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: local IP address 194.247.48.174
    Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: remote IP address 213.121.147.12
    Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: primary DNS address 194.247.47.47
    Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: secondary DNS address 194.247.40.126
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: Script /etc/ppp/ip-up started (pid 1175)
    Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: Script /etc/ppp/ip-up finished (pid 1175), status =
    0x1

    Any thoughts as to why I cannot ping the outside world?

    Regards,

    Vicky

    (I tried 'touch'ing the logs for chat and pppd and rerunning syslogd, but
    it still puts everything into 'messages')


    --
    Anti-spam: Remove xxx from email address before replying

  2. Re: PPP scripting on linux PDA

    Vicky writes:
    > Removing the last "" from the chat-uklinux file did the trick. The pda
    > dialled up ok, but when I tried to ping a web site, there was no
    > response. This occurred whether I used the URL or the IP address.


    What kind of "no response?" No response as in "no output from the
    command at all" (probable name server trouble) or as in "ping reported
    that the peer isn't responding" (probable routing trouble)?

    > From
    > the browser (Konqueror), I got 'host unkown'.


    One thing to add to your configuration is "asyncmap 0xa0000". Your
    peer requests this particular ACCM, and you don't. This is legal, but
    many peers that request this particular ACCM are horribly bug-ridden
    and will fail miserably if the ACCM isn't symmetric. This would cause
    things like DNS (which normally runs over UDP, which is IP protocol
    17, which happens to be ^Q [XON]) to fail.

    You might consider getting rid of the unnecessary (and almost
    certainly harmful) usage of 'mru' and 'mtu' options in your
    configuration file. (Yes, I know that your ISP suggested this. The
    hilarious bit is that your logs [which are oddly mangled by
    cut-n-paste] show that the peer doesn't want you to limit your MRU
    anyway.)

    > Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [LCP ProtRej id=0x32 80 fd 01 01 00 07 15 03 2f]


    May as well say "noccp" in your configuration -- the peer doesn't
    support CCP. (This won't make a difference, though.)

    > Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: local IP address 194.247.48.174
    > Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: remote IP address 213.121.147.12
    > Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: primary DNS address 194.247.47.47
    > Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: secondary DNS address 194.247.40.126


    At this point, minus the MRU/MTU concerns above, you're done with PPP.
    PPP is up and running. Any other problems you're having are probably
    somewhere else.

    > Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: Script /etc/ppp/ip-up finished (pid 1175), status =
    > 0x1


    That's a little funky. It's saying that your /etc/ppp/ip-up script
    returned failure (status != 0 on UNIX is traditionally a failure
    indication). What does that script do? And what in it (if anything)
    is falling apart? This is probably not the problem, but it's hard to
    tell.

    > Any thoughts as to why I cannot ping the outside world?


    What's in your routing table once PPP is up?

    What does /etc/resolv.conf point to? Since you're using your ISP's
    name servers, have you done this?

    # rm -f /etc/resolv.conf
    # ln -s /etc/ppp/resolv.conf /etc/resolv.conf

    --
    James Carlson, Solaris Networking
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  3. Re: PPP scripting on linux PDA

    On Wed, 09 Jul 2003 16:34:56 +0000, James Carlson wrote:

    Thanks for your help. I followed your last suggestions and I have now
    been able to view the web and send and receive emails. It would appear
    that the final culprit was the resolv.conf.

    Regards,

    Vicky


    > Vicky writes:
    >> Removing the last "" from the chat-uklinux file did the trick. The pda
    >> dialled up ok, but when I tried to ping a web site, there was no
    >> response. This occurred whether I used the URL or the IP address.

    >
    > What kind of "no response?" No response as in "no output from the
    > command at all" (probable name server trouble) or as in "ping reported
    > that the peer isn't responding" (probable routing trouble)?
    >
    >> From
    >> the browser (Konqueror), I got 'host unkown'.

    >
    > One thing to add to your configuration is "asyncmap 0xa0000". Your peer
    > requests this particular ACCM, and you don't. This is legal, but many
    > peers that request this particular ACCM are horribly bug-ridden and will
    > fail miserably if the ACCM isn't symmetric. This would cause things
    > like DNS (which normally runs over UDP, which is IP protocol 17, which
    > happens to be ^Q [XON]) to fail.
    >
    > You might consider getting rid of the unnecessary (and almost certainly
    > harmful) usage of 'mru' and 'mtu' options in your configuration file.
    > (Yes, I know that your ISP suggested this. The hilarious bit is that
    > your logs [which are oddly mangled by cut-n-paste] show that the peer
    > doesn't want you to limit your MRU anyway.)
    >
    >> Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: rcvd [LCP ProtRej
    >> id=0x32 80 fd 01 01 00 07 15 03 2f]

    >
    > May as well say "noccp" in your configuration -- the peer doesn't
    > support CCP. (This won't make a difference, though.)


    >
    >> Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]: local IP address
    >> 194.247.48.174 Jul 9 16:50:05 openzaurus daemon.notice pppd[1142]:
    >> remote IP address 213.121.147.12 Jul 9 16:50:05 openzaurus
    >> daemon.notice pppd[1142]: primary DNS address 194.247.47.47 Jul 9
    >> 16:50:05 openzaurus daemon.notice pppd[1142]: secondary DNS address
    >> 194.247.40.126

    >
    > At this point, minus the MRU/MTU concerns above, you're done with PPP.
    > PPP is up and running. Any other problems you're having are probably
    > somewhere else.
    >
    >> Jul 9 16:50:05 openzaurus daemon.debug pppd[1142]: Script
    >> /etc/ppp/ip-up finished (pid 1175), status = 0x1

    >
    > That's a little funky. It's saying that your /etc/ppp/ip-up script
    > returned failure (status != 0 on UNIX is traditionally a failure
    > indication). What does that script do? And what in it (if anything) is
    > falling apart? This is probably not the problem, but it's hard to tell.
    >
    >> Any thoughts as to why I cannot ping the outside world?

    >
    > What's in your routing table once PPP is up?
    >
    > What does /etc/resolv.conf point to? Since you're using your ISP's name
    > servers, have you done this?
    >
    > # rm -f /etc/resolv.conf
    > # ln -s /etc/ppp/resolv.conf /etc/resolv.conf
    >


    --
    Anti-spam: Remove xxx from email address before replying

+ Reply to Thread