The reviews are logically done here, so I decided to join. I too am determining whether to go Netgear 3700 or Linksys E4200 or wait for the Netgear 3800 or 4000.
It looks like there are some pro's and cons going either WNDR3700 or E4200. What is missing is in the review is the E4200 with cards like we have in our laptops, that can do 450. That's almost like having a race, and pulling two of the plug wires on the car with the V8. A top-of-the-line Intel nics, like we use in our laptops, were less than $40 with free shipping. As indicated in the review, some of the tests were more a measure of capacity than real-world experience. However, reconnecting the other two spark plug wires has the potential to significantly impact real-world experience. Go Tim! Give is some numbers with the Ultimate-N 6300 cards.
The specs on the WNDR4000 and the E4200 seem so similar, it causes me to wonder if they are from the same supplier. I've OEMed before. You get basic firmware and components that work, and you build on that with packaging and add your own firmware bugs, er, capabilities, to differentiate yourself. It seems like Tim uncovered a CPU utilization issue with the E4200. It may be the self-imposed 10 user limit on the guest WLANs is more than just a good idea. If the WNDR4000 is based on the same components, it would be a pretty good indicator of what its potential will be, and whether it is worth waiting for.
I own an IT company. We learned by chance of the stellar performance on the 3700's 5 GHZ band while setting up a customer's system in-house. One of the guys upstairs asked what we had running that was giving him 300 mbps on 5 GHZ. In a lot of business situations you need to use 5 GHZ because microwaves operating at completely safe levels of leakage will easily nuke the tiny amount of power allowed for WLANs. We are no strangers to the 5 GHZ band, but the 3700 completely redefined where we deploy it.
We didn't go on to use the 3700 in-house because it wouldn't connect PTPP from the WLAN, while it worked perfectly on copper. That caught us completely off-guard, since normally, the physical layer has nothing to do with the protocol. We confirmed the problem with tech support. However, this was subsequently fixed in the .98 firmware release, even though they don't mention it in the release notes. Since they've fixed that, I've become sympathetic to in-house cries of anguish when someone gets nuked when someone else makes popcorn. However, now I have at least two possibilities to pick from, and perhaps a couple more soon, which is why I'm here.