Some advice as your set these up
Background: we have purchased two of these over the past two years. Both are still working fine. This review is for anyone who is setting one up soon or just wants some inside details before they buy.How we use them: we have the first one (purchased in 2010) on the remote end of a point-to-point wireless system. The wireless spans about 3/4 mile and the remote side would simply drop every few weeks. Attempts to use the wireless ap's built-in reboot feature did not work as it seemed to require a hard power-down/power-up on the remote ap side in order to cycle and reconnect, so we purchased one of these 9258t devices. This solution has been working great. We have the 9258t hard power down the device for 30 seconds every week in the wee hours of sunday morning. The wireless has not had an issue since. The second unit (purchased jan 2012) is for a remote office with a problematic dsl connection. We have a cradlepoint mbr1200 there with a verizon failover (side note: that works really well.. Highly recommend cradlepoint devices). The issue was that once failed over to the verizon connection we were using up valuable data on our data plan, so we needed to fail back to the dsl as soon as possible. As anyone with dsl knows, the modems often require a hard reboot in order to reconnect. The 9258t sits there beside the dsl and pings the dns of the dsl provider.. If it drops more than 20 pings, it starts rebooting the dsl. The 9258t replaced a $250 unit (different brand) from circa 2008 that never did properly handle the ping issue.General comments: as noted by others, the documentation is very poor. The newest unit (jan 2012) has slightly better documentation on the cd.. But still expect to spend some time poking around and guessing. The "insert" photocopy that comes in the box and is supposed to detail the power-cycle-on-ping is probably more confusing than just reading the screens yourself. As well, getting the power-cycle-on-ping to work as desired is tedious. Best advice is to set it to the most simple configuration you can think of first, and then progressively try the various settings over time. In our case the trick was the noechocount setting of 20 which means it will fail to ping 20 times before it power cycles.. That gave the cradlepoint time to failover and then time after a few minutes following the dsl reboot to see the dsl and failback. Page 21 in the new manual (v 1.52) is the best place to start.Advice on the password: the default login is admin and 12345678. You want to change that immediately if this will be internet-connected. Nowhere in the original documentation (and nowhere that i have yet seen in the new documentation) does it tell you that the password limit is 8 characters. Why does that matter? It will let you set a password longer than 8 characters, but it will not actually use that password. Rather, it will just use the first 8 characters of it. So, for example, if you set your password as being johndoe2012, the actual password will be johndoe2. And you will be sitting there typing johndoe2012 forever and getting "login failed" messages.Advice on the e-mail feature: off the top, let me note that the e-mail feature has a mind of its own. We thought at first that it was failing to send because of some communications issue with our e-mail server at times.. But now the second 9258t has the same issues and is using a different e-mail server.. So the problem is most likely touchy firmware. The issues we have seen mostly are delayed or missing alerts.. When a outlet cycles it should e-mail us, but either it does not or it waits about 1 hour and then sends an e-mail. The e-mails themselves are lacking in detail.. An actual e-mail from the system: "power3 turn on by someone at time::2012:02:22:10:05:00 .. Dev power from :192.168.26.4 time:2012:02:22:10:05:00 powerid:1 :2 :3". Power3 is the power port, "someone" appears to be what the system uses when it reboots something on timer, and "dev power" is the name we assigned port 3. The powerid part is a bit of a mystery. Anyway, when setting up e-mail alerts do not get split with the "username" field.. It seems to reject domains so yourdomain\johndoe or johndoe@yourdomain.Local will not work in our experience. Just use the flat johndoe so long as your server accepts that. As well, in the sender field use the whole e-mail address. The new firmware seems to catch this (i.E. If you use just johndoe there instead of johndoe@yourdomain.Com it will prompt you). The old firmware did not and simply failed to send. We have had the best results when leaving the pop3server field blank.Conclusion: that about does it. I gave it four stars because it works mostly as expected. The documentation and touchy settings/results for e-mail/pings knock off a star, otherwise it would be five. These are pretty simple devices but likely not easy for home users.. A moderate level of network understanding is something i would recommend to help you get the most from the units.. Ymmv. But with a little testing and config time they work as well as the more expensive units out there.