jsmiddleton4
Very Senior Member
Yes and its the same as the LAN MAC.
Yes and its the same as the LAN MAC.
I tried to flash Shibby 102 just now, but strangely, the reset button doesn't work with it. It flashes ok, but its GUI doesn't respond.Taurean75, I had the same problem. Upgraded CFE, used restoration utility to upgrade to tomato-K26USB-NVRAM64K-1.28.0500.5MIPSR2Toastman-RT-N-Ext, unable to communicate with router. Restoration utility back to Merlins, all OK. Held reset, turned, continued holding reset for ~30 seconds. Left it sit a few minutes then powered off. Did same routine with wireless button (not sure which does full reset). Once again used restore to install tomato-K26USB-NVRAM64K-1.28.0500.5MIPSR2Toastman-RT-N-Ext, able to connect. According to the manual, holding reset for more than 5 seconds (router already on) is full reset, try this as well.
Jan 1 02:00:38 Samba Server: daemon is started
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:38 kernel: vlan1: received packet with own address as source address
Jan 1 02:00:48 kernel: printk: 32 messages suppressed.
Jan 1 02:00:48 kernel: vlan1: received packet with own address as source address
Jan 1 02:09:09 kernel: vlan1: received packet with own address as source address
Jan 1 02:09:10 kernel: vlan1: received packet with own address as source address
Jan 1 02:09:11 kernel: vlan1: received packet with own address as source address
Jan 1 02:09:13 kernel: vlan1: received packet with own address as source address
Jan 1 02:10:23 kernel: vlan1: received packet with own address as source address
Jan 1 02:10:23 kernel: vlan1: received packet with own address as source address
Jan 1 02:10:56 kernel: vlan1: received packet with own address as source address
Jan 1 02:10:58 kernel: vlan1: received packet with own address as source address
Jan 1 02:14:08 kernel: vlan1: received packet with own address as source address
Jan 1 02:14:18 kernel: vlan1: received packet with own address as source address
Jan 1 02:15:27 kernel: vlan1: received packet with own address as source address
Jan 1 02:15:27 kernel: vlan1: received packet with own address as source address
Jan 1 02:21:19 kernel: vlan1: received packet with own address as source address
Jan 1 02:21:19 kernel: vlan1: received packet with own address as source address
Jan 1 02:28:34 kernel: vlan1: received packet with own address as source address
Jan 1 02:28:34 kernel: vlan1: received packet with own address as source address
Jan 1 02:36:26 kernel: vlan1: received packet with own address as source address
Jan 1 02:36:26 kernel: vlan1: received packet with own address as source address
Jan 1 02:45:45 kernel: vlan1: received packet with own address as source address
Jan 1 02:45:45 kernel: vlan1: received packet with own address as source address
Jan 1 02:55:49 kernel: vlan1: received packet with own address as source address
Jan 1 02:55:49 kernel: vlan1: received packet with own address as source address
Jan 1 03:06:43 kernel: vlan1: received packet with own address as source address
Jan 1 03:06:43 kernel: vlan1: received packet with own address as source address
Jan 1 03:18:53 kernel: vlan1: received packet with own address as source address
Jan 1 03:18:53 kernel: vlan1: received packet with own address as source address
Jan 1 03:31:01 kernel: vlan1: received packet with own address as source address
Jan 1 03:31:01 kernel: vlan1: received packet with own address as source address
Jan 1 03:43:07 kernel: vlan1: received packet with own address as source address
Jan 1 03:43:07 kernel: vlan1: received packet with own address as source address
Jan 1 03:55:14 kernel: vlan1: received packet with own address as source address
Jan 1 03:55:14 kernel: vlan1: received packet with own address as source address
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.
et0macaddr=C8:60:00:00:00:00 @ offset 0x4C1 (this is the mac from the sticker of your router)
pci/1/1/macaddr=C8:60:00:00:00:00 @ offset 0x64D (this mac is the same as et0macaddr)
pci/2/1/macaddr=C8:60:00:00:00:04 @ offset 0xB3C (this is et0macaddr + 4)
In the origional cfe, notice that et0 and pci/1/1 are the same?
you can change the mac via telnet and if it works like you quys want it to, then upgrade / update the cfe again changing the mac in the cfe.
nvram set pci/1/1/macaddr="xx:xx:xx:xx:xx:xx" (xx:~ = et0 + 1)
nvram commit
reboot
The mac thing may be by design, or an Asus mistake (they did ship the router with 32k nvram to begin with.. big mistake)
Well.. That isn't what I meant..barry....
Thanks and very helpful.
So change the MAC and then when we run the CFE updater script it reads the existing information, which will have the updated MAC address and write the new CFE with the new MAC?
From then on, MAC's all different?
If we've already done the update can we update it again?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!