Re: [qubes-users] Re: how to get the update proxy working again

2018-01-08 Thread 'Tom Zander' via qubes-users
On Monday, 8 January 2018 06:53:46 GMT khmartin...@gmail.com wrote:
> Is your new net vm different than "sys-net"? This caused me problems too.
> One solution is to rename the new net vm to "sys-net" or you can edit
> this file in dom0:
> 
> /etc/qubes-rpc/policy/qubes.UpdatesProxy
> 
> In that file there is a line that says target=sys-net.
> I changed it to the same name as my net vm.

That did the trick!
Thanks, I would never have found that...
-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5511262.ciHnklDXiN%40mail.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: how to get the update proxy working again

2018-01-07 Thread khmartinsen
Is your new net vm different than "sys-net"? This caused me problems too. One 
solution is to rename the new net vm to "sys-net" or you can edit this file in 
dom0:

/etc/qubes-rpc/policy/qubes.UpdatesProxy

In that file there is a line that says target=sys-net.
I changed it to the same name as my net vm.

This is because the new update proxy works using qrexec as I understand.
>From the qubes R4.0 release notes:
 - Template VMs do not have network interface by default, qrexec-based updates 
proxy is used instead

There are probably plans to make this update automatically by the qubes.xml 
file or something else. Hope this helped!

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2da5e7b9-1a35-4d37-972d-c1010bc31a6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: how to get the update proxy working again

2018-01-07 Thread khmartinsen
Are you new net vm different than "sys-net"? This caused me problems. One 
solution is to remane it ot sys-net or you can edit the file in dom0:

/etc/qubes-rpc/policy/qubes.UpdatesProxy

In that file there is a line that says target=sys-net.
I changed it to the same name as my net vm.

This is because the new update proxy works using qrexec as I understand.
>From the qubes R4.0 release notes:
 - Template VMs do not have network interface by default, qrexec-based updates 
proxy is used instead

There are probably plans to make this update automatically by the qubes.xml 
file or something else. Hope this helped!

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/90ef88cd-043d-4607-89b4-6ee78ee505aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.