I have a question about Phonix workstations and gateways. I want to work on a cube that is completely unrelated. For example, I want to do completely different work on cube A and cube B so that outsiders don’t know the connection between cube A and cube B at all. Therefore, I am thinking of using different templates for each cube.
However, Whonix has two elements: a workstation and a gateway. I’m thinking of making workstations possible by creating multiple workstation templates. But in this case, you don’t know how to handle the gateway. I know the gateway is connected to syswhonix.
However, I have not connected the other cubes to the gateway. Is it okay to continue like this? In this case, how can the gateway be more anonymous? By the way, both Cube A and Cube B are assumed to use the same syswhonix.
Thank you. I think the most important part for me is the content of the following article.
{How to use Multiple Whonix-Gateway}
・Article Content
{Please ensure that the newly created sys-whonix is based on the whonix-gateway-17 Template and has a distinctive VM name, so it is not confused with other VMs. Additionally, it is recommended not to run multiple Whonix-Gateway instances in parallel, see Multiple Whonix-Gateway.}
So what this is indicating is that you can’t set up multiple different Whonix-Gateways on sys-whonix, so you can’t use them at the same time?
In other words, if I use different Whonix-Gateways with different Whonix app Qubes, do I have to manually change the Whonix-Gateway that is set to sys-whonix each time?（Set Whonix-Gateway{A} to sys-whonix when using whonix app Qube {A}, and set Whonix-Gateway{B} to sys-whonix when using whonix app Qube {B}）.
Also, this time I put the question to {support} instead of {Qubes whonix}. If necessary, resubmit it to {Qubes whonix}.
Why use multiple App Qubes with the same sys-whonix? To separate applications but use the same identity.
Why use different multiple App Qubes with a different sys-whonix? To separate applications and identities.
These can be permanently configured that way. No need for repetitive configuration changes. In other words, you can configure this once and keep using it until you decide to app/remove VMs.
Thank you for your answer. First of all, I want to organize the story. In other words, because whonix is connected as follows, changing only Whonix’s AppQube does not completely maintain anonymity.
whonix-gateway > sys-whonix > whonix-appQube
Therefore, This means that you can increase anonymity by creating multiple whonix-gateway and sys-whonix as follows.
whonix-gateway１ > sys-whonix１ > whonix-appQube１
whonix-gateway２ > sys-whonix２ > whonix-appQube２
Is it the same with respect to sys-net sys-firewall as well as sys-whonix? (I think it’s the same because you said it’s the same, but this is confirmation)
But I read the article about “Tor over Tor” Scenarios, but I don’t really understand it. Are you saying that “Tor over Tor” Scenarios can happen in my way? Does that mean that if you run whonix1 and whonix2 at the same time, you have a total of 6 hops with 3 of each, but the same thing can be mixed in those hops?
Also, do I need to create a similar method for sys-net and sys-firewall for each Qube? How can it be made? If answering in this thread is not appropriate, I will start another thread.
｛Multiple sys-firewall / sys-net are purely up for Qubes, not Whonix supports.｝
That’s certainly true. However, when using whonixQube, do I need to duplicate these systems and use them for each whonixQube? This may be a question that is out of the box of this forum, but I mentioned sys-firewall/sys-net with that intention.
