How to make Ubuntu GNOME ignore VMware's vmnet8?
Multi tool use
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm using Ubuntu GNOME 15.04 and VMware Workstation 12.0, which installs its virtual interface vmnet8 for VMs' network connectivity through NAT. I'm using VMware on my laptop with ordinary eth0 and wlan0 interfaces. I don't have any other interfaces besides loopback.
Before VMware was installed, GNOME was displaying Wi-Fi interface in the top-right standard GNOME3 menu and also the Ethernet interface when the cable was plugged in. After VMware installation, it is now always displaying Ethernet interface as connected (probably due to detecting vmnet8), even though eth0 is down. A try at a visual explanation.
I have already added the following configuration lines into /etc/NetworkManager/NetworkManager.conf:
[main]
no-auto-default=*
[keyfile]
unmanaged-devices=interface-name:vmnet8
And I have also tried adding the vmnet8 definition to /etc/network/interfaces (as NetworkManager should ignore interfaces defined there), but it did not help.
So my question is how to make NetworkManager/GNOME ignore vmnet8 the way it's ignoring lo or Ethernet bridge interfaces (virbr0 for example...)?
gnome network-manager vmware ubuntu-gnome vmware-workstation
asked Nov 14 '15 at 22:19
drwsdrws
264
add a comment |
I'm using Ubuntu GNOME 15.04 and VMware Workstation 12.0, which installs its virtual interface vmnet8 for VMs' network connectivity through NAT. I'm using VMware on my laptop with ordinary eth0 and wlan0 interfaces. I don't have any other interfaces besides loopback.
Before VMware was installed, GNOME was displaying Wi-Fi interface in the top-right standard GNOME3 menu and also the Ethernet interface when the cable was plugged in. After VMware installation, it is now always displaying Ethernet interface as connected (probably due to detecting vmnet8), even though eth0 is down. A try at a visual explanation.
I have already added the following configuration lines into /etc/NetworkManager/NetworkManager.conf:
[main]
no-auto-default=*
[keyfile]
unmanaged-devices=interface-name:vmnet8
And I have also tried adding the vmnet8 definition to /etc/network/interfaces (as NetworkManager should ignore interfaces defined there), but it did not help.
So my question is how to make NetworkManager/GNOME ignore vmnet8 the way it's ignoring lo or Ethernet bridge interfaces (virbr0 for example...)?
gnome network-manager vmware ubuntu-gnome vmware-workstation
asked Nov 14 '15 at 22:19
drwsdrws
264
add a comment |
I'm using Ubuntu GNOME 15.04 and VMware Workstation 12.0, which installs its virtual interface vmnet8 for VMs' network connectivity through NAT. I'm using VMware on my laptop with ordinary eth0 and wlan0 interfaces. I don't have any other interfaces besides loopback.
Before VMware was installed, GNOME was displaying Wi-Fi interface in the top-right standard GNOME3 menu and also the Ethernet interface when the cable was plugged in. After VMware installation, it is now always displaying Ethernet interface as connected (probably due to detecting vmnet8), even though eth0 is down. A try at a visual explanation.
I have already added the following configuration lines into /etc/NetworkManager/NetworkManager.conf:
[main]
no-auto-default=*
[keyfile]
unmanaged-devices=interface-name:vmnet8
And I have also tried adding the vmnet8 definition to /etc/network/interfaces (as NetworkManager should ignore interfaces defined there), but it did not help.
So my question is how to make NetworkManager/GNOME ignore vmnet8 the way it's ignoring lo or Ethernet bridge interfaces (virbr0 for example...)?
gnome network-manager vmware ubuntu-gnome vmware-workstation
asked Nov 14 '15 at 22:19
drwsdrws
264
I'm using Ubuntu GNOME 15.04 and VMware Workstation 12.0, which installs its virtual interface vmnet8 for VMs' network connectivity through NAT. I'm using VMware on my laptop with ordinary eth0 and wlan0 interfaces. I don't have any other interfaces besides loopback.
Before VMware was installed, GNOME was displaying Wi-Fi interface in the top-right standard GNOME3 menu and also the Ethernet interface when the cable was plugged in. After VMware installation, it is now always displaying Ethernet interface as connected (probably due to detecting vmnet8), even though eth0 is down. A try at a visual explanation.
I have already added the following configuration lines into /etc/NetworkManager/NetworkManager.conf:
[main]
no-auto-default=*
[keyfile]
unmanaged-devices=interface-name:vmnet8
And I have also tried adding the vmnet8 definition to /etc/network/interfaces (as NetworkManager should ignore interfaces defined there), but it did not help.
So my question is how to make NetworkManager/GNOME ignore vmnet8 the way it's ignoring lo or Ethernet bridge interfaces (virbr0 for example...)?
gnome network-manager vmware ubuntu-gnome vmware-workstation
gnome network-manager vmware ubuntu-gnome vmware-workstation
asked Nov 14 '15 at 22:19
drwsdrws
264
asked Nov 14 '15 at 22:19
drwsdrws
264
asked Nov 14 '15 at 22:19
drwsdrws
264
asked Nov 14 '15 at 22:19
drwsdrws
264
asked Nov 14 '15 at 22:19
drwsdrws
264
264
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I haven't dealt with this personally but I did find a post that may help you. Helpful?
answered Nov 14 '15 at 22:38
yawa77yawa77
1
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
add a comment |
I found a very simple solution for this problem.
Just type:
vmware-netcfg
in a terminal and remove the NAT and Host only Network interfaces, or any you want to get rid of.
Of course you can't use them from now on. You have to use the bridged connection.
For me this connection doesn't show up in the Gnome networkmanager.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f698057%2fhow-to-make-ubuntu-gnome-ignore-vmwares-vmnet8%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I haven't dealt with this personally but I did find a post that may help you. Helpful?
answered Nov 14 '15 at 22:38
yawa77yawa77
1
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
add a comment |
I haven't dealt with this personally but I did find a post that may help you. Helpful?
answered Nov 14 '15 at 22:38
yawa77yawa77
1
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
add a comment |
I haven't dealt with this personally but I did find a post that may help you. Helpful?
answered Nov 14 '15 at 22:38
yawa77yawa77
1
I haven't dealt with this personally but I did find a post that may help you. Helpful?
answered Nov 14 '15 at 22:38
yawa77yawa77
1
answered Nov 14 '15 at 22:38
yawa77yawa77
1
answered Nov 14 '15 at 22:38
yawa77yawa77
1
answered Nov 14 '15 at 22:38
yawa77yawa77
1
1
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
add a comment |
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
Yes, it's probably the same thing. Although the difference is that VMware gets detected once and there is one menu entry too much, whereas the people commenting this bug report use VirtualBox and have many entries in the top-right menu. Thanks for the link!
– drws
Nov 16 '15 at 15:34
add a comment |
I found a very simple solution for this problem.
Just type:
vmware-netcfg
in a terminal and remove the NAT and Host only Network interfaces, or any you want to get rid of.
Of course you can't use them from now on. You have to use the bridged connection.
For me this connection doesn't show up in the Gnome networkmanager.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I found a very simple solution for this problem.
Just type:
vmware-netcfg
in a terminal and remove the NAT and Host only Network interfaces, or any you want to get rid of.
Of course you can't use them from now on. You have to use the bridged connection.
For me this connection doesn't show up in the Gnome networkmanager.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I found a very simple solution for this problem.
Just type:
vmware-netcfg
in a terminal and remove the NAT and Host only Network interfaces, or any you want to get rid of.
Of course you can't use them from now on. You have to use the bridged connection.
For me this connection doesn't show up in the Gnome networkmanager.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found a very simple solution for this problem.
Just type:
vmware-netcfg
in a terminal and remove the NAT and Host only Network interfaces, or any you want to get rid of.
Of course you can't use them from now on. You have to use the bridged connection.
For me this connection doesn't show up in the Gnome networkmanager.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
ArmenithasArmenithas
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
ArmenithasArmenithas
1
answered 6 hours ago
ArmenithasArmenithas
1
1
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Armenithas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f698057%2fhow-to-make-ubuntu-gnome-ignore-vmwares-vmnet8%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
MtCqJBtU9F3jI7J srHV2l4mE3,ujQK 6vm4vefoA W,5nx Q kPObyVcqk1 fQhuTP1o Xg,fvY40B9t6aFdlN YxVYqzWTG4cW3i
