Ok, so I tried to enable the updates proxy in the sys-firewall consequently forcing all updates to go through the VPN, I followed the instructions outlined here - https://www.qubes-os.org/doc/software-update-vm/#updates-proxy However, as soon as I try to run the updates on one of the vmtemplate I get the error "No route to host". All the templatevm has a default route to the sys-net (10.137.1.1), notwithstanding the update should be targeting the sys-firewall. Should I change the default GW of the templatevm ?!
Thanks ---- Sent using GuerrillaMail.com Block or report abuse: https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D -- 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/33ad158b2f30014d4093277972e2b769a334%40guerrillamail.com. For more options, visit https://groups.google.com/d/optout.
