My take on the "tinfoil cage" is that is is rather far-fetched.
Agreed.It seems that there is an Android on WiFi router problem, It has to do with it ignoring the DHCP lease times.
Full information can be found on theAndroid Open Source Project – Issue Tracker: ”DHCP client ignores lease time”: https://code.google.com/p/android/issues/detail?id=11236
Full information can be found on theAndroid Open Source Project – Issue Tracker: ”DHCP client ignores lease time”: https://code.google.com/p/android/issues/detail?id=11236
Also agreed. I think you were the same user that posted this in another thread or even earlier in this thread, so thanks for continuing to do so.
I find that is a much, much more likely issue than other speculative ideas put forth.
One thing that may help is to make sure the Cube(s) and any proxy are on addresses outside the DHCP pool so there will not be any collisions.
With or without Android insure the proxy address is either statically assigned outside the DHCP pool or set to always get the same address from DHCP, this will prevent a new proxy address stopping mining.
With or without Android insure the proxy address is either statically assigned outside the DHCP pool or set to always get the same address from DHCP, this will prevent a new proxy address stopping mining.
This is my practice by default so perhaps that's how I've avoided it on my own networks and others I've helped with Cubes do the set-up for.
That just seems basic standard good practices to me but maybe I don't fall into the "everyday man" category anymore.
) 