VMware's network configuration (II.)

If you have read VMware's network configuration in detail (a) , now continue to understand;

First, use the CMD program under Windows System, ping one by using the ping command

The network host name or IP address that can be connected:

Then ping the same host name on the FEDORA15 system:

Should be related to the type of network settings, my network card is the way to set host-only;

So in order for the FEDORA15 to be able to ping the host address, let's set the next new

The network card, but does not use the host-only way, uses the NAT way;

① add NIC VMnet8:

② Configure the NIC for Fedora 15 Vmnet8

Now let's look at the network card information for Fedora (more eth3 NICs found):

[[email protected]/]# [[email protected]/]# ifconfig br0 Link encap:ethernet HWaddr 00:0c:29:99:0e:04  inet addr:192.168.1.101 bcast:192.168.1.255 mask:255.255.255.0 inet6 addr:fe80::20c:29ff:fe99:e04/64 Scope:link up broadcast RUNNING multicast mtu:1500 metric:1 RX packets:7047041 errors:0 dropped:0 ove          rruns:0 frame:0           TX packets:10172976 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0            RX bytes:1154188585 (1.0 Gib) TX bytes:10407590882 (9.6 Gib) BR1 Link encap:ethernet HWaddr 00:0c:29:99:0e:0e inet addr:192.168.0.101 bcast:192.168.0.255 mask:255.255.255.0 inet6 addr:fe80::58f6:69ff:fef0:b3db/64 S Cope:link up broadcast RUNNING multicast mtu:1500 metric:1 RX packets:2538 errors:0 dropped:0 Overruns          : 0 frame:0           TX packets:3063 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:251946 (246.0 KiB) TX bytes:301190 (294.1 KiB) eth0 Link encap:ethernet HWaddr 00:0c:29:99:0e:04 inet addr:192.16 8.1.101 bcast:192.168.1.255 mask:255.255.255.0 inet6 addr:fe80::20c:29ff:fe99:e04/64 scope:link up BR          Oadcast RUNNING multicast mtu:1500 metric:1 RX packets:3163 errors:0 dropped:0 overruns:0 frame:0 TX packets:3074 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:827602 (8 08.2 KiB) TX bytes:586661 (572.9 KiB) interrupt:19 Base address:0x2024 eth1 Link encap:ethernet HWaddr 00: 0c:29:99:0e:0e inet addr:192.168.0.101 bcast:192.168.0.255 mask:255.255.255.0 inet6 addr:fe80::20c: 29FF:FE99:E0E/64 scope:link up broadcast RUNNING multicast mtu:1500 metric:1 RX packets:388 errors:0 D          ropped:0 overruns:0 frame:0 TX packets:248 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:34813 (33.9 KiB) TX bytes:36708 (35.8 KiB) interrupt:17 Base address:0x2424 eth2 Link encap:ethernet HWaddr 00:0c:29:99:0e:18 inet addr:192.168.2.101 bcast:192.168.2.255 mask:255.255.255.0 inet6 addr:fe80:: 20C:29FF:FE99:E18/64 scope:link up broadcast RUNNING multicast mtu:1500 metric:1 RX packets:138 errors          : 0 dropped:0 overruns:0 frame:0 TX packets:124 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14219 (13. 8 KiB) TX bytes:18435 (18.0 KiB) interrupt:19 Base address:0x24a4 eth3 Link encap:ethernet HWaddr 00:0c:29 : 99:0e:22 inet addr:192.168.140.128 bcast:192.168.140.255 mask:255.255.255.0 inet6 addr:fe80::20c:2 9FF:FE99:E22/64 scope:link up broadcast RUNNING multicast mtu:1500 metric:1 RX packets:8 errors:0 Drop          ped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 txqueuelen:1000 RX bytes:1048 (1.0 KiB) TX bytes:4002 (3.9 KiB) interrupt:16 Base address:0x2824           Lo Link encap:local Loopback inet addr:127.0.0.1 mask:255.0.0.0 inet6 addr::: 1/128 scope:host          Up LOOPBACK RUNNING mtu:16436 metric:1 RX packets:1254 errors:0 dropped:0 overruns:0 frame:0           TX packets:1254 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0  RX bytes:114658 (111.9 KiB) TX bytes:114658 (111.9 KiB) [[email protected]/]#

Now try to ping the host address:

The Fedora system is set up under the VM on the network card first;

Only for the device driver (vmxnet):

[[Email protected]/]#[[email protected]/]# ethtool-i eth0driver:vmxnetversion:2.0.15.0firmware-version:n/abus-info : 0000:02:01.0[[email protected]/]#[[email protected]/]#

Report:

In fact there are other ways to increase the network card:

In FEDORA15 the/dev/net/path has tun device driver, we can also

Through the device driver to increase the network card;

。。。。。。

VMware's network configuration in detail (ii)