Ok, thanks a lot for your help. I'll try it.
On Aug 5, 2016 00:04, "Qubed One" wrote:
> m...@lamarciana.com:
> >> eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is
> >> generated, so manual changes will be lost. There is a way to avoid this
> >> using
m...@lamarciana.com:
>> eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is
>> generated, so manual changes will be lost. There is a way to avoid this
>> using /etc/qubes/protected-files.d/, but I think it isn't the way to go.
>> Better adjust NetworkManager settings in sys-net,
> eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is
> generated, so manual changes will be lost. There is a way to avoid this
> using /etc/qubes/protected-files.d/, but I think it isn't the way to go.
> Better adjust NetworkManager settings in sys-net, using standard
> connection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Aug 03, 2016 at 06:50:21AM -0700, m...@lamarciana.com wrote:
> > Are you using NetworkManager in that ProxyVM?
>
> I assigned "network-manager" service through "Qubes VM Manager" to my debian
> standalone ProxyVM, but I see this disappears
> Are you using NetworkManager in that ProxyVM?
I assigned "network-manager" service through "Qubes VM Manager" to my debian
standalone ProxyVM, but I see this disappears once I start and shutdown the
machine... I tried again to be sure and I can reproduce the issue. I will
inspect it further
m...@lamarciana.com:
>> If I understand correctly, permanently changing /etc/resolv.conf in the
>> ProxyVM to show:
>>
>> nameserver 208.67.222.222
>> nameserver 208.67.220.220
>>
>> should achieve that in a standalone ProxyVM.
>
> Thanks for your answer. I thought that changing
> If I understand correctly, permanently changing /etc/resolv.conf in the
> ProxyVM to show:
>
> nameserver 208.67.222.222
> nameserver 208.67.220.220
>
> should achieve that in a standalone ProxyVM.
Thanks for your answer. I thought that changing /etc/resolv.conf by hand was
not recommended