VirtualBox - Ubuntu 16.04 Guest no Internet access with chome with NAT
I have a virtual machine with a Ubuntu 16.04 guest and two network interfaces
- First interface: NAT
- Second interface: Bridge
I want to access the guest from my host and I want to access a second ethernet device from the guest. The device is connected with the host over a switch. I can ping the host, the external device and 8.8.8.8with my current setup from the guest, but I don´t have any internet access (chrome stucks at "resolving host").
When I deactivate the bridge the internet access does work, but not with the active bridge.
ifconfig gives me the following output
What is wrong?
ubuntu networking virtualbox
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
add a comment |
I have a virtual machine with a Ubuntu 16.04 guest and two network interfaces
- First interface: NAT
- Second interface: Bridge
I want to access the guest from my host and I want to access a second ethernet device from the guest. The device is connected with the host over a switch. I can ping the host, the external device and 8.8.8.8with my current setup from the guest, but I don´t have any internet access (chrome stucks at "resolving host").
When I deactivate the bridge the internet access does work, but not with the active bridge.
ifconfig gives me the following output
What is wrong?
ubuntu networking virtualbox
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
1
Probably the second (bridge) interface is creating an entry in/etc/resolv.confwith a bad DNS server, or pointing to a DNS server that can not reach the internet.
– Stephen Harris
Dec 24 '18 at 22:42
It was the right tip. Thank you. It works after changing the nameserver to8.8.8.8by hand. How can I set this automatically?
– Kampi
Dec 24 '18 at 22:48
1
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add8.8.8.8, 8.8.8.4in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)
– Kampi
Dec 25 '18 at 8:20
add a comment |
I have a virtual machine with a Ubuntu 16.04 guest and two network interfaces
- First interface: NAT
- Second interface: Bridge
I want to access the guest from my host and I want to access a second ethernet device from the guest. The device is connected with the host over a switch. I can ping the host, the external device and 8.8.8.8with my current setup from the guest, but I don´t have any internet access (chrome stucks at "resolving host").
When I deactivate the bridge the internet access does work, but not with the active bridge.
ifconfig gives me the following output
What is wrong?
ubuntu networking virtualbox
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
I have a virtual machine with a Ubuntu 16.04 guest and two network interfaces
- First interface: NAT
- Second interface: Bridge
I want to access the guest from my host and I want to access a second ethernet device from the guest. The device is connected with the host over a switch. I can ping the host, the external device and 8.8.8.8with my current setup from the guest, but I don´t have any internet access (chrome stucks at "resolving host").
When I deactivate the bridge the internet access does work, but not with the active bridge.
ifconfig gives me the following output
What is wrong?
ubuntu networking virtualbox
ubuntu networking virtualbox
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
edited Dec 24 '18 at 23:10
ctrl-alt-delor
10.9k41957
10.9k41957
asked Dec 24 '18 at 22:34
Kampi
1
asked Dec 24 '18 at 22:34
Kampi
1
asked Dec 24 '18 at 22:34
Kampi
1
1
1
Probably the second (bridge) interface is creating an entry in/etc/resolv.confwith a bad DNS server, or pointing to a DNS server that can not reach the internet.
– Stephen Harris
Dec 24 '18 at 22:42
It was the right tip. Thank you. It works after changing the nameserver to8.8.8.8by hand. How can I set this automatically?
– Kampi
Dec 24 '18 at 22:48
1
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add8.8.8.8, 8.8.8.4in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)
– Kampi
Dec 25 '18 at 8:20
add a comment |
1
Probably the second (bridge) interface is creating an entry in/etc/resolv.confwith a bad DNS server, or pointing to a DNS server that can not reach the internet.
– Stephen Harris
Dec 24 '18 at 22:42
It was the right tip. Thank you. It works after changing the nameserver to8.8.8.8by hand. How can I set this automatically?
– Kampi
Dec 24 '18 at 22:48
1
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add8.8.8.8, 8.8.8.4in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)
– Kampi
Dec 25 '18 at 8:20
1
1
Probably the second (bridge) interface is creating an entry in
/etc/resolv.conf with a bad DNS server, or pointing to a DNS server that can not reach the internet.– Stephen Harris
Dec 24 '18 at 22:42
Probably the second (bridge) interface is creating an entry in
/etc/resolv.conf with a bad DNS server, or pointing to a DNS server that can not reach the internet.– Stephen Harris
Dec 24 '18 at 22:42
It was the right tip. Thank you. It works after changing the nameserver to
8.8.8.8 by hand. How can I set this automatically?– Kampi
Dec 24 '18 at 22:48
It was the right tip. Thank you. It works after changing the nameserver to
8.8.8.8 by hand. How can I set this automatically?– Kampi
Dec 24 '18 at 22:48
1
1
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add
8.8.8.8, 8.8.8.4 in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)– Kampi
Dec 25 '18 at 8:20
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add
8.8.8.8, 8.8.8.4 in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)– Kampi
Dec 25 '18 at 8:20
add a comment |
1 Answer
1
active
oldest
votes
The solution is to add this in the network settings
I can access the internet, my host and the external device with these settings and the network configuration from above.
answered Dec 25 '18 at 8:24
Kampi
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f490814%2fvirtualbox-ubuntu-16-04-guest-no-internet-access-with-chome-with-nat%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The solution is to add this in the network settings
I can access the internet, my host and the external device with these settings and the network configuration from above.
answered Dec 25 '18 at 8:24
Kampi
1
add a comment |
The solution is to add this in the network settings
I can access the internet, my host and the external device with these settings and the network configuration from above.
answered Dec 25 '18 at 8:24
Kampi
1
add a comment |
The solution is to add this in the network settings
I can access the internet, my host and the external device with these settings and the network configuration from above.
answered Dec 25 '18 at 8:24
Kampi
1
The solution is to add this in the network settings
I can access the internet, my host and the external device with these settings and the network configuration from above.
answered Dec 25 '18 at 8:24
Kampi
1
answered Dec 25 '18 at 8:24
Kampi
1
answered Dec 25 '18 at 8:24
Kampi
1
answered Dec 25 '18 at 8:24
Kampi
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f490814%2fvirtualbox-ubuntu-16-04-guest-no-internet-access-with-chome-with-nat%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
1
Probably the second (bridge) interface is creating an entry in
/etc/resolv.confwith a bad DNS server, or pointing to a DNS server that can not reach the internet.– Stephen Harris
Dec 24 '18 at 22:42
It was the right tip. Thank you. It works after changing the nameserver to
8.8.8.8by hand. How can I set this automatically?– Kampi
Dec 24 '18 at 22:48
1
Okay, I solve the problem with the nameserver option in the network settings :)
– Kampi
Dec 24 '18 at 23:18
Maybe you can write up what you learned as an answer to the question, explaining why it went wrong and where you made changes to fix it.
– Stephen Harris
Dec 25 '18 at 3:10
Sorry, but I want test it first, because the first solution doesn´t work with apt. I have opened the network settings in ubuntu (Desktop -> Edit Connections -> Select the NAT interface -> Edit -> IPv4-Settings -> add
8.8.8.8, 8.8.8.4in the field "Additional DNS-Server" This works with chrome and apt. Modify the DNS-Server by hand over resolve.conf doens´t work for apt, but with chrome...don´t understand why, but this solution is a little bit better than the "hacky" way :)– Kampi
Dec 25 '18 at 8:20