LinuxQuestions.org - [SOLVED] could not connect with internet

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - could not connect with internet (https://www.linuxquestions.org/questions/linux-newbie-8/could-not-connect-with-internet-4175558440/)

could not connect with internet

My box is centos 7.1 x64 as guest on windows 10 x64 as host.

I could not connect with internet at cenots.

1.

Quote:

[root@localhost ~]# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::a00:27ff:fe82:c1d8 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:82:c1:d8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 94 bytes 5814 (5.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 353 bytes 35527 (34.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 353 bytes 35527 (34.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

2.
systemctl stop firewalld
systemctl stop iptables
systemctl stop iptables6

3. Selinux
[root@localhost ~]# sestatus
SELinux status: disabled

Any helpful coments would be appreciated.
Thanks in advance.

What virtualization program are you running and what are your settings for the network connection between the host and the guest?

It's virtualbox and bridge adapter is for network connection.

I have some troubleshooting ideas.

Test with a NAT adapter to ensure that the VM can connect to the net.

In the Bridged Adapter dialog under the Advanced item, there are normally several different "Adapter Types" from which to choose. Try each one; odds are that one of them will connect. I have experienced situations in which the Adapter Type to which VB defaulted was not the proper choice.

Let us know what happens.

frankbell/

After update virtualbox 5.0.8 to 5.0.10 today, it's solved.