Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upNetworkManager does not work in ProxyVM/AppVM based on Debian 7 template #955
Comments
marmarek
added
bug
C: core
P: minor
labels
Apr 11, 2015
marmarek
added this to the
Release 3 milestone
Apr 11, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
May 18, 2015
Member
@nrgaway, can you look at this? Or should we ignore the issue since jessie is now stable?
|
@nrgaway, can you look at this? Or should we ignore the issue since jessie is now stable? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
nrgaway
May 18, 2015
I was thinking as labelling it won't fix since Jessie is now stable.
Within a few weeks Whonix will also be moved over to Jessie and I will add
support for stretch
nrgaway
commented
May 18, 2015
|
I was thinking as labelling it won't fix since Jessie is now stable.
Within a few weeks Whonix will also be moved over to Jessie and I will add
support for stretch
|
marmarek
added
the
wontfix
label
Jul 8, 2015
marmarek
closed this
Jul 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedApr 11, 2015
On Debian 7, when NetworkManager is enabled in ProxyVM/AppVM (
qvm-service VMNAME -e network-manager), startup scripts prepare static configuration for eth0 based on Qubes settings (viaxenstore/qubesdb). It is created by
setup-ipscript and the output file is/etc/NetworkManager/system-connections/qubes-uplink-eth0. Apparently NetworkManager in Debian 7 does not understand this file:And tries to configure eth0 using DHCP...
The same file works on Debian 8. It looks like this: