Open Port Inbound 44158 for Helium

Hello!

wrightcomply said:

Do I have the rule correct? 

No, over the Firewall Rule you should use:

• "Any" on the "Source Network and Devices".
• Your Firewall WAN IPv4 on the "Destination Networks", you can use a #Port host since those are updated in real-time with the Interface IP.
• And on "Services" you need to create a new one with the necessary 44158 Port. (With either TCP or UDP, or both if necessary.)

On the NAT Rule you should:

• Leave "Original Source" as "Any".
• "Inbound Interface" should be your WAN Interface.
• "Original Destination" is the same host that you use on the Firewall Rule, with is the correct #Port host that is linked to the WAN Interface.
• "Translated Destination" is the client (Miner IPv4) in which the Traffic will be sent. (NAT'ed)
• "Original Service" is the same service of the Firewall Rule, as stated above.

Those steps above should cover everything.

EDIT: Looking at GitHub, the necessary ports are:

•  44158/TCP
• 1680/UDP

You should use those ports above while creating a new "Service".

NMAP Scan on my Public IP

On the Firewall Rule, change the "Destination Zone" to the correct zone in which the device (miner) is located, such as either LAN or DMZ.

Also, is HTTPS and SSH really necessary? Isn't those two ports (1680 & 44158) enough?

Changed.  Helium suggests 443 and 22 open for support and updates, but I removed it since my NMAP scan shows it open.

I'm perplexed why I get the ports I pasted in, but not 1680 or 44158? I'm still relayed on my bobcatminer and NMAP is still not finding 1680 or 44158 open.  I'm about ready to get rid of Sophos and switch to SonicWall.

You will need two rules, one for incoming traffic originating outside of your network and one for outgoing traffic originating inside you network.

Ian

I have both for incoming and outgoing traffic.  NMAP still shows no open port for 44158 or 1680

I have both for incoming and outgoing traffic.  NMAP still shows no open port for 44158 or 1680