This will enable the DHCP server. You don't want this. Instead change the protocol type from Static IP to DHCP Client and save and apply the changes.
Thanks for the info. I thought that that option looked suspect. That's why I asked in my first post if there was a DHCP Client option. Thanks for confirming that there is.
If anyone is interested, I'll put together a quick starter guide for anyone who wants to switch from the default settings to a dynamic assigned IP setup...
I think that I'm all set. But given that the set up is confusing, I think that it would be generally helpful to other people to keep them from messing up their units.
What an odd choice for Bitmain to expose all of this router functionality. It's more like setting up a firewall than a miner. Instead of suppressing this complexity and providing a mining appliance (which I suspect most people are interested in), they've exposed a bunch of stuff that people don't need.
The sense that I have is that under the hood the two blades are Ethernet devices and front end is a router for them. So I guess people could build out large scale farms made of many blades under one or more routers. Maybe in that case it would make sense to enable a DHCP server for the blades. But if anyone was building out that kind of infrastructure, I assume they'd be using their own router or firewall, not the one that comes with the S3.
So again; exposing this functionality is just an unnecessary complication. But they were probably in a rush to ship, so UI refinements were probably pretty low on the priority list
