On Thu, Sep 05, 2019 at 12:23:13PM +0200, donoban wrote: > On 9/5/19 11:41 AM, qtpie wrote:> My usecase is this: suspend a laptop > with sys-whonix and whonix appvms > > running, then resume it a few hours later. > > > > After resume Tor lost connection, re-connection fails until i manually > > sync time on sys-net then > > @sys-firewall 'sudo ntpdate [timeserver] > > @sys-whonix 'sudo qvm-sync-clock' > > @sys-whonix 'sudo systemctl restart [email protected]' > > > > Is this also you usecase? You do not expierence any issues after > > suspend/resume on qubes 4 with Tor running? > > > > Ouch yes, usually after suspend/resume I had to run just: > @sys-whonix 'sudo systemctl restart [email protected]' > > > Currently I am not using whonix, I am testing with minimal fedora torvm[1]. > > It seems stable. I don't have problems with suspend/resume and I skipped > the sync clock steps [2]. Probably it's less anonymous than Whonix, but > for me seems fine. > > [1] https://hackmd.io/JIXLStC-Sbq8rr1mjomCDQ
You know there's a Qubes package for that? (deprecated but still buildable.) I have my own fork for a torVM which includes Qubes firewall support, which Whonix doesn't provide. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190905143831.GA22350%40thirdeyesecurity.org.
