手动配置网关解决VMWare虚拟机可以访问主机但无法上网问题：选择NAT并配置IP和NetMask后，可以ping通主机，但无法上网。解决方案：手动配置默认网关。步骤：在虚拟网络编辑器中，找到网关配置，这里是192.168.171.2。在虚拟机设置中，确保选择NAT。IP和网络掩码已经配置：[root@localhost~]#ifconfigens33ens33:flags=4163mtu1500inet192.168.171.128netmask255.255.255.0broadcast192.168.171.255:inet20c8029:inet20c8029feba:ba7cprefixlen64scopeid0x20ether00:0c:29:ba:ba:7ctxqueuelen1000（以太网）RX数据包281023字节361357640（344.6MiB）RX错误0丢弃0超限0帧0TX数据包68897字节14016800(13.3MiB)TXerrors0dropped0overruns0carrier0collisions0可以Ping通主机，但无法连接Internet：[root@localhost~]#ping192.168.171.1PING192.168.171.1(192.168.171.1)56(84)bytes来自192.168.171.1的data.64字节：icmp_seq=1ttl=128time=0.416ms来自192.168.171.1的64字节：icmp_seq=2ttl=128time=0.318ms来自192.168.171.1的64字节：icmp_seq=3ttl=128time来自192.168.171.1的0.348ms64字节：icmp_seq=4ttl=128time=0.262ms^C---192.168.171.1ping统计数据---4包ts传输，4接收，0%丢包，时间3001msrttmin/avg/max/mdev=0.262/0.336/0.416/0.055ms[root@localhost~]#ping8.8.8.8connect:NetworkisunreachableCheckroutingtable:[root@localhost~]#netstat-nrKernelIProutingtableDestinationGatewayGenmaskFlagsMSSWindowirttIface192.168.122.00.0.0.0255.255.255.0U000virbr0192.168.171.00.0.0.0255.250Uens手动添加网关：[root@localhost~]#routeadddefaultgw1??92.168.171.2[root@localhost~]#netstat-nrKernelIP路由表目标网关Genmask标志MSS窗口irttIface0.0.0.0192.168.171.20.0.0.0UG000ens33192.168.122。00.0.0.0255.255.255.0U000virbr0192.168.171.00.0.0.0255.255.255.0U000ens33再试一次：[root@localhost~]#ping8.8.8.8PING.8.8.8(8.8.8.8)56(84)字节esofdata.64bytesfrom8.8.8.8:icmp_seq=1ttl=128time=23.4ms64bytesfrom8.8.8.8:icmp_seq=2ttl=128time=26.5ms64bytesfrom8.8.8.8:icmp_seq=3ttl=128time=22.5ms64bytesfrom8.8.8.8:icmp_seq=4ttl=128time=29.2ms^C---8.8.8.8pingstatistics---4个数据包传输，4个接收，0%数据包丢失，时间3007msrttmin/avg/max/mdev=22.524/25.448/29.255/2.666ms删除新添加的网关，重现之前的错误：[root@localhost~]#routedeldefaultgw1??92.168.171.2[root@localhost~]#netstat-nrKernelIProutingtableDestinationGatewayGenmaskFlagsMSSWindowirttIface192.168.122.00.0.0.0255.255.255.0U000virbr0192.168.171.00.0.0.0255.255.255.0U000n8conect8.8~:网络无法访问参考链接：https：//www.freebsd.org/doc/h...https://unix.stackexchange.co...
