/qubes-issues

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

Debian wheezy: NetworkManager in ProxyVM tries to configure eth0 using DHCP #1280

Closed
marmarek opened this Issue Oct 6, 2015 · 0 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.1
1 participant
@marmarek
@marmarek
Member

marmarek commented Oct 6, 2015

NetworkManager in wheezy is older and do not understand connection format we use in /etc/NetworkManager/system-connections/qubes-uplink-eth0. Especially it doesn't recognize address1 option, which renders connection unusable.
Since this connection is unusable, NetworkManager loads default settings, which
is to configure eth0 using DHCP. Which of course cannot work, because we do not
provide DHCP server.

@marmarek marmarek added this to the Release 3.1 milestone Oct 6, 2015

@marmarek marmarek added bug C: core P: minor C: Debian labels Oct 6, 2015

@marmarek marmarek closed this in marmarek/old-qubes-core-agent-linux@580d21a Oct 6, 2015

marmarek added a commit to marmarek/old-qubes-core-agent-linux that referenced this issue Oct 11, 2015

@marmarek
network: fix 'qubes-uplink-eth0' NetworkManager connection (#1280) 
According to the specification[1], the setting name is 'addresses', not
'address'.  The later apparently worked on some NetworkManager versions,
but for example not on the one in Debian wheezy. Also fix value
format (IP;netmask;gateway).

[1] htts://developer.gnome.org/NetworkManager/unstable/ref-settings.html

Fixes QubesOS/qubes-issues#1280

(cherry picked from commit 580d21a)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
4ac04e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment