Cannot Access Antminer S1 Management Page Over Wifi

[sgi02]

I recently brought an old Antminer S1 out of retirement to use as a space heater, and to my surprise it works exceptionally well. I have it connected via WiFi and it has been hashing for days now without issue. The problem is that I cannot access the management page over the WiFi connection, hardwired I can access it fine. The S1 is configured as follows..

WAN - Static IP
IP - 192.168.1.99
Subnet - 255.255.255.0
Gateway - 192.168.1.1
DNS - 192.168.1.1
DNS2 - 8.8.8.8
Broadcast - N/A

WWAN - Static IP
IP - 192.168.1.42
Subnet - 255.255.255.0
Gateway - 192.168.1.1
DNS - 192.168.1.1
DNS2 - 8.8.8.8
Broadcast - N/A

I have changed IP, DNS and Broadcast values numerous times to no avail. If I try to connect to the management page via WiFi the connection times out, I can not ping the antminer via WiFi at 192.168.1.42. The strange thing is that if I plug in the ethernet connection I can access the management page at 192.168.1.99 AND 192.168.1.42. I am simply stumped here! If anyone has any suggestions to help me it would be greatly appreciated, thanks!

[1714711492]

1714711492

[1714711492]

1714711492

[1714711492]

1714711492

[1714711492]

1714711492

[1714711492]

1714711492

[deltalima]

The problem is that with both WAN and WWAN on the same subnet the S1 can receive packets on the WWAN interface but replies on the WAN interface so wifi access only work with the Ethernet cable plugged in.

Quick fix is to connect via cable and move the WAN interface to a different subnet

(e.g. IP - 192.168.2.42
Subnet - 255.255.255.0
Gateway - 192.168.2.1)

If it doesn't work you will need to give your PC a static IP address on the 192.168.2.0/24 subnet to get back into the S1 to fix things.

[VirosaGITS]

The problem is that with both WAN and WWAN on the same subnet the S1 can receive packets on the WWAN interface but replies on the WAN interface so wifi access only work with the Ethernet cable plugged in.

Quick fix is to connect via cable and move the WAN interface to a different subnet

(e.g. IP - 192.168.2.42
Subnet - 255.255.255.0
Gateway - 192.168.2.1)

If it doesn't work you will need to give your PC a static IP address on the 192.168.2.0/24 subnet to get back into the S1 to fix things.

Wow, how complicated. I just setup mine to DHCP, turn on its wifi, unplugged Ethernet and done. Went and gave it a static DHCP lease later for good measure. Running two subnet sound like a pain.

[sgi02]

Wow, how complicated. I just setup mine to DHCP, turn on its wifi, unplugged Ethernet and done. Went and gave it a static DHCP lease later for good measure. Running two subnet sound like a pain.

This was the fix. Setting WAN and WWAN to DHCP and assigning a static lease for my desired IP did the trick! Now I don't have to lug my little heater to the router every time I want to change settings or switch pools. Thanks a lot for your help!