Shulou(Shulou.com)06/01 Report--

List of articles (follow Wechat official account EmulatedLab, get articles in time and download links)

1. EVE-NG introduction (the best simulator for EVE-NG, the era of simulation environment is coming! )

2. Introduction of EVE-NG installation process

3. EVE-NG imports Dynamips and IOL

4. EVE-NG imports QEMU image

5. EVE-NG Associate SecureCRT,VNC,Wireshark

6. EVE-NG network card is bridged to take you into more advanced experiments.

7. EVE-NG hard disk is expanded to store a large number of images.

8. EVE-NG customizes personal images, and scripts are imported quickly.

9. EVE-NG accommodates H3C, Huawei, and swallows GNS3

10. Here comes the EVE-NG image! Create the largest EVE communication circle in China

11. EVE-NG image attacks again, omnipotent!

12. Increase the holdings of EVE-NG image and step onto the altar!

13. EVE-NG does not have enough memory? Teach you to expand virtual memory!

14. EVE-NG updates are convenient and effortless!

15. EVE-NG minority image, help to taste fresh!

16. EVE-NG experience Seafile, discard 10K/s network disk

17 、.

Click to view matching video tutorials!

EVE-NG network card bridging, taking you into a more advanced experiment

First, add a virtual physical network card to EVE-NG (no matter what kind of network card, the method is similar)

Why is it a virtual physical network card? The VMnet1 network card itself is virtual, but for EVE-NG in VMware, it is a physical network card.

If the network card itself is a real physical network card, then EVE-NG can communicate directly with the real physical network card.

The two ways are the same. The former: EVE-NG can communicate with other virtual machines of VMware; the latter: EVE-NG can communicate with real physical network cards.

The VMnet1 IP of this machine is 10.0.1.99. The final effect is that the router in the EVE-NG can ping the IP, which proves that the bridge is successful.

VMware supports booting to add hardware, and EVE-NG can immediately recognize the network card.

If your EVE-NG cannot be recognized after adding the network card, you can restart the network service of EVE.

Root@eve-ng:~# / etc/init.d/networking restart

[ok] Restarting networking (via systemctl): networking.service.

Root@eve-ng:~#

If you can't recognize it, turn off the EVE-NG, add the network card, and then turn it on.

As you can see from the screenshot above, the Nic of the added VMnet1 has been identified as eth2, and the MAC address is the same.

2. Edit the configuration file of EVE network card

Open the configuration file with vim (I'm used to using vim,nano)

Root@eve-ng:~# vim / etc/network/interfaces

In fact, the default configuration has already been bridged. The reason for adding this part is that I want to explain to you the principle of bridging and the parameters that can be used.

Root@eve-ng:~# vim / etc/network/interfaces

# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces (5).

# The loopback network interface

Auto lo

Iface lo inet loopback

# The primary network interface

Iface eth0 inet manual # (EVE-NG 's management network card)

Auto pnet0

# iface pnet0 inet dhcp # (manage the bridge network card of the network card, and all devices connected to the pnet0 can communicate with eth0)

# bridge_ports eth0 # (bridging to eth0)

# bridge_stp off # (turn off stp spanning Tree Protocol, which is also important in production environments, especially in KVM,OpenStack,Docker. )

Iface pnet0 inet static # (method of modifying fixed IP)

Bridge_ports eth0

Bridge_stp off

Bridge_ageing 0

Address 10.0.0.100

Netmask 255.255.255.0

Gateway 10.0.0.1

Dns-domain UnetLab.sms.com

Dns-nameservers 114.114.114.114

# Cloud devices

Iface eth2 inet manual # (newly added VMnet1 Nic)

Auto pnet1

Iface pnet1 inet manual # (bridged network card of VMnet1, devices connected to pnet1 can communicate with VMnet1)

Bridge_ports eth2

Bridge_stp off

# of course, pnet1 can also be configured as static or dynamic IP. Tr in the experiment can eliminate bridging problems. Whether pnet1 has IP or not will not affect the bridging feature.

Iface eth3 inet manual

Auto pnet2

Iface pnet2 inet manual

Bridge_ports eth3

Bridge_stp off

……

……

……

Iface eth9 inet manual

Auto pnet9

Iface pnet9 inet manual

Bridge_ports eth9

Bridge_stp off

Currently, my EVE-NG network card is configured.

Iface eth0 inet manual

Auto pnet0

Iface pnet0 inet static

Bridge_ports eth0

Bridge_stp off

Address 10.0.0.100

Netmask 255.255.255.0

Gateway 10.0.0.1

Iface eth2 inet manual

Auto pnet1

Iface pnet1 inet static

Bridge_ports eth2

Bridge_stp off

Address 10.0.1.98

Netmask 255.255.255.0

Gateway 10.0.1.99

III. Testing

1. Create a new experimental instance on the Web interface, add Network Cloud, and add routers.

There are two types of Network

The first kind: Bridge, which is equivalent to a stupid switch.

Bridge icon

Note:

In the age of Unetlab, stupid switches were automatically generated when the network cable was connected, and somehow EVE removed this kind of intelligent Feature. The guess is to avoid one of the most disgusting Bug of Unetlab: once the connection is successful, after the boot experiment, the topology is found to be wrong and the topology is adjusted. In this case, the edited topology and device direct connection may not work, and EVE-NG must be restarted to return to normal.

Of course, this Bug no longer exists in EVE, but it also adds some disadvantages, and the topology can not be modified until the device is turned off.

The second kind: Cloud, the cloud for network card bridging.

Cloud icon

2. Connect the line

As shown in the figure above, we can see that Cloud does not have any interfaces. In other words, any experimental equipment can connect to this cloud and can communicate with each other as long as the IP of the same network is configured.

3. Start up and test the equipment

Configure IP address, ping test (10.0.1.99 is the address of Windows host VMnet1 Nic)

Ping test (10.0.1.98 is the pnet1 Nic address of EVE-NG)

Additional content:

Since this article is about assigning virtual network cards to EVE-NG virtual machines, in fact, the same is true for assigning physical network cards, so here is a brief introduction

I have a TP-Link wireless network card with USB interface. The network name is TP-Link wireless network.

Then VMware will recognize the network card (the network card is disabled)

First add a new network VMnet2 (any one will do)

Change VMnet2 to bridge mode and bridge to TP-Link Wireless USB Adapter, that is, the physical network card you want to bridge, click OK

Then change the newly added network card of EVE-NG to VMnet2

Then according to the method in the previous text, you can do it step by step!

End!

QQ group QR code, look forward to your joining!

Follow the official Wechat account EmulatedLab and get updated articles and download links in time!

This article was published on the official account EmulatedLab of Wechat on April 13, 2017.

Maosen | Mori

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.