Sometimes posts get eaten here, thought you might have moderated rights to the thread.

TLDR:

Quote from: sxemini on August 02, 2023, 01:22:57 PM

Here

1. Not true, there seems to be a problem with localization and while it's not the 0 position it's probably a issue with 12/24 hour format as it also has problems with the date, where it seems like it's not organized properly. Some parts of the world are DD/MM/YY, where the US is MM/DD/YY.

https://i.imgur.com/aMdiLL1.jpg

2. Static IPs are a lot of tedious work, especially as your network grows. The solution would be to run a active directory, which entails a lot more work. This is something that should be built into AM as AM is made to make mining easier, not harder, and I don't believe it's beyond scope.

3. Bandaid fix and not something you want in a mission critical environment. I have something similar already setup, but you have to manage each installation and make sure they're identical at all times or bad things happen.

Don't play dev when you're not the dev. Ideally we should be working to improve a piece of software, not come up with arbitrary rules as to why things can't be fixed or improved upon.

Quote from: patrike on August 04, 2023, 08:59:22 AM

Quote from: bensam1231 on August 02, 2023, 03:35:37 AM

2. I'm running into a issue where IPs are changing on ASICs and the AM client doesn't update the current listing to reflect this. They can easily be found by scanning the network, but obviously not good. This is generally being caused by my router resetting then occasionally the miners resetting.

Could you add a Rule Action that runs a network scan and readds the miners replacing their original entry? They are uniquely identifiable at least by their MAC address.

a) A partial solution is to configure the DHCP lease time on your router to be much longer than the default. Set it to something like 10 years and it will not change IP address of a miner simply because it's down for a short while.

b) A more complete solution is to make use of a Remote Proxy that is responsible for an entire IP address range. Using the Automatic Discovery feature it will automatically find new miners and add them. You can also enable MAC address identification and it will keep track of MAC addresses to handle the case when an ASIC miner changes IP address. Awesome Miner will simply update the IP address of the existing External Miner entry to point to the new IP address.

See the article below and also the final section about MAC address identification.
https://support.awesomeminer.com/support/solutions/articles/35000085994-environment-setup-remote-proxy-for-distributing-load

1. I didn't think of setting up longer leases (already done), although another bandaid I'll see if it helps. Ideally you don't want really long leases or you end up with devices that are no longer on your network eating a IP. Weirdly enough, the only time I've seen asics pull another IP is when the rule reboots them when they're locked up. They almost never pull new IPs or change.

2. Proxy looks to be a solution, although I feel as though this functionality should already be built into AM in some way. I intended on using a action to scan for new devices after the lockup rule goes off and readding them.

I already have MAC tracking turned on. For some reason after I readd them to AM they don't take over the original entry and are added as a new entry in the list.