Thanks Unman for the info and suggestion. I switched the template for sys-net to debian-8. This one came along with Qubes 3.2. sys-net had no trouble getting an IP assigned to the vif.
I then switched the template for sys-net back to fedora-25 and the IP assignment to the vif again failed as before. I then issued: qvm-prefs sys-net -s netvm none That didn't resolve the problem - sys-net still didn't get an IP assigned to the vif. Next I thought maybe it is upstream and ran the qvm-prefs against the sys-firewall: qvm-prefs sys-firewall -s netvm sys-net Same problem - no IP assigned to the sys-net vif. I use debian for some of the qubes but have not used it for the sys-net or sys-firewall. I'm also suspect that since debian-8 came with the qubes 3.2 release, it may be working just like fedora-23 has been working. I'll follow the clone and upgrade instructions to take the debian-8 and transform it into a debian-9 template and try it. If that works, I'll shift the netvm's over to debian and then reevaluate with Qubes 4.0. -- 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/f6ddc75d-612c-4434-9d76-596398c720f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
