使用VMvare安装centos7，配置虚拟机上网（桥接）

本文主要是介绍使用VMvare安装centos7，配置虚拟机上网（桥接），希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

使用VMvare安装centos7，配置虚拟机上网（桥接）

#网卡配置：

[root@localhost ~]# vi /etc/sysconfig/network-scripts/ifcfg-ens33

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
#设置为none
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens33
UUID=ecee4f0b-4ced-4c4f-8cbe-bb660d15890f
DEVICE=ens33
#设置为开机自启
ONBOOT=yes
#设置静态IP
IPADDR=192.168.1.241
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
#取消NetworkManager管理
NM_CONTROLLED=no

"/etc/sysconfig/network-scripts/ifcfg-ens33" 24L, 443C written
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# systemctl restart network

#DNS配置：

[root@localhost ~]# vi /etc/NetworkManager/NetworkManager.conf

# Configuration file for NetworkManager.
#
# See "man 5 NetworkManager.conf" for details.
#
# The directories /usr/lib/NetworkManager/conf.d/ and /var/run/NetworkManager/conf.d/
# can contain additional configuration snippets installed by packages. These files are
# read before NetworkManager.conf and have thus lowest priority.
# The directory /etc/NetworkManager/conf.d/ can contain additional configuration
# snippets. Those snippets are merged last and overwrite the settings from this main
# file.
#
# The files within one conf.d/ directory are read in asciibetical order.
#
# If /etc/NetworkManager/conf.d/ contains a file with the same name as
# /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored.
# Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can
# put an empty file to /etc with the same name. The same applies with respect
# to the directory /var/run/NetworkManager/conf.d where files in /var/run shadow
# /usr/lib and are themselves shadowed by files under /etc.
#
# If two files define the same key, the one that is read afterwards will overwrite
# the previous one.

[main]
#plugins=ifcfg-rh,ibft
dns=none

[logging]
# When debugging NetworkManager, enabling debug logging is of great help.
#
# Logfiles contain no passwords and little sensitive information. But please
# check before posting the file online. You can also personally hand over the
# logfile to a NM developer to treat it confidential. Meet us on #nm on freenode.
# Please post full logfiles except minimal modifications of private data.
#
# You can also change the log-level at runtime via
# $ nmcli general logging level TRACE domains ALL
# However, usually it's cleaner to enable debug logging
# in the configuration and restart NetworkManager so that
# debug logging is enabled from the start.
#
# You will find the logfiles in syslog, for example via
# $ journalctl -u NetworkManager
#
# Note that debug logging of NetworkManager can be quite verbose. Some messages
# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
# in man journald.conf).
#
#level=TRACE
#domains=ALL
~
~
"/etc/NetworkManager/NetworkManager.conf" 51L, 2154C written
[root@localhost ~]# systemctl restart NetworkManager.service
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# vi /etc/resolv.conf

nameserver 114.114.114.114
nameserver 8.8.8.8

"/etc/resolv.conf" 2L, 46C written
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# curl -I http://www.baidu.com
HTTP/1.1 200 OK
Server: bfe/1.0.8.18
Date: Tue, 07 May 2019 14:14:23 GMT
Content-Type: text/html
Content-Length: 277
Last-Modified: Mon, 13 Jun 2016 02:50:23 GMT
Connection: Keep-Alive
ETag: "575e1f6f-115"
Cache-Control: private, no-cache, no-store, proxy-revalidate, no-transform
Pragma: no-cache
Accept-Ranges: bytes