Use GNS3 + VMware to build a large network topology

Many people like to complain about the lack of real-machine labs and the poor support of simulators. I don't think so. The potential of the simulator is infinite. Wait for you to explore it. The original topology of www.2cto.com described the requirements of this experiment: 1. vro: Configure IPSec VPN, and form a site-to-site VPN2 with the firewall. Firewall: Configure NAT, OSPF, IPSECVPN3 and layer-3 switching: There are many requirements for creating VLANs, DHCP, and OSPF. Here we only talk about the main requirements. For details, refer to the GNS3 topology in the attachment: the figure is messy. Because I have no experience in firewall, I have replaced it with a vro. Let's take a look at the implementation process. In the source image, the routers and firewalls on both sides of the Internet are in the same network, so a vswitch is added. The Internet uses a Router OS. Because my local computer is connected to a notebook wireless network, ROS has two NICs, one bridging wireless network, and the other connecting VMnet1 (host-only ), A simple disguise was made on ROS. In GNS3, the C1 bridge is connected to VMnet1. Because there are many running machines, I connected the other three server bridges to a local connection and connected the other computer. I also connected the VM bridge to a local connection, in this way, the three servers can be connected to the firewall, and the other three windows Server bridges can be connected to the local VMnet3, so that the three layers can be connected to exchange OK, the configuration of the exchange route is not mentioned here. Upload and test it later. Use the client to test the DHCP function: The VPCSVPN function is used here: only when the VLAN10 host accesses the network segment 172.16.16.0/24 on the router can the subnet of vlan 10 be connected to the network segment 172.16.16.1, vlan11 cannot be used. virtual channels have been set up. Testing NAT is basically implemented except for all the functions of the firewall. attachments and configuration files have been uploaded, I did not test it one by one. Check that VMware's virtual network is too messy.