New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

R3.0: qubes-tor requires frequent restarts #1298

Closed
andrewdavidwong opened this Issue Oct 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@andrewdavidwong
Member

andrewdavidwong commented Oct 8, 2015

I'm not exactly sure what the problem is, but I've noticed that, compared to R2, torvm in R3.0 is rather unreliable. Even if the torvm is already running and sudo service qubes-tor restart shows that everything is fine, starting a new AppVM which uses the torvm as its netvm will result in that AppVM having no Tor access. After manually restarting qubes-tor (sudo service qubes-tor restart in the torvm), the AppVM has Tor access.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 10, 2015

Member

Are you using standard or minimal template here?

Member

marmarek commented Oct 10, 2015

Are you using standard or minimal template here?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 10, 2015

Member

I can't reproduce it with fedora-21-minmal template. There is a bug in udev rule - missing restart word, but this only means that the service will not be automatically restarted when new AppVM is connected.
Do you remember why it was there? As said before - even without that restart (the broken one), newly connected AppVMs are working fine for me.

Can you compare iptables (filter and nat tables) and routing table when such access is broken and after qubes-tor service restart?

Member

marmarek commented Oct 10, 2015

I can't reproduce it with fedora-21-minmal template. There is a bug in udev rule - missing restart word, but this only means that the service will not be automatically restarted when new AppVM is connected.
Do you remember why it was there? As said before - even without that restart (the broken one), newly connected AppVMs are working fine for me.

Can you compare iptables (filter and nat tables) and routing table when such access is broken and after qubes-tor service restart?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 11, 2015

Member

Hm, I haven't been able to reproduce it anymore either. Feel free to close. I'll comment here again if I can find some useful info to share.

Member

andrewdavidwong commented Oct 11, 2015

Hm, I haven't been able to reproduce it anymore either. Feel free to close. I'll comment here again if I can find some useful info to share.

@marmarek marmarek closed this Oct 11, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment