Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upWhonix 12 rinetd starting before qubes-whonix-postinit replace-ips #1398
Comments
added a commit
to adrelanos/qubes-whonix
that referenced
this issue
Nov 10, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Nov 10, 2015
Member
Confirmed. I think it's happening by chance. A race condition. And a release critical bug.
See above referenced commit "added more comments to ease fixing".
These are all init scripts that matter...
- https://github.com/Whonix/qubes-whonix/blob/master/lib/systemd/system/qubes-whonix-firewall.service
- https://github.com/Whonix/qubes-whonix/blob/master/lib/systemd/system/qubes-whonix-network.service
- https://github.com/Whonix/qubes-whonix/blob/master/lib/systemd/system/qubes-whonix-postinit.service
- https://github.com/Whonix/qubes-whonix/blob/master/lib/systemd/system/qubes-whonix-sysinit.service
Please share your thoughts on any systemd unit file relation ships, After= and Before=.
qubes-whonix-postinit needs to run before rinetd, but also before Tor. And some others. Which ones should become clear by looking at the contents of the FILES variable in replace-ips script.
https://github.com/nrgaway/qubes-whonix/blob/master/usr/lib/qubes-whonix/replace-ips#L55-L79
If you have other suggestions, please have it going.
I also plan to refactor/simplify all the above systemd unit files and init stuff for Whonix 13.
Ideally we had static IPs. That would abolish the need for replace-ip's which has been discussed here:
#1143
|
Confirmed. I think it's happening by chance. A race condition. And a release critical bug. See above referenced commit "added more comments to ease fixing". These are all init scripts that matter...
Please share your thoughts on any systemd unit file relation ships, qubes-whonix-postinit needs to run before rinetd, but also before Tor. And some others. Which ones should become clear by looking at the contents of the https://github.com/nrgaway/qubes-whonix/blob/master/usr/lib/qubes-whonix/replace-ips#L55-L79 If you have other suggestions, please have it going. I also plan to refactor/simplify all the above systemd unit files and init stuff for Whonix 13. Ideally we had static IPs. That would abolish the need for replace-ip's which has been discussed here: |
added a commit
to adrelanos/qubes-whonix
that referenced
this issue
Nov 11, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
The fix is in the Whonix testers repository. Closeable. |
qubesuser commentedNov 10, 2015
In Whonix 12 the systemd rinetd service is starting after qubes-whonix-postinit, which means it loads the configuration before replace-ips has replaced the 10.152.152.10 IP, which results in local ports being redirected there and thus Tor Browser and so on not working.
In the Whonix 11 template it seemed fine, although it might be by chance.
Looks like replace-ips should invoke "systemctl reload rinetd" and some systemd dependency constraints should be added.
There might be other services in addition to rinetd with the same issues.