Post
Topic
Board Mining (Altcoins)
Merits 1 from 1 user
Re: Official FutureBit Apollo LTC Image and Support thread
by
peetee
on 02/05/2020, 11:22:13 UTC
⭐ Merited by vapourminer (1)
Hi everyone,

I've just upgraded both of my Apollos (a batch 1 and a batch 2) to the new firmware, replaced MCU on the batch 1, etc. They're both on different networks, and the batch 2 appears to be humming along nicely.

The batch 1 is having a few issues.

1. The MCU temp seems pretty high. It's at about 81C. Is this a concern?
2. My ssh connection to the node is very unstable. It appears as though this may be related to memory(?) since the connection doesn't have as many issues during startup/shutdown. But during steady state my ssh connections either hang and never authenticate, or I authenticate and get disconnected shortly thereafter. Perhaps it's due to litecoind performing its initial synchronization to the blockchain and this will fix itself once it's caught up. I'll keep an eye on it. The web UI doesn't appear to be affected negatively and the Apollo is mining succesfully, so this is an annoyance but not necessarily a problem.
3. I'm not getting any inbound connections to my node.

Regarding the last point: my network is... different. I have the node sitting behind an edge router that ultimately breaks out into two load balanced WAN connections. How does litecoind know which public IP address to advertise to the world for getting inbound connections? Is it using some kind of STUN technique? I've coerced all outbound connections using TCP/9333 out of one specific WAN interface, but I'm not seeing anything come inbound. While my routers don't support UPnP (and even if they did I'd have disabled it ;-) I have confirmed that my port forwarding rules work fine.

Any tips on how to make sure the world sees the correct WAN IP are appreciated!