On Tue, Jan 07, 2020 at 10:42:22AM -0800, paulos elias wrote:
> sys-firewall starts just fine. It just doesn't have internet access.
you mentioned using a very nonstandard network setup earlier.
have you tried just using a plain qubes default network setup?
does that work?
if you "customized"
And for default thing you said, I have been using sys-firewall as netvm for
other appvms this whole time as you would expect. It was all normal until today.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
sys-firewall starts just fine. It just doesn't have internet access.
--
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.
On Tue, 7 Jan 2020 07:10:53 -0800 (PST)
paulos elias wrote:
> I have been using qubes for over a month and everything was working fine
> and in good shape until today. Today I opened up my PC and found out that
> sys-net has internet access but not other appvms whose netvm is sys-net. I
> can
I have been using qubes for over a month and everything was working fine and in
good shape until today. Today I opened up my PC and found out that sys-net has
internet access but not other appvms whose netvm is sys-net. I can do pinging
and all from sys-net but I always get "host unreachable"
