Problems With A PPP Dial-Up Connection

From: Byron Hillis (b_hillis_at_optusnet.com.au)
Date: 03/17/05

  • Next message: Ron Johnson: "Re: [ANN] PicoDebian: a thinned down version of Debian Sarge"
    To: <debian-user@lists.debian.org>
    Date: Thu, 17 Mar 2005 23:45:10 +1100
    
    

    Hi everybody,

    Okay, so I want to set up a normal dial-up connection to my ISP (no
    broadband yet unfortunately). I found this HOWTO
    http://www.aboutdebian.com/modems.htm and followed all the steps. But as you
    might have guessed, it doesn't work.

    Specs:
    Debian Woody 3.0
    2.4.18-bf2.4

    Connected on the LAN via eth0.
    Modem: Netcomm Roadster II 56Ultra connected via ttyS1

    Here's the problem. The modem works fine (or so I think), and dials in and
    connects as per expected. But then no connections seem to work. Pings and
    Lynx don't work to the other end of the ppp connection, or any of my service
    providers DNS servers. Pings work to local public IP. I tried adding the
    default route as suggested in the HOWTO and also added my nameservers. When
    I type _route_ to get the list of route's it takes about 30 secs for
    anything other than the headers to come up. But _dig_ works. I also noticed
    that it seems to disconnect after a while (maybe 10 mins) and then
    automatically reconnects (as it should). Not sure what's going on there.

    Here's some useful info...
    (INFO CHANGED TO PROTECT THE INNOCENT)

    /etc/resolv.conf --------------->

    search optusnet.com.au.
    nameserver 1.2.3.4
    nameserver 1.2.3.5

    <--------------------------

    /etc/chatscripts/provider --------------->

    ABORT BUSY
    ABORT "NO CARRIER"
    ABORT VOICE
    ABORT "NO DIALTONE"
    "" ATZW2
    OK ATDT123456789
    ogin username
    word \qpassword

    <--------------------------

    /etc/ppp/peers/provider --------------->

    # You usually need this if there is no PAP authentication
    noauth

    # The chat script (be sure to edit that file, too!)
    connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"

    # Set up routing to go through this PPP link
    defaultroute

    # Default modem (you better replace this with /dev/ttySx!)
    /dev/ttyS1

    # Speed
    115200

    # Keep modem up even if connection fails
    persist

    <--------------------------

    Output from route BEFORE pon (no delay) ---------------->

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    localnet * 255.255.255.0 U 0 0 0 eth0
    default remnant 0.0.0.0 UG 0 0 0 eth0

    <-------------------------------------

    Output from ifconfig AFTER pon ---------------->

    eth0 Link encap:Ethernet HWaddr 00:20:18:A1:39:08
              inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
              RX packets:579 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1382 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:57285 (55.9 KiB) TX bytes:104983 (102.5 KiB)
              Interrupt:9 Base address:0xaf00

    lo Link encap:Local Loopback
              inet addr:127.0.0.1 Mask:255.0.0.0
              UP LOOPBACK RUNNING MTU:16436 Metric:1
              RX packets:292 errors:0 dropped:0 overruns:0 frame:0
              TX packets:292 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:26389 (25.7 KiB) TX bytes:26389 (25.7 KiB)

    ppp0 Link encap:Point-to-Point Protocol
              inet addr:10.10.10.10 P-t-P:1.1.1.1 Mask:255.255.255.255
              UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
              RX packets:168 errors:0 dropped:0 overruns:0 frame:0
              TX packets:181 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:3
              RX bytes:26736 (26.1 KiB) TX bytes:12613 (12.3 KiB)

    NOTE: Is there something strange about the ppp0 mask? Just guessing?

    <-------------------------------------

    Output from route AFTER pon (30s delay) (No extra routing added)
    ---------------->

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    203.164.5.254 * 255.255.255.255 UH 0 0 0 ppp0
    localnet * 255.255.255.0 U 0 0 0 eth0
    default remnant 0.0.0.0 UG 0 0 0 eth0

    <-------------------------------------

    Output from dig www.debian.org (No extra routing added) ---------------->

    ; <<>> DiG 9.2.1 <<>> www.debian.org
    ;; global options: printcmd
    ;; connection timed out; no servers could be reached

    <-------------------------------------

    Output from route AFTER pon (30s delay) (Extra routing added)
    ---------------->

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    203.164.5.254 * 255.255.255.255 UH 0 0 0 ppp0
    localnet * 255.255.255.0 U 0 0 0 eth0
    default * 0.0.0.0 U 0 0 0 ppp0
    default remnant 0.0.0.0 UG 0 0 0 eth0

    <-------------------------------------

    Output from dig www.debian.org (Extra routing added) ---------------->

    ; <<>> DiG 9.2.1 <<>> www.debian.org
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15798
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;www.debian.org. IN A

    ;; ANSWER SECTION:
    www.debian.org. 1257 IN A 194.109.137.218

    ;; AUTHORITY SECTION:
    debian.org. 1257 IN NS spohr.debian.org.
    debian.org. 1257 IN NS klecker.debian.org.
    debian.org. 1257 IN NS newsamosa.debian.org.
    debian.org. 1257 IN NS saens.debian.org.

    ;; ADDITIONAL SECTION:
    newsamosa.debian.org. 1257 IN A 208.185.25.35

    ;; Query time: 147 msec
    ;; SERVER: 210.49.20.209#53(211.29.132.12)
    ;; WHEN: Thu Mar 17 23:21:12 2005
    ;; MSG SIZE rcvd: 150

    <-------------------------------------

    Output from ping -v 1.2.3.4 (Extra routing added - DNS IP) ---------------->

    PING 1.2.3.4 (1.2.3.4): 56 data bytes
    ping: packet too short (56 bytes) from 1.1.1.1
    ping: packet too short (56 bytes) from 1.1.1.1
    ping: packet too short (56 bytes) from 1.1.1.1
    ping: packet too short (56 bytes) from 1.1.1.1

    --- 1.1.1.1 ping statistics ---
    4 packets transmitted, 0 packets received, 100% packet loss

    NOTE: 1.1.1.1 is the other end of the PPP connection.

    <-------------------------------------

    Thanks for your help. This problem is a real pain to debug, cause I have to
    boot into windows to go on the net to look for information, then jump back,
    try the new info and repeat the process.

    Byron

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Ron Johnson: "Re: [ANN] PicoDebian: a thinned down version of Debian Sarge"

    Relevant Pages

    • Re: NTHell
      ... > packet loss 40% to 50% ... > ping times up to nearly 400mS ... My broadband connection is via the set top box. ... loss rises above 10%, the STB information available on the TV screen ...
      (uk.comp.sys.mac)
    • Re: PPP problem in a usb driver...
      ... Also when i open 4 vc connections and start a ping ... Each connection makes a separte entry in the global task of my ... when a packet comes on reception or when it receives a call ... memory free is failing. ...
      (comp.os.linux.development.system)
    • Re: PPP problem in a usb driver...
      ... Also when i open 4 vc connections and start a ping ... Each connection makes a separte entry in the global task of my ... when a packet comes on reception or when it receives a call ... memory free is failing. ...
      (comp.os.linux.development.system)
    • Re: Config ADSL
      ... >The connection still fails, so I have included my routing table for you to see, if it helps: ... You have 2 default gateways assigned, and both are on the local LAN ... You must remove the default gateways and allow the DSL connection to set ... ping is not the almighty tool much people take ...
      (Fedora)
    • Re: peer to peer messaging
      ... attempts to open a connection to port 80 of the server at that IP address. ... For example a packet from my machine might have source IP ... Packets from the sever to my laptop would have those reversed. ...
      (comp.lang.java.programmer)