Re: [qubes-users] Tor bridge/entry node/relay question

['awokd' via qubes-users]

'gray' via qubes-users:

 I also tried 
[this](https://github.com/Osndok/qvm-expose-port/blob/master/qvm-expose-port), 
which I think is equivalent to the third section of the Qubes Firewall 
page. I tried `qubes-expose-port` both from the guest and from dom0. 
When run in dom0, it tells me I need to expose the physical networking 
device, as well, which I didn't know how to do (so perhaps it would work 
when run properly from dom0).


The above should work if you are exposing ports on the standalone qube. 
Is it directly attached to sys-firewall? If not, it should be. Dom0 is 
not the right place; as you noted, it intentionally has no networking.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/adf399f9-ab85-f2ef-7bed-6965e6de852d%40danwin1210.me.

[qubes-users] Tor bridge/entry node/relay question

['gray' via qubes-users]

Hi!

I've been trying to set up a StandAlone Qube to run a tor bridge/entry 
node/relay, but have met with tons of trouble and it seems there's basically no 
documentation on this. I've tried the instructions in 
[this](https://old.reddit.com/r/Qubes/comments/bvdx4n/qubes_run_your_own_local_tor_server_entry_node/)
 post, which allows for a working Tor connection, but doesn't allow the Qube to 
see the wider Tor network (meaning that it's essentially only my traffic over 
the bridge, which invalidates the purpose of running a bridge) and presumably 
has its own security issues. The error that indicates that this issue persists 
is the standard Tor, "Your server has not managed to confirm that its ORPort is 
reachable."

I've tried the first and second section of 
[this](https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-qubes)
 page to remedy - the first is included in the original instructions, the 
second was tried as I know relatively little about the network stack - but both 
failed. I also tried 
[this](https://github.com/Osndok/qvm-expose-port/blob/master/qvm-expose-port), 
which I think is equivalent to the third section of the Qubes Firewall page. I 
tried `qubes-expose-port` both from the guest and from dom0. When run in dom0, 
it tells me I need to expose the physical networking device, as well, which I 
didn't know how to do (so perhaps it would work when run properly from dom0).

Finally, I tried to follow the [canonical Whonix 
instructions](https://www.whonix.org/wiki/Host_a_Bridge_or_Tor_Relay#Inside_Whonix-Gateway_.E2.84.A2)
 for this, but wasn't able to get past the second step in the instructions (I 
was unable to get libvirt working, which I assume is a Qubes thing).

Anyone have experience doing this/advice?

- gray

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/gh92mqQr9DV6KmQqjnEJpi4H2MWlkcIVazceQeNQbm5WvNxcxVPoecAUyWgGdxX15TJm4KsLKdC6pBLiKPa7qAxmh6BMHQQe_LPBdjzrC2g%3D%40protonmail.com.