The instructions for corridor do not work on Qubes 4.2 Debian 12.
Used the Extrepo method.
Have the devs actively tested if corridor is working?
The instructions for corridor do not work on Qubes 4.2 Debian 12.
Used the Extrepo method.
Have the devs actively tested if corridor is working?
would like to set up a 75$ XMR bounty for anyone who can manage to get corridor working and provide easy instructions for it.
Setting up tor (0.4.7.16-1) …
Something or somebody made /var/lib/tor disappear.
Creating one for you again.
Something or somebody made /var/log/tor disappear.
Creating one for you again.
Created symlink /etc/systemd/system/multi-user.target.wants/tor.service → /lib/s
ystemd/system/tor.service.
Setting up ipset (7.17-1) …
Setting up corridor (2:0.11.8.9-1) …
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-data.servic
e → /lib/systemd/system/corridor-data.service.
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-forwar
ding.service → /lib/systemd/system/corridor-init-forwarding.service.
Created symlink /etc/systemd/system/systemd-networkd.service.requires/corridor-i
nit-forwarding.service → /lib/systemd/system/corridor-init-forwarding.service.
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-logged
.service → /lib/systemd/system/corridor-init-logged.service.
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-snat.s
ervice → /lib/systemd/system/corridor-init-snat.service.
Created symlink /etc/systemd/system/multi-user.target.wants/corridor.target → /l
ib/systemd/system/corridor.target.
This is the error I am stuck on when I do sudo apt install --no-install-recommends corridor
If I redo the steps, except enable corridor service in the qvm menu at the END instead of the beginning like the instructions say, I am able to install the package. However, I fail this
sudo systemctl --no-pager --full status corridor-data
sudo systemctl --no-pager --full status corridor-init-forwarding
sudo systemctl --no-pager --full status corridor-init-logged
sudo systemctl --no-pager --full status corridor-init-snat
Came across this post on the Qubes forum but figured I would post here as it seems more related to Whonix. I was able to install corridor as per the instructions but like in your case, I am also not passing those leakchecks nor do I have internet connectivity in sys-whonix when I connect it to my newly made sys-corridor vm. Came on here to try to collect the bounty as I had set up corridor with no issues a few years ago when I first discovered whonix as I wanted to test for leaks. Haven’t played with it in a while and am now coming across this issue so perhaps corridor isn’t being maintainted for 4.2? How old/new is the wiki?
You didn’t post an error.
What is failing? You need tonget into the habit of posting error messages.
Related topic:
the whonix corridor instructions don’t work and rustybird’s qubes instructions aren’t really tested as he uses corridor on his router, not on qubes. I would suggest that you learn qubes firewall rules and just set up your custom firewall to disallow non-tor traffic as corridor isn’t working. would be nice if it was though.
-long time whonix user
Proper bug report required as per: