Marek Marczykowski-Górecki: > On Thu, Jun 30, 2016 at 10:27:00PM +0000, Patrick Schleizer wrote: >> Marek Marczykowski-Górecki: >>> On Thu, Jun 30, 2016 at 08:31:00PM +0000, Patrick Schleizer wrote: >>>> As I noticed, when the VM is upgraded to R3.2 but dom0 stays at R3.1, >>>> this breaks qubes-gui-agent in the VM. >>> >>>> [1] What about the other way around...? I upgraded dom0 R3.2 but left >>>> whonix-gw / anon-whonix at R3.1. This broke networking inside Whonix and >>>> I have not been able yet to fix that or determine the cause. Is this to >>>> be expected? >>> >>> Can you elaborate? I don't recall any change introducing incompatibility >>> in this direction. There may be some non-working new features, but that >>> should be all, at least in theory... >>> >>> > >> Not much to elaborate at this time unfortunately. > >> - Tor does not connect anymore. Stops at 80% bootstrapping. >> - After unloading Whonix firewall [1] for debugging purposes and logging >> in as user "clearnet", it was not possible to "ping 8.8.8.8". (icmp >> filtered by sys-firewall IP.) > >> Did you test if Whonix works with/in R3.2 yet? > > Yes, it works fine on my system. > > Even though I haven't upgraded qubes-specific packages there to R3.2 > yet. So exactly the case you described as not working... > > And finally it survive system suspend! Yes, I have upgraded to Whonix > 13. > >
It is not related to R3.1 vs R3.2 at all indeed. Reported a bug. sys-firewall broken, does not function as ProxyVM in R3.2 https://github.com/QubesOS/qubes-issues/issues/2141 Cheers, Patrick -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d7b2d2d1-0412-d96a-4a2b-a408190818dd%40riseup.net. For more options, visit https://groups.google.com/d/optout.
