Anyone get adsl-start working in FC3? - Linux

This is a discussion on Anyone get adsl-start working in FC3? - Linux ; I have a redhat 9 system for years and ran my adsl modem in bridged mode and then connected to my provider with adsl-start. This worked very well, always for years. I did this with rp-pppoe-3.5-1, when an upgrade for ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Anyone get adsl-start working in FC3?

  1. Anyone get adsl-start working in FC3?

    I have a redhat 9 system for years and ran my adsl modem in bridged mode
    and then connected to my provider with adsl-start. This worked very well,
    always for years. I did this with rp-pppoe-3.5-1, when an upgrade for rp-
    pppoe-3.5-2 came along and I did it, I could no longer connect, went back
    to rp-pppoe-3.5-1. Life was grand.

    Then the script kiddies came along, broke into the system through apache,
    and wreaked havoc. Now the redhat 9 system is no longer secure. Dumping
    it for fedora core 3. I did adsl-setup as before, and then adsl-start.
    Would not connect. I went back to my old rp-pppoe-3.5-1 package, tried
    again, could not connect. Here is some debug info from the current adsl-
    start:

    ---------------------------------------------
    Sat May 7 16:02:28 EDT 2005
    ---------------------------------------------
    * The following section is a dump of the packets
    * sent and received by rp-pppoe. If you don't see
    * any output, it's an Ethernet driver problem. If you only
    * see three PADI packets and nothing else, check your cables
    * and modem. Make sure the modem lights flash when you try
    * to connect. Check that your Ethernet card is in
    * half-duplex, 10Mb/s mode. If all else fails,
    * try using pppoe-sniff.
    rp-pppoe debugging dump
    rp-pppoe-3.5
    16:01:53.549 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
    SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
    01 01 00 00 01 03 00 04 bd 13 00 00 ............

    16:01:58.548 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
    SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
    01 01 00 00 01 03 00 04 bd 13 00 00 ............

    16:02:08.546 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
    SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
    01 01 00 00 01 03 00 04 bd 13 00 00 ............
    ---------------------------------------------

    This is the very same physical setup as the working redhat 9 distro. I
    can plug in the new fc3 drive and can no longer connect. What is the deal
    with adsl-connect with fc3? Has anyone ever gotten this to work with
    fedora core? What is so difficult about this? Should I try a diffent
    distro? How could something so widely used like fc3 just "not work" with
    adsl-setup?

    --
    ~Ohmster
    ohmster at newsguy dot com

  2. Re: Anyone get adsl-start working in FC3? - Solved!

    Ohmster wrote in
    news:Xns964FD5E494F76MyBigKitty@216.77.188.18:

    > This is the very same physical setup as the working redhat 9 distro. I
    > can plug in the new fc3 drive and can no longer connect. What is the
    > deal with adsl-connect with fc3? Has anyone ever gotten this to work
    > with fedora core? What is so difficult about this? Should I try a
    > diffent distro? How could something so widely used like fc3 just "not
    > work" with adsl-setup?


    Kernel had nothing to do with it, problem was spotted by Trygve Selmer in
    comp.os.linux.networking. Trygve noticed that the eth devices were
    reversed in my posted ifconfigs.


    ---------------------------------------------------------------------
    ifconfig working rehat 9 machine:
    ---------------------------------------------------------------------
    eth0 Link encap:Ethernet HWaddr 00:50:04:26:A4:62
    ---------------------------------------------------------------------
    ifconfig non-working fc3 machine:
    ---------------------------------------------------------------------
    eth1 Link encap:Ethernet HWaddr 00:50:04:26:A4:62
    ---------------------------------------------------------------------

    Swapping the ethernet cables solved the problem. Thanks everybody.

    --
    ~Ohmster
    ohmster at newsguy dot com

    --
    ~Ohmster
    ohmster at newsguy dot com

+ Reply to Thread