How to configure static IP for ASIC miners? (Router Setup)

Understanding Static IP Assignment for ASIC Miners

1. Static IP configuration ensures that each ASIC miner retains the same network address across reboots and router resets, eliminating DHCP-induced connectivity fluctuations.

2. Without a static IP, miners may receive different addresses from the router’s DHCP pool, causing monitoring tools to lose visibility or fail to send shares consistently.

3. ASIC firmware typically supports both DHCP and static IP modes, but most manufacturers recommend using DHCP with DHCP reservation as a safer alternative to manual static assignment.

4. Assigning static IPs directly on the miner requires accurate knowledge of subnet mask, gateway, and DNS server values—mismatches here will result in total network isolation.

5. Some newer Bitmain and MicroBT models allow static IP setup via web interface or SSH, while older units rely solely on DHCP reservation through the router.

Router-Based DHCP Reservation Method

1. Log into the router’s admin panel using its default gateway IP—commonly 192.168.1.1 or 192.168.0.1—via a browser on a connected device.

2. Navigate to LAN settings, DHCP server configuration, or client list—exact naming varies by vendor (e.g., “Attached Devices” on ASUS, “DHCP Reservation” on TP-Link).

3. Identify each miner by its MAC address, which is usually printed on the label at the bottom or back of the unit and visible in the miner’s web UI under Network or Status.

4. Reserve a specific IP address for each MAC entry, ensuring the reserved address falls within the router’s DHCP range but does not overlap with other reserved or manually assigned devices.

5. Save changes and reboot the router if prompted; afterward, power-cycle each miner to force renewal of its lease with the reserved address.

Direct Static IP Configuration on Miner

1. Access the miner’s web interface by entering its current IP address into a browser—this IP can be discovered via ARP scan or router client list.

2. Go to Network Settings or System → Network and disable DHCP; switch to Manual or Static IP mode.

3. Enter a fixed IPv4 address outside the DHCP pool—for example, if the router uses 192.168.1.100–192.168.1.199, select 192.168.1.50.

4. Input matching subnet mask (usually 255.255.255.0), default gateway (router’s LAN IP), and at least one DNS server (e.g., 8.8.8.8 or 1.1.1.1).

5. Apply settings and confirm connectivity by pinging the miner from another device and verifying hash rate reporting in the mining pool dashboard.

Network Segmentation and VLAN Considerations

1. Large-scale deployments often isolate miners on a dedicated VLAN to prevent broadcast storms and reduce interference with office or residential traffic.

2. Enterprise-grade routers like Ubiquiti EdgeRouter or MikroTik support VLAN tagging per port, allowing physical separation without additional cabling.

3. When using VLANs, ensure the miner’s static IP resides in the correct subnet—for instance, VLAN 10 with 10.0.10.0/24 requires corresponding gateway and DNS entries aligned to that scope.

4. Some ASICs do not support VLAN ID configuration natively, requiring untagged access ports or managed switches configured for PVID forwarding.

5. Misconfigured VLAN membership may cause the miner to obtain an IP from the wrong DHCP scope—or none at all—leading to silent failures during stratum handshakes.

Frequently Asked Questions

Q: Can I assign the same static IP to two different miners?No. Duplicate IPs cause ARP conflicts, resulting in intermittent or complete loss of communication for both devices. Each miner must have a unique IPv4 address within the same subnet.

Q: Why does my miner show “No Internet” even after static IP setup?This usually indicates incorrect gateway or DNS configuration. Verify the gateway matches the router’s LAN IP and that DNS servers respond to queries using tools like nslookup or dig from a connected PC.

Q: Do I need to update firewall rules when using static IPs?Only if your router enforces zone-based policies. Static assignment itself does not trigger firewall changes, but persistent IPs make it easier to create precise inbound/outbound rules for remote management or pool whitelisting.

Q: Will changing the miner’s static IP affect its connection to the mining pool?No, provided the new IP maintains full Layer 3 reachability to the pool’s stratum endpoint. Pool connectivity depends on routing and port accessibility—not the miner’s internal address assignment.