On Wed, Aug 02, 2017 at 07:01:15AM -0700, [email protected] wrote: > I've been doing more digging and came across an FAQ that suggested checking: > systemctl enable NetworkManager-dispatcher.service > > In reviewing the fedora-23 and 25 templates, the service is enabled in both. > > This morning I shutdown all qubes and brought sys-net up under fedora-25. > The network interfaces showed enp0s0 and lo - both properly plumbed and I > could ping the external world. But there was no vif interface. > NetworkManager-dispatcher.service showed it ran successfully. > > I then started sys-firewall (also under fedora-25). When sys-firewall > started successfully, I looked at the network interfaces on sys-net and now > vif10.0 was added, but it carries no inet or inet6 IP addresses. > > I'm not finding any logs in dom0 or sys-net that would tell me why the vif > didn't get an IP. Any suggestions on where I might look for the problem? >
I've noticed after one of the recent updates, that my Debian qubes sometimes dont get allocated an IP address on first connection - particularly if I change netvm. (I dont use Fedora) What works for me is just running the connection again - qvm-prefs <qube> -s netvm <netvm> After the second "bump" the IP address is allocated as expected. I haven't bothered to debug. I'd be interested to know if you see this behaviour when using Debian templates, and if it's particular to sys-net or if it affects any netvm, including sys-firewall. NetworkManager-dispatcher is an old service that should trigger on change in external IP - I dont think it's relevant to your issue. It's expected that there wont be a vif interface until you attach a qube downstream. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170802165535.u22fny66bn7iijaq%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
