That isn't a problem with the BitCoin protocol, but Instawallet's website.
iOS and Android devices support EAP-TLS, then wire any devices that you can such as the game systems (less certs to manage anyway), and do exactly what you describe for anything that can only do WEP if it's required. The extra AP should probably be in a different VLAN so that it only has access to what it needs, and doesn't allow a hole to something else in the network. Although, this is similar to puting a simple padlock on the bank vault door because the manager can't remember the combination.
If security is convienent for you, then it's easy for the hackers. In order to make it difficult for the hackers, the lowest security level has to be raised, and it will become inconvienent for you. That's the trade-off.
This neighbor sounds like he has it out for this guy, and escalated it into a turf war. It's probably only going to end by this guy giving up and wiring everything, or creating a fortress. Since he's asking on slashdot, he's probably looking to do the latter.
I agree with all of these, especially the enterprise auth. I'd use 802.1x with EAP-TLS and implement certificates that you can revoke if they're cracked. A lot of work to set up a PKI, but might be worth it.
With as much of a jerk this guy is, you should make sure to implement additional security such as IPSec or a DMZ that is only accessable via a VPN on any file storage systems that you have to prevent them from accessing or destroying personal data. More work, but probably more worth it if you have important data.
None of this will stop the deauth packets, but implementing 802.11w (2009) should help with that. Linux should be able to support it, Windows will require Win 8, and I don't know how many mobile devices implement it.
My understanding is that it requires changing (possibly creating or accepting?) a calendar event from the iOS device. Normal email flow is unaffected. I haven't tried yet as I don't think there's a way to undo it, and I don't want to have to disassociate my iPhone at this point.
Looking at my logs, I have a couple of users that are creating log events in the IIS logs every second or so. At this point it's a minor impact on our overall logging, and hasn't inflated to the point that I want to block my users. I've had a drive fill up in the past and created a scheduled tasks to remove logs older than 15 days.
I've sent my users emails to see if they are experiencing any battery or syncing issues with their devices so far, but haven't heard back from them yet.
Apparently if you update a calendar item on your iOS device, it tries to update Exchange and fails.
It then retries continuously, chewing through battery life and log files: http://wmpoweruser.com/exchange-server-acting-up-blame-those-ios-6-1-users-then-ban-them/.
Just get cheaper GPS units and make a note of when it stops sending data.
Somehow, I think Wolowitz is responsible....
IPv5 was originally designed as a streaming protocol, but they abandoned it now that everything is encapsulated in HTTP.
With Google pushing this so hard, why didn't they change the logo? They should have had one for the IPv6 crowd different from the IPv4....
You should also be able to do some naked eye observations such as:
Observe the track of the Moon across the sky over a month.
Watch the rotation of the starts over a night (or several hours)
Watch an upcomming meteor shower. The next one is the Lyrids on April 21: http://stardate.org/nightsky/meteors/
It was the Rocky Mountain News that shut down...