Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. B

    CFE bootloader update

    The 1st patch routine did not handle a variable with a space in the data. So.. vlan1ports=1 2 3 4 8* turned into vlan1ports=1 in the patched cfe. as long as you have running firmware there is no problem. However, if you ever need recovery mode, your lan ports will not work. in regard to...
  2. B

    CFE bootloader update

    I'm not too familiar with much other than dd-wrt.
  3. B

    CFE bootloader update

    @lfbb.. Those macs are created by the firmware and have to do with virtual interfaces (vlans, wds, etc.). I am not that familiar with Tomato so I don't know exactly how it works in that firmware. I do know that the list of cfe nvram variables is very short compared to what the firmware builds...
  4. B

    CFE bootloader update

    1). I used /tmp/home/root/ because that was where the extract routine put the cfe. You can use /tmp I would think. 2). Yes.. no need to put "cfe" and the end of the write command. dd-wrt calls the partition "cfe", stock asus and merlin call the partition "pmon". Note: if you have updated...
  5. B

    CFE bootloader update

    I'm a windows user so I use winscp. You must enable ssh on the router 1st to use winscp. that write command is when running dd-wrt. running a merlin build use: mtd-write -i cfe.new -d pmon this assumes that your new cfe is named "cfe.new". you do not need to unlock the cfe 1st like...
  6. B

    CFE bootloader update

    Every cfe I have seen for this router, et0 and pci/1/1 macs are the same. Either by design, or by mistake.. they are the same.
  7. B

    CFE bootloader update

    Conversation to long to start quoting a bunch of posts.. So.. you guys are saying that if you change pci/1/1's mac address in the cfe it does not change the reported mac in the gui (except for tomato).. even after you reset the router to defaults?
  8. B

    CFE bootloader update

    Well.. That isn't what I meant.. Change the mac via nvram set & commit.. Then reboot the router and make sure your macs are the way they are supposed to be (or the way you want). This is for testing without making anything permanent. If it all works out.. Then update the cfe again but...
  9. B

    CFE bootloader update

    when I was working with the cfe and helping with the port many months ago I noticed that two stated macs in the cfe are the same. the cfe has the mac(s) stated in 3 places.. The offsets are the original 1.0.1.2 cfe. If you update the cfe to 1.0.1.3, the offsets change a bit...
Top