I have set fully functional apt-cacher-ng qube and am updating all the templates and dom0 via it. Now, in general I always try to install packages first in disposables to check whatever, but for obvious reasons I cannot do that. So, what I do, I have a backup of non-apt-cacher-ng yum.repos.d and so…

I think you are confused between the processes for using the caching proxy over qrexec, (as for templates), and using it over normal networking. Looking at your extensive notes, I see that you have adopted a scattergun approach, trying many different things and changing your targets and configu…

Thanks, I have managed to set it but only if cacher is set as netVM for the qube. If any other qube is set as netVM, the error is thrown ▶ Error Is it possible sys-whonix for example to be set as netVM for the qube, yet it to updates via apt-cacher-ng? Or, I am missing something in configuration?

Yes, you are missing something. If sys-whonix is set as netvm, then all traffic is send through Tor. This means that the traffic aimed at 10.x.x.x will be routed through Tor it never has a chance to hit the caching proxy because it is encrypted by the time it hits that proxy

Thanks unman. Indeed I missed the fact and i was just intended to find out how I could bypass tor for local addresses in Qubes, but then, it turned out that this won’t work even when clearnetVM is set for AppVM. I have specifically enabled updates-proxy-setup service and disabled qubes-updates-prox…

Is there a chance i can expect some concrete advise how to set AppVm, or should I continue to investigate myself?

Is there a chance you will provide enough concrete information to allow anyone to help you? I have told you that you can configure the proxy by setting a file under /etc/apt/apt.conf.d - this is the canonical way under Debian. Provided that you do not have a netvm set which routes traffic over T…

You are probably right that I’m missing to give some info that would help. Thanks for your response, anyway. Indeed appreciated. I’ll try it again: I’m using debian-11 based app qube, named debian-11-test I have specifically disabled updates-proxy-setup service, by adding it to the Service tab, a…

[image] enmus: As a noob, I can only conclude that some package or (networking) service is installed/created during creating netVM which doesn’t happen when creating app qube. No, it’s not this, most probably. This inter-netVM can be updated only if its netVM is apt-cacher-ng too, so the same…

First of all, Thank you for such a detailed and nicely organized response. I guess it would be of immense help to other users too. [image] unman: Access using normal networking. Access using normal networking, where the proxy is not direct netvm. I just want to be short now. From point to …

qubes.UpdatesProxy * vault @anyvm deny qubes.UpdatesProxy * @anyvm @default allow target=cacher It looks, this would be the proper way so far. Still have to learn about RPC policies, I admit that while the syntax is pretty much clear, content isn’t yet (for example what + Argument is and could be…

Qubes OS Forum

How to update non-template qubes over qrexec while using apt-cahcer-ng as netVM & everything in policies talk about cacher

User Support