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 ?!
Sent using GuerrillaMail.com
Block or report abuse:
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.