New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no network connectivity for newly started AppVM? #257

Closed
marmarek opened this Issue Mar 8, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 1 Jul 2011 22:21 UTC
Every time I start a new AppVM, I get a message from the firewall that iptables-restore failed, which results in no networking the the newly started AppVM. I the must open firewallVM prefs in qubes manager, click ok, which forces reload of firewall rules, and then it works fine.

This happens on one machine only (on the other works fine).

I'm using core v1.6.4 in both VMs and Dom0.

Migrated-From: https://wiki.qubes-os.org/ticket/257

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 14 Jul 2011 00:26 UTC
If you are using domain names in firewall configuration, this can be caused by unconfigured /etc/resolv.conf.

Fixed here:
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=4fd6cf98d54b85c742fb4afa3e3245499fd2adc3

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 14 Jul 2011 00:26 UTC
If you are using domain names in firewall configuration, this can be caused by unconfigured /etc/resolv.conf.

Fixed here:
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=4fd6cf98d54b85c742fb4afa3e3245499fd2adc3

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 14 Jul 2011 09:39 UTC
No, this problem occurs even for domains that have no rules at all (wide open to internet). This problem also seems to be a race condition -- it happens only sometimes (TM), more or less 50% of time I start a new AppVM.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 14 Jul 2011 09:39 UTC
No, this problem occurs even for domains that have no rules at all (wide open to internet). This problem also seems to be a race condition -- it happens only sometimes (TM), more or less 50% of time I start a new AppVM.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 14 Jul 2011 17:33 UTC
The firewall rules are common, so it is enough that some (running) AppVM uses domain names in firewall rules to fail its loading.

But this can be also problem with setting DNAT to DNS servers (which cannot be set properly without /etc/resolv.conf) - also fixed by this commit.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 14 Jul 2011 17:33 UTC
The firewall rules are common, so it is enough that some (running) AppVM uses domain names in firewall rules to fail its loading.

But this can be also problem with setting DNAT to DNS servers (which cannot be set properly without /etc/resolv.conf) - also fixed by this commit.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 16 Jul 2011 23:38 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 16 Jul 2011 23:38 UTC

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment