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 [2] https://hackmd.io/JIXLStC-Sbq8rr1mjomCDQ#Fix-clock-synchronization-issue-after-suspendresume-cycle-in-dom0 -- 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/5e95cec2-c4ce-390a-afa2-66ee1223f1ec%40riseup.net.
