I am the lead network guru for an ISP in Alaska. Our DSLAM aggregragator is a Cisco 6400 UAC. I have had this problem since PPPoE rolled out in version 4. I see a timeout with pppoe waiting for a PADO paket.
I'm trying this out now on Beta 5 and running into the same problem I had on version 4. Here's a way to replicate the problem. If I login root to the firewall, change to /var/sec/chroot-pppoe/usr/sbin and run:
./pppoe -d -A -I eth3
I get:
pppoe: Timeout waiting for PADO packets
BUT if I add -U which according to the help is:
-U -- Use Host-Unique to allow multiple PPPoE sessions.
Then I get:
./pppoe -d -A -U -I eth3
chilly:/var/sec/chroot-pppoe/usr/sbin # ./pppoe -d -A -U -I eth3
Access-Concentrator: olive-nrp1
Got a cookie: 33 13 ff ad d2 41 81 b4 0d 61 bd c5 1c e3 f8 42
AC-Ethernet-Address: 00:01:96:04:c3:09
--------------------------------------------------
Yea! It works! So, what I end up having to do is modify the file /usr/sec/chroot-pppoe/bin/DSL.sh to change the two lines:
ACOUT=$(/usr/sbin/pppoe -I $HW -A | grep -v \"\-\-\")
and
/usr/sbin/pppd-pppoe call $SYMN ipparam "$IPPARAM" pty "/usr/sbin/pppoe -I $HW -m $MSS"
to read:
ACOUT=$(/usr/sbin/pppoe -U -I $HW -A | grep -v \"\-\-\")
and
/usr/sbin/pppd-pppoe call $SYMN ipparam "$IPPARAM" pty "/usr/sbin/pppoe -U -I $HW -m $MSS"
and then everything works fine.
I am available to run debugs on our 6400 if you wish to figure out this problem.. Also on version 5 I found I have to set the MTU to 1492 to match what's on my 6400.
John Fulton
Anchorage, AK
