RH9: ADSL connection drops every ~50 secs if inactive.

Discussion in 'Linux Networking' started by Gabolander, Aug 9, 2003.

  1. Gabolander

    Gabolander Guest

    Hi all,
    I've the following problem:
    I've an ADSL ethernet Modem connected in my linux box rh 9.
    After configuring ADSL connection with /sbin/adsl-setup, I can perfectly
    connect with /sbin/adsl-start, but every 30~50 secs, if the connection
    (ppp0) stays inactive, the connection drops, and reactivate itself some
    seconds later.

    While configuring adsl via /sbin/adsl-setup, at the question "Do you want
    the link to come up on demand, or stay up continuously?", I answered 'no',
    but the problem is there as well.
    Under winz-xp I don't have such problem.
    I preface I have a strange network configuration:
    the eth1 interface is the NIC connected to eth-modem.
    when I'm not connected I have the following configuration:
    (Ifconfig output)
    eth0 Link encap:Ethernet HWaddr 00:05:1C:0B:62:DE
    inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:0 (0.0 b) TX bytes:11337 (11.0 Kb)

    eth1 Link encap:Ethernet HWaddr 00:D0:70:00:BF:86
    inet addr:192.168.1.0 Bcast:192.168.1.1 Mask:255.255.255.255
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:48329 errors:0 dropped:0 overruns:0 frame:0
    TX packets:47629 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:35146498 (33.5 Mb) TX bytes:5036490 (4.8 Mb)

    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:121 errors:0 dropped:0 overruns:0 frame:0
    TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:38886 (37.9 Kb) TX bytes:38886 (37.9 Kb)

    (route output)
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
    169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
    127.0.0.0 * 255.0.0.0 U 0 0 0 lo


    .... while, when I'm connected I have :
    (Ifconfig output)
    eth0 Link encap:Ethernet HWaddr 00:05:1C:0B:62:DE
    inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:0 (0.0 b) TX bytes:11337 (11.0 Kb)

    eth1 Link encap:Ethernet HWaddr 00:D0:70:00:BF:86
    inet addr:192.168.1.0 Bcast:192.168.1.1 Mask:255.255.255.255
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:48343 errors:0 dropped:0 overruns:0 frame:0
    TX packets:47639 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:35147383 (33.5 Mb) TX bytes:5037090 (4.8 Mb)

    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:121 errors:0 dropped:0 overruns:0 frame:0
    TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:38886 (37.9 Kb) TX bytes:38886 (37.9 Kb)

    ppp0 Link encap:point-to-Point Protocol
    inet addr:80.182.123.105 P-t-P:192.168.100.1
    Mask:255.255.255.255
    UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
    RX packets:7 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0
    RX bytes:246 (246.0 b) TX bytes:54 (54.0 b)


    (route output)
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0
    192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
    169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
    127.0.0.0 * 255.0.0.0 U 0 0 0 lo
    default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0


    I feel 169.254.0.0 address is strange (should be ZEROCONF, but I don't know
    how it works).

    Thnx in advance to anyone will help me.

    --
    === NO SPAM ALERT ===
    If you desire to answer directly to me please post mail
    to "GgNOzappiSPAM(at)inwind(dot)it" (removing all the
    uppercase letters, including leading 'G'). Spam mail will
    be bombed !!
     
    Gabolander, Aug 9, 2003
    #1
    1. Advertisements

  2. In /etc/ppp/pppoe.conf comment out the line that says PPPOE_TIMEOUT=80

    The purpose of PPPOE_TIMEOUT is to time out the client if LCP (layer 2)
    echo requests aren't answered for 80 seconds. Unfortunately in some
    cases RP seems to timeout if IP (layer 3) is inactive for that long,.
    even when layer 2 is chatting along with echo-request/echo-reply just fine.

    I had to do this with RH 7.3. FWIW I haven't had to do this with RH9.
    I use the genuine RP software from the RP site, not the RH hack of the
    RP software.

    HTH
     
    Allen Kistler, Aug 9, 2003
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.