Jared has been working to improve the network configuration for these rigs. Here's how it works now:
-on boot up, the card will get the dhcp range of your network
-it will then take the .249 of this range
-you'll find the updated web UI at this address
-there's a network config button at the bottom that will let you change the IP of the rig
Jared also added a shutdown button at the bottom of the web UI. Use this before powering down - we find that SD cards survive a lot better this way.
More cards arrived today and more are going out
Cheers,
Dave
Just to clarify a bit further... Hypothetical example...
You receive your mining rig, and your home computer's IP address is 192.168.2.104 (You can find this by going to start -> run -> type 'cmd' and press enter -> ipconfig )
You set it up. Once it boots up, it
**will take an extra 30-50 seconds to reconfigure the IP.** Let me repeat that because it is going to trip someone up. It should reconfigure its IP automatically for you, but it
**will take an extra 30-50 seconds!!** Someone over-eager might log in and start messing with it during this configuration process, but that might cause them problems that they would need to correct later.
When it boots up, for the first few seconds it will not be able to access the network. Then it will work its DHCP magic, and voila! It will move the rig to 192.168.2.249, matching your computer's scheme of 192.168.2.xxx. For the vast majority of customers this means you won't even need to hook up a TV/monitor, although this script can't handle every possible network setup out there. If you bought multiple rigs or you already have a device on *.249, it will search downwards until it finds an open(not pingable) IP and move it there.
After that point you should be able to modify the IP as you desire on the web interface. If it hasn't reconfigured itself to a proper IP(*.249, *.248, ... etc) within 2 minutes, something went wrong with the script. You'll need to connect a monitor/TV and check it that way. If you send me the /home/pi/.ip_results.log file I can improve this system.
One final note, this **should** not affect any customers at all, but there are two compiled miner's in /opt/bitfury/chainminer/. The one that is setup there and should be the only one that customers need to interact with is miner_customer(which should be equal to miner, you can check by doing 'cmp miner miner_customer' and it should not produce any output). miner_warehouse is only used if the system detects that the miner appears to be in the 100TH mine warehouse(compiled identically, just looks elsewhere to get work from rather than the built-in stratums), which should not happen to any customers.
Let me know if you encounter any problems or bugs with the system. We tested it on several different network setups before shipping it out, but there are so many different types of network setups that I can't possibly hope that it will work properly for all of them.
Jared
Poll
