New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates proxy fails to set iptables rules in ProxyVM #1555

Closed
marmarek opened this Issue Dec 28, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@marmarek
Member

marmarek commented Dec 28, 2015

When updates proxy is started, it inserts two iptables rules:

  1. In nat table (redirect traffic directed to 10.137.255.254:8082 to the local process)
  2. In filter table to actually allow that traffic (INPUT chain)

The second one is overwritten by qubes-firewall service (running only in ProxyVM). qubes-firewall recreates all the filter table at each reload (basically when some VM is connected or disconnected from it). This means that updates proxy is pretty useless in ProxyVM.

Thanks @hdevalence for the report.

@rustybird

This comment has been minimized.

Show comment
Hide comment
@rustybird

rustybird Jun 8, 2016

There's a workaround for this in https://github.com/rustybird/qubes-updates-cache/blob/master/usr/lib/qubes/updates-cache-iptables that is kind of weird, but maybe good enough until the 4.0 firewall stuff is ready.

The file (with lines 11 and 22 changed) could be copied over to https://github.com/QubesOS/qubes-core-agent-linux/blob/master/network/iptables-updates-proxy because both commands use the same iptables rules and take the same "start"/"stop" arguments.

rustybird commented Jun 8, 2016

There's a workaround for this in https://github.com/rustybird/qubes-updates-cache/blob/master/usr/lib/qubes/updates-cache-iptables that is kind of weird, but maybe good enough until the 4.0 firewall stuff is ready.

The file (with lines 11 and 22 changed) could be copied over to https://github.com/QubesOS/qubes-core-agent-linux/blob/master/network/iptables-updates-proxy because both commands use the same iptables rules and take the same "start"/"stop" arguments.

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Feb 6, 2017

Referencing the updates doc, the proxyVM I created to handle updates in front of my VPN VM doesn't work. Its as if the proxy service only works correctly in netVMs.

So I guess a fix didn't make it into the release and that section of the doc isn't valid?

tasket commented Feb 6, 2017

Referencing the updates doc, the proxyVM I created to handle updates in front of my VPN VM doesn't work. Its as if the proxy service only works correctly in netVMs.

So I guess a fix didn't make it into the release and that section of the doc isn't valid?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment