The heat development is moderate even in horizontal installation, vertical you hardly notice it any more. A second copy, free-standing, is most topsy marginalst warm, and my power meter (the other goes down well in switching power supplies to about 4W) surrendered if the low net power consumption and shows 0 W to, even if I maximum point, the transmit power on and the little device stresse tidy. There are real well 2.5W or so.
Very understated way, are also the green status LEDs mentioned. The switch LEDs are even me soon a bit too dark. The device itself is no sound on its own, only the AC adapter (9V 0.6A) whistles / chirps a little, but even that is pretty marginal. When it comes to emission of radio frequency interference (just the part of the power supply) is at least nothing unusual noted that moderate consumption is likely to affect positively here.
I would leave it completely honest with the drive firmware, would this not partout refused to accept my desired password - there are very few special characters permitted (-, _ and even something). So it was time for my first steps with alternative firmware for such equipment. DD-WRT I did not find for v9 (there's also), so I had to resort to the more complicated to handle OpenWRT, whose latest release version 14:07 thank God comes down. First of all, it's not for absolute layman - one should not only the current (English) Wiki carefully read the device, and networking skills (IP, DNS, DHCP and Wi-Fi) are in demand, and Linux basic knowledge can not hurt. For this you can also do so much more - time circuit for WLAN, bridge mode (with or without WDS), configure VLANs itself, use the WAN port as an extra LAN port, turn off LEDs, expand with additional packages to add new functionality ...
However Too freakin 'needs sets the 4 MiB something scarcely measured flash memory of the device limits, which then ~ 460 K are available only. For HTTPS to the Web Interface's not enough, for example, even if you can make do with a SSH tunnel. After all, the main memory capacity with 32 MiB has failed pretty neat, also clocked with 550 MHz processor is more powerful than previous versions.
The throughput at close range to a notebook with AR9287 (measured with netio) is about 11 MB / s client> AP and 9 MB / s AP> Client (2x2, 40 MHz channel). With 20-MHz channel, the throughput drops to about 9.5 Mbytes / s or 5-6 MB / s. By comparison with the 1043ND v1.8 as AP to get a maximum of 15-17 MB / s (2x2, 40 MHz channel). Why sending multiple streams obviously does not work, I do not now less clear, maybe a driver issue - can it should be the hardware itself. Minimal Ping is often about 1 ms, with the 1043er (now, incidentally, also on OpenWRT) is there something less. Overall, the limitation to fall by "only" 100 Mbit Ethernet but from rather moderate.
The recipient of the 841N seems a little zustopfempfindlich, the mere activation of 1043ND one meter next to it (no overlap between the channels) already affect the throughput significantly. The 1043ND shows quite unimpressed by contrast. I can not complain, however, the receiver sensitivity, more on that later.
Number 1 has been running for more than three weeks to himself, switched-behaved (with appropriately furnished Cronjob) after closing the WLAN and early again, and after my experience with TP-Link I would think that there still remains a while now , Since the attachment was not so ideal, he sailed down twice (ahem), but ran on each unmoved - he is not sensitive to vibration before ...
Number 2 I as a wireless bridge have with relayd on "normal" AP (pseudo-Bridge) set because I have a "wireless cable" needed to bridge the repair time of a defective network socket for a printer and the main router there no WDS. The device is actually not that complicated and terribly to make completely by LuCI, you should have shot no desire only when configuring the main router.
Throughput while (main AP again my 1043ND): Nearly 10 MByte / s Bridge> AP, nearly 9 MB / s AP> Bridge. The bridge Routerchen comes here quite a sweat, 'top' reported partly more than 90% "SIRQ" and only a few percent idle. (In pure AP mode there are maybe 30-50%.)
I then still the acid test done in the basement, two floors below the main AP (transmit power +17 dBm) - here the displayed signal strength comes out barely over -80 to -77 dBm, in otherwise empty band. The notebook, which otherwise is reflected really well in my experience, brought here by more grudging registration only about 500 KB / s and sending 900 KByte / s receiving access roads. About the Bridge which were then at maximum transmission power 2-2.5 MB / s - mind you in both directions! The transmission power seems to be a very important factor, because with nominally 0 dBm (1 mW) instead of 20 dBm (100 mW) broke the throughput to less than 200 Kbytes / s. (+14 DBm When there were solid 1.5-2 MB / s.) The adapter in the notebook is thus probably simply do not have so much power, I'd 5-10 dBm value - it seems also a bit worse to hear (longer cables? less antenna gain? guess both). Remember: Everything has an end, only the sausage and the WLAN have two. ;)
So if despite unsuspected band assignment has range problems, should not only look at his wireless router critical but sometimes the terminal ...
