I'm noticing some problems running bitcoin-qt on our local wireless mesh network (
http://open-mesh.com OM2P).
When bitcoin-qt is syncing the blockchain, eventually the wireless will stop taking new http (or IMCP) requests. open connections still transmit data fine and DNS lookups resolve. Exiting the bitcoin client causes the wireless to resume working after about a minute or two.
I've been in contact with the open-mesh support team for quite some time about seemingly random wireless dropouts but the discovery that starting the bitcoin client dependably reproduces the problem for me gives me a technical path to target.
So a couple questions...
Has anyone ever seen anything similar happen when starting bitcoin on your network?
What might bitcoin be doing during the blockchain download that could cause something like this to happen? I know there are 8 connections and some downloading going on, but it can't be any more of a bandwidth hog than a big youtube or movie which both download fine without causing the network brownout.
Any help or hints you could give would be great.