Sys-net not sharing internet

[paulos elias]

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" error from others which use sys-net as netvm. Until today it was working fine. I don't know what I did wrong that caused this(could be some small stuff given I am not that expert at it) and I have nothing specific I remember except rebooting the system yesterday (couple of times) and browsing grub help-list(by booting into grub and typing 'help') while at it. I desperately need help right now since I have wasted the afternoon just on this in vain.

[Mike Keehan]

On a normal Qubes installation, the default network connection for a VM
is to sys-firewall, and not to sys-net. Has your sys-firewall failed to
start?

Mike.

ps - if you get a number of these emails from me, please let me know.
I have replaced my email configuration to try to stop multiple
replies going out from my mailer.

[paulos elias]

sys-firewall starts just fine. It just doesn't have internet access.

[paulos elias]

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.

[dhorf-hfre...@hashmail.org]

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" your sys-net / sys-firewall too much and dont
know how to return them to regular configuration, try creating
new ones from scratch.
there isnt anything really magic about them, just sys-net should be
hvm with the device(s) assigned, and both sys-net and sys-fw should
have the "provides network" flag set.
(just name them sys-net2 and sys-fw2 or so)

you could also try to debug the current problem.
standard linux network debugging applies, there is nothing
really qubes-specific about this.
start by trying to ping "outward".
can sys-firewall ping sys-net?
can an appvm ping sys-firewall and/or sys-net?