No, I've hex-patched current cfe and it is already new 1.0.1.3 (updated about a week ago).The Chief did you run the newest version of the script during your last attempt?
No, I've hex-patched current cfe and it is already new 1.0.1.3 (updated about a week ago).The Chief did you run the newest version of the script during your last attempt?
Ain't 'nvram set / nvram commit' after cfe update is enough?If you change the MACs in the CFE, you will probably need to also wipe out your settings using the WPS button, otherwise the CFE will never write the new MACs to nvram.
Ain't 'nvram set / nvram commit' after cfe update is enough?
- lfbbet0macaddr=50:46:5D:XX:YY:30
pci/1/1/macaddr=50:46:5D:XX:YY:30
pci/2/1/macaddr=50:46:5D:XX:YY:34
I see lot of talks about MAC addresses displayed on the webui. You guys should really do traffic sniffing using a tool like Wireshark to see what actual MAC addresses are used by your traffic. What gets displayed on a webui could be wrong. What matters is what gets used in your packets.
Yes Merlin...after disabling all adapters except the 2.4Ghz, Wireshark still shows data moving from xx:xx:xx:xx:xx:B0 only...and the webgui shows the 2.4Ghz as xx:xx:xx:xx:xx:B3![]()
![]()
Ok now I'm officially begging.
Would some one please list the steps to move the cfe from the router to my desktop and then how to put it back in the proper directory?
Do I need to be running Merlin's to do so?
Did you try an Hex Editor? I have this 3 MACs in my CFE:
et0macaddr=50:46:5D:XX:YY:30
pci/1/1/macaddr=50:46:5D:XX:YY:30
pci/2/1/macaddr=50:46:5D:XX:YY:34
- lfbb
However in your example you have the LAN and the 2.4ghz MAC's the same.
| Thread starter | Title | Forum | Replies | Date |
|---|---|---|---|---|
| F | ASUS RT-N66U admin interface not accessible following firmware update | ASUS N Routers & Adapters | 4 |
We use essential cookies to make this site work, and optional cookies to enhance your experience.