On 10/16/2016 08:50 AM, 4lpt9o+3m11o9qubb38o via qubes-users wrote:
You don't need to manually add the iptables rules. When enable the
'qubes-yum-proxy' on the VPNVM the rule to iptables is automatically added:
Chain PR-QBS-SERVICES (1 references)
pkts bytes target prot opt in out
On the second iptables rules I meant to past this instead:
0 0 ACCEPT tcp -- vif+ * 0.0.0.0/00.0.0.0/0
tcp dpt:8082
Sorry for the confusion
Sent using GuerrillaMail.com
Block or report abuse:
https://www.guerrillamail.com/abuse/?a=UFR2AB5NV
You don't need to manually add the iptables rules. When enable the
'qubes-yum-proxy' on the VPNVM the rule to iptables is automatically added:
Chain PR-QBS-SERVICES (1 references)
pkts bytes target prot opt in out source destination
0 0 REDIRECT tcp
On 10/15/2016 04:56 PM, 4lgaqp+cqeepdnbinsts via qubes-users wrote:
> Hi Chris,
>
> Thanks for the suggestion.
> Just to clarify, the VPN tunnel was created within the sys-firewall,
I believe the VPN set up by the instructions in the official docs
interfere with the updates proxy functionality.
T
On 10/15/2016 04:56 PM, 4lgaqp+cqeepdnbinsts via qubes-users wrote:
> Hi Chris,
>
> Thanks for the suggestion.
> Just to clarify, the VPN tunnel was created within the sys-firewall, and
> currently that's the only proxyVM that I'm using (apart from the sys-whonix),
> hence all traffic from the sy
> 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 vmte
I was finally able to put this to work! I have to set the sys-firewall as a
qubes-yum-proxy forcing also all the apt/yum traffic through the tunnel.
Everything seems to be working fine now, although I do get a warning on the
sys-firewall on the firewall settings while using the Qubes VM Manager:
On 10/15/2016 12:56 PM, 4lgaqp+cqeepdnbinsts via qubes-users wrote:
Hi Chris,
Thanks for the suggestion.
Just to clarify, the VPN tunnel was created within the sys-firewall, and
currently that's the only proxyVM that I'm using (apart from the sys-whonix),
hence all traffic from the sys-net isn
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
Unfortunately I overlooked the config. There's already an automatic rule that
whitelists all VMs that are marked to 'Allow connections to Updates proxy' to
connect to the proxy on port 8082, therefore my suggestion would not work
(specially given the fact that the rule to block all traffic is ad
Hi Chris,
Thanks for the suggestion.
Just to clarify, the VPN tunnel was created within the sys-firewall, and
currently that's the only proxyVM that I'm using (apart from the sys-whonix),
hence all traffic from the sys-net isn't encapsulated by the tunnel.
My understanding is that the sys-firewa
11 matches
Mail list logo
