sys-net stopped working after update

54 views
Skip to first unread message

Ray Brainer

unread,
Feb 28, 2017, 3:08:08 PM2/28/17
to qubes-users
I successfully installed fedora-24 template and removed fedora-23 template.
Sys-net was assigned to fedora-23.
I reassigned it to fedora-24-minimal.
No luck.

Any advice?

Chris Laprise

unread,
Feb 28, 2017, 3:30:30 PM2/28/17
to Ray Brainer, qubes-users
Did sys-net fail to start? Did it start, but network-manager won't connect?

Chris

Ray Brainer

unread,
Feb 28, 2017, 4:27:08 PM2/28/17
to qubes-users, va...@statfact.org, tas...@openmailbox.org
It starts. But there is no ip resolution.

Slideshowbob

unread,
Mar 1, 2017, 3:39:44 PM3/1/17
to qubes...@googlegroups.com
(resent because I forgot to CC qubes-users)

You could try to create a new net-vm, assign your network hardware and start this instead. Maybe it's some incompatability with the config files. If it works, set it as standard net-vm.

Another thing you could try is: before shutting down your net-vm, right-click on the NetworkManager applet and untick "Enable Networking". I have to do this when I'm in one specific wlan, because otherwise after a restart of the net-vm I won't get an ip assigned (no clue why but this reliable solves the issue for me).

slideshowbob

Steve Coleman

unread,
Mar 2, 2017, 2:07:32 PM3/2/17
to qubes-users
I ran into this and found my issue was the fedora-24-minimal did not
have tinyproxy installed.
Reply all
Reply to author
Forward
0 new messages