Hello,
I want to install Bitcoin Core on my laptop for Testnet. For that purpose I’ll make a standalone dedicated to Bitcon Core. My question is, how can I access only that AppVM in my personal LAN to point e.g. a miner to that node?
Should I also clone sys-network for that? And I want to use sys-whonix as NetVM is it possible?
Thank you very much.
The simplest way is to connect your Standalone/AppVM to sys-net and block everything but 192.168.0.1/24 with ufw.
Another solution could be Solene'% : Script NAT on Qubes OS.
Thanks for the answer, but I need internet for the BTC node.
I will take a look on the scripts, thanks.
A network engineering ideal way is to use IPv6 and to configure each upstream qube to allow traffic to the IPv6 address of the qube that is running a service listening on a layer 4 port.
I don’t attempt this ideal way in practice. In practice I add another network interface and attach that additional network interface to the qube that listens on a layer 4 port. I also only do this with a qube that runs OpenBSD. That works for me, others mileage may vary.
Another way is you could SSH to the device on your LAN from the qube with the -L flag, using TCP port 3007 as just an example here.
user@qube $ ssh -L 127.0.0.1:3007:127.0.0.1:3007 user@miner
and then from user@miner connect to 127.0.0.1:3007.
Leveraging an SSH session to tunnel a TCP path is probably going to give you the least friction and the most consistency without modifying your network. The way Qubes has sys-net and sys-firewall “your network” includes these VMs (which are their own machines albiet virtual).