Please, someone?
--
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
I'm already in the process of implementing this feauture (method A) in R4.0.
> dom0 doesn't store any DNS settings. Each VM forwards packets to the
> next upstream VM and the DNS decision is made at your netvm resolv.conf.
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by
>
I'm already in the process of implementing this feauture (method A) in R4.0.
> dom0 doesn't store any DNS settings. Each VM forwards packets to the
> next upstream VM and the DNS decision is made at your netvm resolv.conf.
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by
>
I'm already in the process of implementing this feauture (method A) in R4.0.
> dom0 doesn't store any DNS settings. Each VM forwards packets to the
> next upstream VM and the DNS decision is made at your netvm resolv.conf.
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by
On 10/28/2017 06:36 PM, nicholas roveda wrote:
Up to now, I've thought of 2 possible solutions:
[...]
I really need some help, maybe from the developers, to understand better these
mechanisms, to be able to implement a solution as more general as possible,
that users can adopt without