donoban: > On 9/3/19 9:31 PM, qtpie wrote: >> The only issue I keep having with Qubes-Whonix, is that after >> suspend/resume, Whonix-GW time is out of sync and cant connect to the >> Tor network. According to Whonix the safe option is to simply not >> suspend Whonix. >> >> https://www.whonix.org/wiki/Post_Install_Advice#Network_Time_Syncing >> >> However with a laptop running from battery not using suspend is not >> really an option and manually shutting down multiple qubes is annoying. >> To do this automatically I wrote this script, but cant get it working >> yet. Any help is welcome. >> >> https://github.com/qtpies/qubes-whonix-suspending > > Do you want to restart all domains using sys-whonix netvm? Probably > there are better solutions and I think that Whonix already handles this > properly. I used it for years and I only remember problems with this on > Qubes 3. > > Check: > https://github.com/QubesOS/qubes-issues/issues/4989 > https://github.com/QubesOS/qubes-issues/issues/4939 >
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? -- 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/72f73585-4147-efbd-f1bd-79b650c16512%40disroot.org.
