I know the router is not officially supported by RT firmware (due to the ADM6996 switch), so I use it at my own risk, and it works for me
I was hoping that the update to 2.95 would resolve the PPPoE auth issues, since I was never able to get PPPoE working on this router with RT firmware, and especially since my ISP had stopped support for PPPoA auth a long while back (or so they claimed) and so was unable to use this router with RT firmware due to the pppoe issues. Although occasionally I could manage to connect to the ISP with PPPoA, they often seem to disable it for extended periods of time without prior warning (and support would insist on switching over to PPPoE), which was annoying.
Why do ISP do this, despite the fact that PPPoA is superior to PPPoE?
According to one source:
Anyway, I'm aware that many users had been having issues with PPPoE, and I had previously went through several threads on the issue to try and figure out any solution, but to no avail.PPPoE is a (some say ill-conceived) mechanism that utilizes PPP framing to transmit protocol packets across an ethernet. While the idea sounds silly (there is, after all, a well-defined way to do this already), it has a couple of advantages that the ISP community has latched onto. The main ones are the ability to reuse a well-honed infrastructure to support PPP termination, including serving IP addresses and other configuration information; and a pretty good way of tracking usage for billing purposes.
Background info:
1. You have no DSL sync issues, no DSL training issues
2. PPPoE does not work, regardless of DSL modem firmware you use (dsp70A, dsp71A, etc), and regardless of modulation and/or PPPoE settings.
3. PPPoA works flawlessly, if/when your ISP supports it, or your same PPPoE settings (and user/pass) work just fine with another DSL modem on the same line.
P.S. out of the box (no special DSP driver config), with 2.95 fw, I have:
/var # cat /proc/avalanche/avsar_ver
ATM Driver version:[7.01.00.10]
DSL HAL version: [7.01.00.08]
DSP Datapump version: [7.01.01.00] Annex A
SAR HAL version: [01.07.2c]
PDSP Firmware version:[0.54]
Chipset ID: [Ohio250(7200/7100A2)]
I came across a well-detailed (recent) thread, on the continued PPPoE issue:
d-link dsl 500T trouble
In that thread, user "free2rhyme" suggested that changing MAC address of the nas0 interface helped (go to post)
Preliminary steps:
1. Make sure you have only one connection:
Click setup -> look under "WAN setup", you should only see 4 items:
2. Make sure you've properly added a PPPoE connection and clicked "Apply", otherwise there will be no "nas0" interface created.New Connection
Modem (should have a green led next to it, means DSL line is synced)
YourConnectionName (or "quickstart")
Log Out
3. Go to "System" and click "Save All" to permanently save these settings.
You will not be connected yet, of course, due to the PPPoE issue, which we are about to resolve.
The DSL MAC address PPPoE fix:
1. Login to router via telnet or ssh, and run:
Code: Select all
# ps www | grep ppp
Code: Select all
833 root 2676 S /usr/sbin/pppd plugin pppoe nas0 user YOURUSERNAME password YOURPASSWORD nodetach pppoe_ses_id 0 defaultroute mru 1492 maxfail 10 lcp-echo-failure 10 lcp-echo-interval 60
2. Run:
Code: Select all
# ifconfig nas0
(note: I xx'ed out the last three octets of the HWaddr)
Code: Select all
nas0 Link encap:Ethernet HWaddr 01:E0:03:xx:xx:xx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:1386 (1.3 KiB)
3. Change your nas0 interface to another (valid) MAC address. If you had another DSL modem which you had successfully connected on the same line with PPPoE, you could copy its mac address, and only change the last octet or two of it, and use that.
Here's what I did (I xx'ed out the last three octets):
Code: Select all
# ifconfig nas0 down
# ifconfig nas0 hw ether 0013A3XXXXXX
# ifconfig nas0 up
If your PPPoE connection is not yet connected, you could try Disconnect/Connect on the connection page.
DO NOT PROCEED IF YOU HAVE NOT SUCCESSFULLY CONNECTED AT THIS POINT.
Now that we know that we can successfully connect with our new MAC Address, we want to make it permanent, so you don't have to do this manually every time the router is rebooted.
4. Find the environment variable holding the original HWaddr of the nas0 interface which you noted from step 2. You could also find it through the web-interface by going to "Status" -> "Product Information". It will be next to "DSL MAC"
Code: Select all
# printenv | grep -i 01:e0:03:XX:XX:XX
Code: Select all
HWA_3 01:e0:03:XX:XX:XX
5. Make a backup env var of that mac address, just in case, for future reference. You could simply copy the var name we got in previous step, and trail it with "_backup":
Code: Select all
# setenv HWA_3_backup 01:e0:03:XX:XX:XX
Setting bootloader environment variable: "HWA_3_backup" to "01:e0:03:XX:XX:XX"
Code: Select all
# setenv HWA_3 00:13:A3:XX:XX:XX
Setting bootloader environment variable: "HWA_3" to "00:13:A3:XX:XX:XX"
Code: Select all
# reboot
You will now also see that the new MAC address is reflected in the web-interface, from "Status" -> "Product Information", next to "DSL MAC".
Cheers