On Friday, 3 May 2019 17:00:20 UTC+3, awokd wrote: > [email protected]: > > > I've found the issue. I have separate sys-net for cabled eth and > > sys-net-wifi. Today I tried to update and it failed but I happened to see > > that sys-net was started (I was on wifi and had turned sys-net off). > > > > I then connected through cable and the update was successful. > > > > Is there a way to setup that Fedora (and Debian) updates happen through a > > specific network, like my sys-net-wifi? > > > > Thanks in advance > > > Edit /etc/qubes-rpc/policy/qubes.UpdatesProxy, and update the Template > line. You'll probably also want to change where dom0 updates in > qubes-prefs updatevm.
Hi, Thanks a lot, I've updated /etc/qubes-rpc/policy/qubes.UpdatesProxy and will test next time an update is available. I've issued "qubes-prefs updatevm" on dom0 terminal and the answer was "sys-firewall-wifi", which is my firewall VM and not sys-net or sys-net-firewall. Should it work over the wifi? I do not remember having updated qubes-prefs updatevm when I created sys-net-wifi/sys-firewall-wifi. Regards -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b6d7ce38-39e4-43dd-9abe-e2fd7b527e7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
