This is a multi-part message in MIME format. --------------399499CB35F1F13DDF59ADC0 Content-Type: multipart/alternative; boundary="------------259FE06B37F8E5724E065E43" --------------259FE06B37F8E5724E065E43 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all: I recently got signed up for Qwest DSL. Currently the only working connection I have is on a Windows box. :-( I'm trying to get it up and running on an older system running Mandrake 7.0, which I intend to make into a firewall. First, I installed the Intel Pro/100+ PCI card that came with the DSL installation kit. This seemed to install OK; Mandrake automatically used the "eepro100" driver; and I set it up as eth1. Then I compiled and installed the Roaring Penguin PPPoE client; which seemed to go in OK. The problem is that the connection doesn't work; it always fails for some reason. Roaring Penguin's "how-to" told me to run it in debug mode, which I did (several times). It produced a file which shows that, among other things, PPPoE is timing out waiting for PADO packets, and it only gets three PADI packets. (I don't know what those acronyms stand for.) I then checked the lights on the Intel NIC; it claimed to be running in 100 MHz mode, which is verboten for this PPPoE client. I tried booting via a DOS floppy to configure the NIC; but all Intel's stupid DOS program would do was verify that it was indeed running in 100 MHz and full-duplex. So I downloaded Intel's Linux driver off the website, and compiled and installed it, using the option to put it in 10 MHz half duplex-- at least the 100MHz light went out. Then in DrakConf, I replaced the reference to "eepro100" with "e100" (the new driver.) I'm not sure any of this got done correctly, but at least eth1 still shows up in ifconfig. Anyway, to make a very long story short, the thing still doesn't connect. I've included the debug file in this message in hopes that someone will know how to help me. One odd thing-- since I've installed the e100 driver, an "eth2" shows up in the ifconfig listing in the debug file. Normally, eth2 doesn't show up at all, because I only have two NIC's on this thing. Does this mean my NIC is configured incorrectly? Also, when it listed the modules, e100 shows up as "unused." So maybe it's not actually using that module. I'm probably doing something dumb here, but I'm getting pretty frustrated. I'd greatly appreciate any help anyone could give me; many thanks in advance. Vaughn Treude The debug file is attached; I'm not sure if this is will go all right on the list, but for some reason I'm unable to paste it into Netscape. BTW, the version of Netscape I have that came with Mandrake 7.0 seems to be very buggy. I've heard people say good things about Konqueror, which a web search tells me is part of KDE, yet it didn't install in my version of KDE. Is that a relatively new thing? - ***************** Nakota Software, Inc. Custom Industrial Software Development --------------259FE06B37F8E5724E065E43 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all:
    I recently got signed up for Qwest DSL.  Currently the only working connection I have is on a Windows box.  :-(  I'm trying to get it up and running on an older system running Mandrake 7.0, which I intend to make into a firewall.  First, I installed the Intel Pro/100+ PCI card that came with the DSL installation kit.   This seemed to install OK; Mandrake automatically used the "eepro100" driver; and I set it up as eth1.   Then I compiled and installed the Roaring Penguin PPPoE client; which seemed to go in OK.  The problem is that the connection doesn't work; it always fails for some reason.    Roaring Penguin's "how-to" told me to run it in debug mode, which I did (several times).  It produced a file which shows that, among other things, PPPoE is timing out waiting for PADO packets, and it only gets three PADI packets.  (I don't know what those acronyms stand for.)   I then checked the lights on the Intel NIC; it claimed to be running in 100 MHz mode, which is verboten for this PPPoE client.  I tried booting via a DOS floppy to configure the NIC; but all Intel's stupid DOS program would do was verify that it was indeed running in 100 MHz and full-duplex.  So I downloaded Intel's Linux driver off the website, and compiled and installed it, using the option to put it in 10 MHz half duplex-- at least the 100MHz light went out.  Then in DrakConf, I replaced the reference to "eepro100" with "e100" (the new driver.)  I'm not sure any of this got done correctly, but at least eth1 still shows up in ifconfig.
    Anyway, to make a very long story short, the thing still doesn't connect.  I've included the debug file in this message in hopes that someone will know how to help me.  One odd thing-- since I've installed the e100 driver, an "eth2" shows up in the ifconfig listing in the debug file.  Normally, eth2 doesn't show up at all, because I only have two NIC's on this thing.  Does this mean my NIC is configured incorrectly?  Also, when it listed the modules, e100 shows up as "unused."  So maybe it's not actually using that module.
    I'm probably doing something dumb here, but I'm getting pretty frustrated.  I'd greatly appreciate any help anyone could give me; many thanks in advance.

Vaughn Treude

The debug file is attached; I'm not sure if this is will go all right on the list, but for some reason I'm unable to paste it into Netscape.  BTW, the version of Netscape I have that came with Mandrake 7.0 seems to be very buggy.  I've heard people say good things about Konqueror, which a web search tells me is part of KDE, yet it didn't install in my version of KDE.  Is that a relatively new thing?
  

- 
*****************
Nakota Software, Inc.
Custom Industrial Software Development
  --------------259FE06B37F8E5724E065E43-- --------------399499CB35F1F13DDF59ADC0 Content-Type: text/plain; charset=us-ascii; name="pppoe-debug.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pppoe-debug.txt" --------------------------------------------- * The following section contains information about your system Wed May 16 22:44:18 MST 2001 Output of uname -a Linux basil.nakota.com 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 i586 unknown --------------------------------------------- * The following section contains information about your network * interfaces. The one you chose for PPPoE should contain the words: * 'UP' and 'RUNNING'. If it does not, you probably have an Ethernet * driver problem. Output of ifconfig -a eth0 Link encap:Ethernet HWaddr 00:40:05:5F:21:F2 inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0xff80 eth1 Link encap:Ethernet HWaddr 00:D0:B7:6C:8E:61 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2938 errors:0 dropped:0 overruns:0 frame:0 TX packets:66 errors:1 dropped:0 overruns:5 carrier:1 collisions:1 txqueuelen:100 Interrupt:11 Base address:0xc000 eth2 Link encap:Ethernet HWaddr 00:D0:B7:6C:8E:61 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xff00 Memory:c3850000-c3850c40 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ppp0 Link encap:Point-to-Point Protocol POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 --------------------------------------------- * The following section contains information about kernel modules * If the module for your Ethernet card is 'tulip', you might * want to look for an updated version at http://www.scyld.com Output of lsmod Module Size Used by ppp 21036 0 (autoclean) e100 49480 0 (unused) nls_iso8859-1 2052 1 (autoclean) nls_cp437 3580 1 (autoclean) eepro100 13960 1 (autoclean) sound 64184 0 (autoclean) (unused) soundcore 3524 3 (autoclean) [sound] soundlow 300 0 (autoclean) [sound] lockd 33256 1 (autoclean) sunrpc 56612 1 (autoclean) [lockd] slhc 4392 0 [ppp] ne2k-pci 4256 1 (autoclean) 8390 6020 0 (autoclean) [ne2k-pci] vfat 11004 1 fat 32640 1 [vfat] supermount 14880 2 (autoclean) --------------------------------------------- * The following section lists your routing table. * If you have an entry which starts with '0.0.0.0', you probably * have defined a default route and gateway, and pppd will * not create a default route using your ISP. Try getting * rid of this route. Output of netstat -n -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1 192.168.1.101 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo --------------------------------------------- Contents of /etc/resolv.conf * The following section lists DNS setup. * If you can browse by IP address, but not name, suspect * a DNS problem. nameserver 206.80.192.1 nameserver 204.147.80.5 --------------------------------------------- * The following section lists /etc/ppp/options. * You should have NOTHING in that file. Contents of /etc/ppp/options --------------------------------------------- * The following section identifies your Ethernet interface * and user name. Some ISP's need 'username'; others * need 'username@isp.com'. Try both ETH=eth1; USER=tv6@qwest.net --------------------------------------------- * The following section shows the pppd command we will invoke pppd invocation /usr/bin/setsid /usr/sbin/pppd pty '/usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1 -T 80 -U -m 1412 ' noipdefault noauth default-asyncmap defaultroute hide-password nodetach local mtu 1492 mru 1492 noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp user tv6@qwest.net lcp-echo-interval 20 lcp-echo-failure 3 debug --------------------------------------------- Using interface ppp0 Connect: ppp0 <--> /dev/pts/4 sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] sent [LCP ConfReq id=0x1 ] LCP: timeout sending Config-Requests Connection terminated. Waiting for 1 child processes... script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1 -T 80 -U -m 1412 -D /tmp/pppoe-debug-2262/pppoe-debug.txt-0, pid 2332 pppoe: Timeout waiting for PADO packets Script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1 -T 80 -U -m 1412 -D /tmp/pppoe-debug-2262/pppoe-debug.txt-0 finished (pid 2332), status = 0x100 --------------------------------------------- * The following section is an extract from your log. * Look for error messages from pppd, such as * a lack of kernel support for PPP, authentication failure * etc. Extract from /var/log/messages May 16 20:13:28 basil pppd[11111]: pppd 2.3.10 started by root, uid 0 May 16 20:13:28 basil pppd[11111]: Using interface ppp0 May 16 20:13:28 basil pppd[11111]: Connect: ppp0 <--> /dev/pts/2 May 16 20:13:59 basil pppd[11111]: LCP: timeout sending Config-Requests May 16 20:13:59 basil pppd[11111]: Connection terminated. May 16 20:14:03 basil pppoe[11115]: Timeout waiting for PADO packets May 16 20:14:03 basil pppd[11111]: Exit. May 16 20:21:29 basil pppd[11262]: pppd 2.3.10 started by root, uid 0 May 16 20:21:29 basil pppd[11262]: Using interface ppp0 May 16 20:21:29 basil pppd[11262]: Connect: ppp0 <--> /dev/pts/2 May 16 20:22:00 basil pppd[11262]: LCP: timeout sending Config-Requests May 16 20:22:00 basil pppd[11262]: Connection terminated. May 16 20:22:04 basil pppoe[11264]: Timeout waiting for PADO packets May 16 20:22:04 basil pppd[11262]: Exit. May 16 22:34:20 basil kernel: registered device ppp0 May 16 22:34:20 basil pppd[1864]: pppd 2.3.10 started by root, uid 0 May 16 22:34:20 basil pppd[1864]: Using interface ppp0 May 16 22:34:20 basil pppd[1864]: local IP address 10.112.112.112 May 16 22:34:20 basil pppd[1864]: remote IP address 10.112.112.113 May 16 22:35:18 basil pppd[1864]: Starting link May 16 22:35:18 basil pppd[1864]: Serial connection established. May 16 22:35:18 basil pppd[1864]: Connect: ppp0 <--> /dev/pts/3 May 16 22:35:49 basil pppd[1864]: LCP: timeout sending Config-Requests May 16 22:35:49 basil pppd[1864]: Connection terminated. May 16 22:35:53 basil adsl-stop: Killing pppd May 16 22:35:53 basil pppd[1864]: Terminating on signal 15. May 16 22:35:53 basil pppd[1864]: Exit. May 16 22:36:07 basil pppd[1978]: pppd 2.3.10 started by root, uid 0 May 16 22:36:07 basil pppd[1978]: Using interface ppp0 May 16 22:36:07 basil pppd[1978]: Connect: ppp0 <--> /dev/pts/3 May 16 22:36:38 basil pppd[1978]: LCP: timeout sending Config-Requests May 16 22:36:38 basil pppd[1978]: Connection terminated. May 16 22:36:42 basil pppoe[1980]: Timeout waiting for PADO packets May 16 22:36:42 basil pppd[1978]: Exit. May 16 22:40:31 basil pppd[2237]: pppd 2.3.10 started by root, uid 0 May 16 22:40:31 basil pppd[2237]: Using interface ppp0 May 16 22:40:31 basil pppd[2237]: Connect: ppp0 <--> /dev/pts/4 May 16 22:41:02 basil pppd[2237]: LCP: timeout sending Config-Requests May 16 22:41:02 basil pppd[2237]: Connection terminated. May 16 22:41:06 basil pppoe[2239]: Timeout waiting for PADO packets May 16 22:41:06 basil pppd[2237]: Exit. May 16 22:44:21 basil pppd[2330]: pppd 2.3.10 started by root, uid 0 May 16 22:44:21 basil pppd[2330]: Using interface ppp0 May 16 22:44:21 basil pppd[2330]: Connect: ppp0 <--> /dev/pts/4 May 16 22:44:52 basil pppd[2330]: LCP: timeout sending Config-Requests May 16 22:44:52 basil pppd[2330]: Connection terminated. May 16 22:44:56 basil pppoe[2332]: Timeout waiting for PADO packets Wed May 16 22:44:56 MST 2001 --------------------------------------------- * 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.0 22:44:21.490 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12 SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff 01 01 00 00 01 03 00 04 1c 09 00 00 ............ 22:44:26.488 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12 SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff 01 01 00 00 01 03 00 04 1c 09 00 00 ............ 22:44:36.488 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12 SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff 01 01 00 00 01 03 00 04 1c 09 00 00 ............ --------------399499CB35F1F13DDF59ADC0--