Joined: 01 May 2009 Posts: 274 Location: San Jose, Ca
Posted: Thu Jun 10, 2010 5:22 Post subject:
So is the E3000 exactly like the WRT610N V2? _________________ E3000 K2.6 Eko 16758 Mega
E3000 CB K2.6 EKO 16758 STD USB NAS
WRT610N V2 CB K2.6 Eko15337 STD Nokaid
WRT310N V2 CB K2.6 BS 15362 STD Nokaid
Old model and new model all have the exact same hardware under the hood (same processor, same switch, same PCB). Only difference is that the new ones have a different CFE that allocates a larger space for nvram (most likely for their Cisco Connect software settings).
As I see in your sig you already have a WRT610Nv2. No reason for you to get an E3000 then. Both work the same and the average person doesn't need that larger nvram.
Old model and new model all have the exact same hardware under the hood (same processor, same switch, same PCB). Only difference is that the new ones have a different CFE that allocates a larger space for nvram (most likely for their Cisco Connect software settings).
BlCa` wrote:
Is E2000 reset button working properly or is it plagued with the same bug as 320n's ?
The E2000 PCB has been changed and has got a higher hardware revision than the WRT320N.
The change is the reset button which now is working in the E2000. _________________ Kernel panic: Aiee, killing interrupt handler!
I have a E2000 and have loaded both dd-wrt.v24-14584_NEWD-2_K2.6_big and dd-wrt.v24-14567_NEWD-2_K2.6_std_usb_ftp. One thing I noticed was when I selected a specific wireless channel it always changed back to "Auto" when it was saved or applied -- this happened with both firmware listed above.
Joined: 05 Dec 2009 Posts: 377 Location: Toronto, Canada
Posted: Thu Jun 10, 2010 17:09 Post subject:
pharma wrote:
I have a E2000 and have loaded both dd-wrt.v24-14584_NEWD-2_K2.6_big and dd-wrt.v24-14567_NEWD-2_K2.6_std_usb_ftp. One thing I noticed was when I selected a specific wireless channel it always changed back to "Auto" when it was saved or applied -- this happened with both firmware listed above.
Joined: 31 May 2010 Posts: 6 Location: San Francisco, CA, USA
Posted: Thu Jun 10, 2010 17:45 Post subject:
At first, big thanks Eko and everybody else who helped to make this happens!
Got 14584 big working on my E3000.
Most functionality works as expected.
Considerably faster than WL500gPv2 I had before.
However, 2.4GHz G signal strength gives less coverage than WL500pPv2 (Likely will keep ASUS for legacy G devices and printer).
Minor possible bug is that router's CPU is reported as 4716, while it should be 4718 (?). (I assumed that 4718 is the one with 5Ghz radio and 4716 is only 2.4Ghz)
root@E3000:~# cat /proc/cpuinfo
system type : Broadcom BCM4716 chip rev 1
processor : 0
cpu model : MIPS 74K V4.0
BogoMIPS : 239.20
wait instruction : no
microsecond timers : yes
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : yes
ASEs implemented : mips16 dsp
shadow register sets : 1
VCED exceptions : not available
VCEI exceptions : not available
Other notes:
went straight from Cisco's web interface to flashing with 14584 big, waited extra 2 minutes for reboot.
Firefox 3.6.3 on OSX 10.6.3 still showed cached version of Cisco's web interface. Browser restart solved the issue.
After enabling jffs it's size was reported incorrectly. Soft reboot corrected the issue.
Router reboots with no issues, no need to underclock.
I'll get my USB drive and printer connected soon: will test its functionality next (gotta move to current Optware style: had own tree of scripts since v23) _________________ WRT54GL
WRTSL54GS
WL500gPv2
RT-N16
WL520gU
E3000
Minor possible bug is that router's CPU is reported as 4716, while it should be 4718 (?). (I assumed that 4718 is the one with 5Ghz radio and 4716 is only 2.4Ghz)
root@E3000:~# cat /proc/cpuinfo
system type : Broadcom BCM4716 chip rev 1
processor : 0
cpu model : MIPS 74K V4.0
BogoMIPS : 239.20
wait instruction : no
microsecond timers : yes
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : yes
ASEs implemented : mips16 dsp
shadow register sets : 1
VCED exceptions : not available
VCEI exceptions : not available
4716/17/18 do all share the same cpu core and report themselves as 4716. _________________ Kernel panic: Aiee, killing interrupt handler!
Loaded the big version by loading the small version with hard reset before small and after big and several default loads inbetween and after. Seems good so far, few things to note, not sure how big of a deal they are.
5GHz AP defaulted to disabled, not sure if that's intended or not, but the clients couldn't see the 5.0 AP even though it was set to mixed in the wireless tab and said the radio was on in the wireless status tab until the whole router was rebooted.
I saw the memory information blank bug that was reported a few pages back but that cleared when I reset to factory defaults, which makes me think those people also need to reset factory defaults or better yet hard reset...
I just got this router Sunday so didn't bother playing around with the firmware settings past security much since this version was coming out "soon", but I did see a speed doubling with some clients when I enabled 40MHz in the 5GHz range. Connectivity on this router even with default firmware was much better than old 310 I had, so will be watching to make sure the FW upgrade doesn't change that...
One question I had was since the max ports for 8MB RAM is 1024 and max ports for 32MB is 4096, should the max ports for 64MB be 8192? I don't personally NEED that many, but if the hardware can hack it shouldn't the UI let it?