This way we can preserve the MAC and MAC+1 designation in the CFE...yet it IS generic.
Some routers use et0macaddr and et1macaddr
I've seen where they are MAC and MAC+1....and where they are both the same MAC.
The DIR-330 CFE provided above has both the et0macaddr and et1macaddr variables set to ff:ff:ff:ff:ff:ff...the nvram.bin file contains the MAC addresses for this particular model.
So....If you are going to make a MAC generic...keep the same first 3 octets like my example of the buffalo above being 00:16:01...then change the last 3 to 00:00:01 for LAN and 02 when the WAN is included as the MAC addresses.
Thank you....if you want to provide a CFE unedited...that's ok too...any that I use for distribution will be modified to a provided MAC address by the "brickee"...but stored in my database with the generic MAC structure as indicate above.
redhawk _________________ The only stupid question....is the unasked one.
Joined: 24 Jan 2010 Posts: 13 Location: Massachusetts, USA
Posted: Sat Feb 06, 2010 17:25 Post subject:
@redhawk0
I believe tornado knows about this. I have read it somewhere in the mountain of information this board has to offer. When I bricked my router, I was unable to find a lot of info on the dir330. Posted and was offered help by Tornado. I could not find the CFE online in the forums, so he sent me his CFE because I believed at the time I had corrupted it. But, I learned that ours were the same. I was able to pull down the NVRAM and found my MAC. There is mention in a few posts that it is stored there, but no info on how to restore it. That is why I have posted the clean NVRAM with the MAC info and locations for the DIR-330. I will gladly give a full copy of the NVRAM, but the data in it is dependent upon the version of firmware running. This is not that useful. With these two files (CFE and NVRAM-after adding mac) you can JTAG erase all of memory and download both files and then reboot TFTP to 192.168.0.2 any version of firmware you want...OEM, DD-WRT micro, mini and mega.
Given how many times I have bricked and restored this router, I am trying to come up with a repeatable procedure to edit the wiki for the DIR-330. I wish to be able to clearly state how to go from OEM to DD-WRT and back if needed.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Sat Feb 06, 2010 17:29 Post subject:
mild_pats_fan wrote:
@redhawk0
I believe tornado knows about this. I have read it somewhere in the mountain of information this board has to offer. When I bricked my router, I was unable to find a lot of info on the dir330. Posted and was offered help by Tornado. I could not find the CFE online in the forums, so he sent me his CFE because I believed at the time I had corrupted it. But, I learned that ours were the same. I was able to pull down the NVRAM and found my MAC. There is mention in a few posts that it is stored there, but no info on how to restore it. That is why I have posted the clean NVRAM with the MAC info and locations for the DIR-330. I will gladly give a full copy of the NVRAM, but the data in it is dependent upon the version of firmware running. This is not that useful. With these two files (CFE and NVRAM-after adding mac) you can JTAG erase all of memory and download both files and then reboot TFTP to 192.168.0.2 any version of firmware you want...OEM, DD-WRT micro, mini and mega.
Given how many times I have bricked and restored this router, I am trying to come up with a repeatable procedure to edit the wiki for the DIR-330. I wish to be able to clearly state how to go from OEM to DD-WRT and back if needed.
mpf
Very good information...I appreciate your contribution to the project. Looks like you and Tornado have things well under control then and your explanation as taught me something about the DLink structure.
Much appreciated.
redhawk _________________ The only stupid question....is the unasked one.
I make no promises, but these SHOULD be right if someone wants to take a look at them.
Thanks, looks ok at a first glance, I will see if I can find the difference in boot between these and their older brothers. _________________ Kernel panic: Aiee, killing interrupt handler!
_________________ First Network:
Linksys WRT600N V1.1 as Router - DD-WRT v24 mega
Asus WL-330g as AP - Stock Firmware
Linksys WAP54G V3.1 as AP - DD-WRT v24 micro
Linksys WRT54G V4.0 as AP - DD-WRT v24 std
Second Network:
D-Link DIR-655 as Router - Stock Firmware