Not working

[cheesestickstomatojuice]

Hello,

I had setup corridor on QubesOS based on the debian template. The corridor package in the Whonix repository is outdated, and it didn't work, so I manually set it up and it still doesn't work. I initially thought the issue might be related to iptables using nftables, so I switched to legacy iptables, but the problem persists. When I noticed that the corridor package in the Whonix repository was outdated, I compared the original repository on this repo, which were several commits ahead. I’ve updated to the latest commits, but it’s still not working. There are no errors, and everything appears to be fine, yet it still doesn’t function. I also switched to standalonevm, but there was no change in the outcome. Is this still maintained? and working? or am I missing something?

[rustybird]

Generally, the Qubes OS instructions are targeted at some niche use cases for development. Users of Qubes OS should usually install corridor on their router (or on a box between their router and their notebook) as a holistic fail-safe mechanism, like with any other OS. That said -

I’ve updated to the latest commits, but it’s still not working. There are no errors, and everything appears to be fine, yet it still doesn’t function.

By "doesn't function" do you mean the corridor-gateway VM is passing through all traffic of client VMs, even non-Tor traffic? Or is it blocking all traffic, even Tor traffic?

In corridor-gateway, what does sudo systemctl status 'corridor*' 'tor*' show?

[cheesestickstomatojuice]

It's showing all green, as in it's all working I looked for the ip's for the tor gateways and it was all there. There is no internet connectivity.

[rustybird]

It's showing all green

Can you paste the output of the command?

I looked for the ip's for the tor gateways and it was all there.

You mean the Tor relays in the corridor_relays ipset?

There is no internet connectivity.

That's in the "downstream" VMs for which you have set corridor-gateway as their netvm, right? How have you configured them to torify their traffic? (corridor does not proxy traffic over Tor, it merely filters traffic according to whether it is already proxied over Tor or not.)