PPPoE config problem, more info
Vaughn Treude
plug-discuss@lists.PLUG.phoenix.az.us
Sat, 19 May 2001 22:43:37 -0700
--------------0A69EED19BD32309C00AD112
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello everybody,
A couple of days ago, I posted a message requesting help getting my
Qwest DSL connection working on a Linux box. Since I didn't receive any
replies, I kept trying other approaches. It's still not working, but I
have a lot more info I can share. Maybe this time my message will make
a bit more sense and somebody will be able to point me in the right
direction.
When I signed up for Qwest, they sent me a Cisco 678 modem and an
Intel Pro100+ PCI ethernet card. I was able to get the Cisco modem to
talk to two of my Windows boxes (with existing LAN cards) so I know it
works. I installed the Intel ethernet card in my Mandrake box, and it
recognized it right away and installed the eepro100 driver. I
configured it as eth1 because I had an existing eth0 ethernet connection
to my LAN.
Since I'm running Mandrake 7.0, I don't have any kernel-based PPPoE
support. I downloaded the source for the Roaring Penguin PPPoE client
and compiled and installed it without a hitch. I also followed their
setup instructions to enter the info for my new ISP (Qwest.) The PPPoE
daemon would start and run, but when I started Netscape, I wasn't able
to browse the web or check my email. So I ran the Roaring Penguin
client in its debug mode. I fixed a few minor problems, but the same
thing would always happen-- it would time out trying to get PADO
packets, and also send just three PADI packets and quit.
Following RP's suggestions, I made sure the Intel card was
configured to run at 10Mbps half-duplex. (I used the mii-diag
utility.) It still didn't work. Then, on searching Google for relevant
postings, I found a message that suggested using Intel's e100 driver
instead of eepro100. I tried this also; it appeared to work, but still
wouldn't connect.
I'm going to insert part of the Roaring Penguin debug log, in case
some kind soul would like to glance for it for any obvious problems.
I'll add some comments here and there. I also notices a strange error
in /var/log/messages that happened when I run the adsl start script:
May 19 22:09:43 basil modprobe: can't locate module char-major-108
I believe this means that I'm missing some sort of driver but how do I
figure out which?
Anyway, the following stuff is the debug dump. I've deleted some of the
repetitive and extraneous stuff. Thanks very much in advance for any
help you can give me.
Vaughn Treude
---------------------------------------------
* The following section contains information about your system
Sat May 19 21:25:54 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:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 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.99 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1095 errors:0 dropped:0 overruns:0 frame:0
TX packets:177 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xff00 Memory:c383c000-c383cc40
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:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 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 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.99 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 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/2
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5c020ad8>]
< deleted 9 more repetitions of the above.>
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-1108/pppoe-debug.txt-0, pid
1178
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-1108/pppoe-debug.txt-0 finished
(pid 1178), 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
<Deleted a lot of the following, because there were many similar
retries:>
May 19 20:18:15 basil pppd[2709]: pppd 2.3.10 started by root, uid 0
May 19 20:18:15 basil pppd[2709]: Using interface ppp0
May 19 20:18:15 basil pppd[2709]: local IP address 10.112.112.112
May 19 20:18:15 basil pppd[2709]: remote IP address 10.112.112.113
May 19 20:21:25 basil adsl-stop: Killing pppd
May 19 20:21:25 basil pppd[2709]: Terminating on signal 15.
May 19 20:21:25 basil pppd[2709]: Exit.
May 19 20:21:31 basil pppd[2751]: pppd 2.3.10 started by root, uid 0
May 19 20:21:31 basil pppd[2751]: Using interface ppp0
May 19 20:21:32 basil pppd[2751]: local IP address 10.112.112.112
May 19 20:21:32 basil pppd[2751]: remote IP address 10.112.112.113
May 19 20:22:06 basil pppd[2751]: Starting link
May 19 20:22:07 basil pppd[2751]: Serial connection established.
May 19 20:22:07 basil pppd[2751]: Connect: ppp0 <--> /dev/pts/4
May 19 20:22:38 basil pppd[2751]: LCP: timeout sending Config-Requests
May 19 20:22:38 basil pppd[2751]: Connection terminated.
May 19 20:22:42 basil pppoe[2772]: Timeout waiting for PADO packets
May 19 20:22:42 basil pppd[2751]: tcflush failed: Input/output error
May 19 20:26:45 basil pppd[2751]: Starting link
May 19 20:26:45 basil pppd[2751]: Serial connection established.
May 19 20:26:45 basil pppd[2751]: Connect: ppp0 <--> /dev/pts/4
May 19 20:27:16 basil pppd[2751]: LCP: timeout sending Config-Requests
May 19 20:27:16 basil pppd[2751]: Connection terminated.
May 19 20:27:20 basil pppoe[2775]: Timeout waiting for PADO packets
May 19 20:27:21 basil pppd[2751]: tcflush failed: Input/output error
May 19 20:28:14 basil adsl-stop: Killing pppd
May 19 20:28:14 basil pppd[2751]: Terminating on signal 15.
May 19 20:28:15 basil pppd[2751]: Exit.
May 19 20:40:00 basil kernel: PPP: ppp line discipline successfully
unregistered
May 19 21:21:57 basil kernel: registered device ppp0
May 19 21:21:57 basil pppd[979]: pppd 2.3.10 started by root, uid 0
May 19 21:21:57 basil pppd[979]: Using interface ppp0
May 19 21:21:57 basil pppd[979]: Connect: ppp0 <--> /dev/pts/2
May 19 21:22:29 basil pppd[979]: LCP: timeout sending Config-Requests
May 19 21:22:29 basil pppd[979]: Connection terminated.
May 19 21:22:32 basil pppoe[983]: Timeout waiting for PADO packets
May 19 21:22:32 basil pppd[979]: Exit.
May 19 21:24:10 basil pppd[1094]: pppd 2.3.10 started by root, uid 0
May 19 21:24:10 basil pppd[1094]: Using interface ppp0
May 19 21:24:10 basil pppd[1094]: Connect: ppp0 <--> /dev/pts/2
May 19 21:24:42 basil pppd[1094]: LCP: timeout sending Config-Requests
May 19 21:24:42 basil pppd[1094]: Connection terminated.
May 19 21:24:46 basil pppoe[1096]: Timeout waiting for PADO packets
May 19 21:24:46 basil pppd[1094]: Exit.
May 19 21:25:58 basil pppd[1176]: pppd 2.3.10 started by root, uid 0
May 19 21:25:58 basil pppd[1176]: Using interface ppp0
May 19 21:25:58 basil pppd[1176]: Connect: ppp0 <--> /dev/pts/2
May 19 21:26:29 basil pppd[1176]: LCP: timeout sending Config-Requests
May 19 21:26:29 basil pppd[1176]: Connection terminated.
May 19 21:26:33 basil pppoe[1178]: Timeout waiting for PADO packets
May 19 21:26:33 basil pppd[1176]: Exit.
Sat May 19 21:26:34 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
21:25:58.730 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 9a 04 00 00 ............
21:26:03.724 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 9a 04 00 00 ............
21:26:13.735 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 9a 04 00 00 ............
--
*****************
Nakota Software, Inc.
Custom Industrial Software Development
--------------0A69EED19BD32309C00AD112
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hello everybody,
<br> A couple of days ago, I posted a message requesting
help getting my Qwest DSL connection working on a Linux box. Since
I didn't receive any replies, I kept trying other approaches. It's
still not working, but I have a lot more info I can share. Maybe
this time my message will make a bit more sense and somebody will be able
to point me in the right direction.
<br> When I signed up for Qwest, they sent me a Cisco
678 modem and an Intel Pro100+ PCI ethernet card. I was able to get
the Cisco modem to talk to two of my Windows boxes (with existing LAN cards)
so I know it works. I installed the Intel ethernet card in my Mandrake
box, and it recognized it right away and installed the eepro100 driver.
I configured it as eth1 because I had an existing eth0 ethernet connection
to my LAN.
<br> Since I'm running Mandrake 7.0, I don't have any
kernel-based PPPoE support. I downloaded the source for the Roaring
Penguin PPPoE client and compiled and installed it without a hitch.
I also followed their setup instructions to enter the info for my new ISP
(Qwest.) The PPPoE daemon would start and run, but when I started
Netscape, I wasn't able to browse the web or check my email.
So I ran the Roaring Penguin client in its debug mode. I fixed a
few minor problems, but the same thing would always happen-- it would time
out trying to get PADO packets, and also send just three PADI packets and
quit.
<br> Following RP's suggestions, I made sure the Intel
card was configured to run at 10Mbps half-duplex. (I used the mii-diag
utility.) It still didn't work. Then, on searching Google for
relevant postings, I found a message that suggested using Intel's e100
driver instead of eepro100. I tried this also; it appeared to work,
but still wouldn't connect.
<br> I'm going to insert part of the Roaring Penguin
debug log, in case some kind soul would like to glance for it for any obvious
problems. I'll add some comments here and there. I also
notices a strange error in /var/log/messages that happened when I run the
adsl start script:
<p>May 19 22:09:43 basil modprobe: can't locate module char-major-108
<p>I believe this means that I'm missing some sort of driver but how do
I figure out which?
<p>Anyway, the following stuff is the debug dump. I've deleted some
of the repetitive and extraneous stuff. Thanks very much in
advance for any help you can give me.
<p>Vaughn Treude
<p>---------------------------------------------
<br>* The following section contains information about your system
<br>Sat May 19 21:25:54 MST 2001
<br>Output of uname -a
<br>Linux basil.nakota.com 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000
i586 unknown
<br>---------------------------------------------
<br>* The following section contains information about your network
<br>* interfaces. The one you chose for PPPoE should contain the
words:
<br>* 'UP' and 'RUNNING'. If it does not, you probably have an Ethernet
<br>* driver problem.
<br>Output of ifconfig -a
<br>eth0 Link encap:Ethernet HWaddr
00:40:05:5F:21:F2
<br> inet addr:192.168.1.101
Bcast:192.168.1.255 Mask:255.255.255.0
<br> UP BROADCAST
RUNNING MULTICAST MTU:1500 Metric:1
<br> RX packets:9
errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:29
errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0
txqueuelen:100
<br> Interrupt:10
Base address:0xff80
<p>eth1 Link encap:Ethernet HWaddr
00:D0:B7:6C:8E:61
<br> inet addr:10.0.0.99
Bcast:10.255.255.255 Mask:255.0.0.0
<br> UP BROADCAST
RUNNING MULTICAST MTU:1500 Metric:1
<br> RX packets:1095
errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:177
errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0
txqueuelen:100
<br> Interrupt:11
Base address:0xff00 Memory:c383c000-c383cc40
<p>lo Link encap:Local Loopback
<br> inet addr:127.0.0.1
Mask:255.0.0.0
<br> UP LOOPBACK
RUNNING MTU:3924 Metric:1
<br> RX packets:56
errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:56
errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0
txqueuelen:0
<p>ppp0 Link encap:Point-to-Point Protocol
<br> POINTOPOINT
NOARP MULTICAST MTU:1500 Metric:1
<br> RX packets:0
errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:10
errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0
txqueuelen:10
<p>---------------------------------------------
<br>* The following section lists your routing table.
<br>* If you have an entry which starts with '0.0.0.0', you probably
<br>* have defined a default route and gateway, and pppd will
<br>* not create a default route using your ISP. Try getting
<br>* rid of this route.
<br>Output of netstat -n -r
<br>Kernel IP routing table
<br>Destination Gateway
Genmask Flags
MSS Window irtt Iface
<br>10.0.0.99 0.0.0.0
255.255.255.255 UH 0 0
0 eth1
<br>192.168.1.101 0.0.0.0
255.255.255.255 UH 0 0
0 eth0
<br>192.168.1.0 0.0.0.0
255.255.255.0 U
0 0 0 eth0
<br>10.0.0.0 0.0.0.0
255.0.0.0 U
0 0 0 eth1
<br>127.0.0.0 0.0.0.0
255.0.0.0 U
0 0 0 lo
<br>---------------------------------------------
<br>Contents of /etc/resolv.conf
<br>* The following section lists DNS setup.
<br>* If you can browse by IP address, but not name, suspect
<br>* a DNS problem.
<br>nameserver 206.80.192.1
<br>nameserver 204.147.80.5
<br>* The following section shows the pppd command we will invoke
<br>pppd invocation
<br>/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
<br>---------------------------------------------
<br>Using interface ppp0
<br>Connect: ppp0 <--> /dev/pts/2
<br>sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5c020ad8>]
<br>< deleted 9 more repetitions of the above.>
<br>LCP: timeout sending Config-Requests
<br>Connection terminated.
<br>Waiting for 1 child processes...
<br> script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe
-I eth1 -T 80 -U -m 1412 -D /tmp/pppoe-debug-1108/pppoe-debug.txt-0,
pid 1178
<br>pppoe: Timeout waiting for PADO packets
<br>Script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1
-T 80 -U -m 1412 -D /tmp/pppoe-debug-1108/pppoe-debug.txt-0
finished (pid 1178), status = 0x100
<br>---------------------------------------------
<br>* The following section is an extract from your log.
<br>* Look for error messages from pppd, such as
<br>* a lack of kernel support for PPP, authentication failure
<br>* etc.
<br>Extract from /var/log/messages
<br><Deleted a lot of the following, because there were many similar
retries:>
<br>May 19 20:18:15 basil pppd[2709]: pppd 2.3.10 started by root, uid
0
<br>May 19 20:18:15 basil pppd[2709]: Using interface ppp0
<br>May 19 20:18:15 basil pppd[2709]: local IP address 10.112.112.112
<br>May 19 20:18:15 basil pppd[2709]: remote IP address 10.112.112.113
<br>May 19 20:21:25 basil adsl-stop: Killing pppd
<br>May 19 20:21:25 basil pppd[2709]: Terminating on signal 15.
<br>May 19 20:21:25 basil pppd[2709]: Exit.
<br>May 19 20:21:31 basil pppd[2751]: pppd 2.3.10 started by root, uid
0
<br>May 19 20:21:31 basil pppd[2751]: Using interface ppp0
<br>May 19 20:21:32 basil pppd[2751]: local IP address 10.112.112.112
<br>May 19 20:21:32 basil pppd[2751]: remote IP address 10.112.112.113
<br>May 19 20:22:06 basil pppd[2751]: Starting link
<br>May 19 20:22:07 basil pppd[2751]: Serial connection established.
<br>May 19 20:22:07 basil pppd[2751]: Connect: ppp0 <--> /dev/pts/4
<br>May 19 20:22:38 basil pppd[2751]: LCP: timeout sending Config-Requests
<br>May 19 20:22:38 basil pppd[2751]: Connection terminated.
<br>May 19 20:22:42 basil pppoe[2772]: Timeout waiting for PADO packets
<br>May 19 20:22:42 basil pppd[2751]: tcflush failed: Input/output error
<br>May 19 20:26:45 basil pppd[2751]: Starting link
<br>May 19 20:26:45 basil pppd[2751]: Serial connection established.
<br>May 19 20:26:45 basil pppd[2751]: Connect: ppp0 <--> /dev/pts/4
<br>May 19 20:27:16 basil pppd[2751]: LCP: timeout sending Config-Requests
<br>May 19 20:27:16 basil pppd[2751]: Connection terminated.
<br>May 19 20:27:20 basil pppoe[2775]: Timeout waiting for PADO packets
<br>May 19 20:27:21 basil pppd[2751]: tcflush failed: Input/output error
<br>May 19 20:28:14 basil adsl-stop: Killing pppd
<br>May 19 20:28:14 basil pppd[2751]: Terminating on signal 15.
<br>May 19 20:28:15 basil pppd[2751]: Exit.
<br>May 19 20:40:00 basil kernel: PPP: ppp line discipline successfully
unregistered
<br>May 19 21:21:57 basil kernel: registered device ppp0
<br>May 19 21:21:57 basil pppd[979]: pppd 2.3.10 started by root, uid 0
<br>May 19 21:21:57 basil pppd[979]: Using interface ppp0
<br>May 19 21:21:57 basil pppd[979]: Connect: ppp0 <--> /dev/pts/2
<br>May 19 21:22:29 basil pppd[979]: LCP: timeout sending Config-Requests
<br>May 19 21:22:29 basil pppd[979]: Connection terminated.
<br>May 19 21:22:32 basil pppoe[983]: Timeout waiting for PADO packets
<br>May 19 21:22:32 basil pppd[979]: Exit.
<br>May 19 21:24:10 basil pppd[1094]: pppd 2.3.10 started by root, uid
0
<br>May 19 21:24:10 basil pppd[1094]: Using interface ppp0
<br>May 19 21:24:10 basil pppd[1094]: Connect: ppp0 <--> /dev/pts/2
<br>May 19 21:24:42 basil pppd[1094]: LCP: timeout sending Config-Requests
<br>May 19 21:24:42 basil pppd[1094]: Connection terminated.
<br>May 19 21:24:46 basil pppoe[1096]: Timeout waiting for PADO packets
<br>May 19 21:24:46 basil pppd[1094]: Exit.
<br>May 19 21:25:58 basil pppd[1176]: pppd 2.3.10 started by root, uid
0
<br>May 19 21:25:58 basil pppd[1176]: Using interface ppp0
<br>May 19 21:25:58 basil pppd[1176]: Connect: ppp0 <--> /dev/pts/2
<br>May 19 21:26:29 basil pppd[1176]: LCP: timeout sending Config-Requests
<br>May 19 21:26:29 basil pppd[1176]: Connection terminated.
<br>May 19 21:26:33 basil pppoe[1178]: Timeout waiting for PADO packets
<br>May 19 21:26:33 basil pppd[1176]: Exit.
<br>Sat May 19 21:26:34 MST 2001
<br>---------------------------------------------
<br>* The following section is a dump of the packets
<br>* sent and received by rp-pppoe. If you don't see
<br>* any output, it's an Ethernet driver problem. If you only
<br>* see three PADI packets and nothing else, check your cables
<br>* and modem. Make sure the modem lights flash when you try
<br>* to connect. Check that your Ethernet card is in
<br>* half-duplex, 10Mb/s mode. If all else fails,
<br>* try using pppoe-sniff.
<br>rp-pppoe debugging dump
<br>rp-pppoe-3.0
<br>21:25:58.730 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
<br>SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff
<br>01 01 00 00 01 03 00 04 9a 04 00 00
............
<p>21:26:03.724 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
<br>SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff
<br>01 01 00 00 01 03 00 04 9a 04 00 00
............
<p>21:26:13.735 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
<br>SourceAddr 00:d0:b7:6c:8e:61 DestAddr ff:ff:ff:ff:ff:ff
<br>01 01 00 00 01 03 00 04 9a 04 00 00
............
<br>
<pre>--
*****************
Nakota Software, Inc.
Custom Industrial Software Development</pre>
<p>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br> </html>
--------------0A69EED19BD32309C00AD112--