Ok, I did some more research and there is support for return connections over a SSH tunnel.
I modified the client config to tunnel remote 8333 ports to the miner, works.
Now, operations question;
Is there any benefit in running bitcoind at the internet connected side of the pipe, and tunnel the RPC connections over SSH, vs. tunneling the internet connections over SSH?
P.
Topic: Miner behind firewall and SSH Server behind firewall (Read 945 times)
Hi
I'm just getting started, and I need some advice on how to allow incoming connections over my SSH server that is behind a firewall.
Setup is as follows:
Miner is in a data center, network only allows outbound HTTP/80 and HTTPS/443, no inbound traffic allowed.
SSH server is running at home, behind home router.
Home router forwards incoming port 443 to SSH server on port 22.
Miner running SSH client, configured to SOCKS tunnel on 9050 to SSH server over 443.
The miner can connect out over SOCKS over SSH to the internet.
But the inbound connections from other miners coming to 8333 on my home router is not going back to the miner.
How do I go about tunneling the inbound traffic on 8333 on the home router to the miner?
P.
I'm just getting started, and I need some advice on how to allow incoming connections over my SSH server that is behind a firewall.
Setup is as follows:
Miner is in a data center, network only allows outbound HTTP/80 and HTTPS/443, no inbound traffic allowed.
SSH server is running at home, behind home router.
Home router forwards incoming port 443 to SSH server on port 22.
Miner running SSH client, configured to SOCKS tunnel on 9050 to SSH server over 443.
The miner can connect out over SOCKS over SSH to the internet.
But the inbound connections from other miners coming to 8333 on my home router is not going back to the miner.
How do I go about tunneling the inbound traffic on 8333 on the home router to the miner?
P.
Jump to: