bridge Dynamips with local NIC
Thursday, September 27th, 2007 | Dynamips-Links
bridge Dynamips with local NIC
bridge Dynamips with local NIC
First, to bridge Dynamips with local NIC is to capture parameter of NIC. Then how to capture parameter? Here are three methods:
?use Dynamips –e command line parameters
Click “start-run-cmd”, enter into your dynamips directory with cd command. Then input dynamips –e to capture.
?Use Dynamips+Dynagen win32 installation package. Double-click the shortcut Network device list on the desktop to capture after installation.
?Use DynamipsGUI to capture
2007-9-26 02:15
Then you can see the result as follwing?
?to make it easy for explanation, I add on my host VM virtual NIC, Tap NIC and Microsoft Loopback NIC?
2007-9-26 02:15
NIC parameter is the underlined part in the above picture.
E.g. local network card parameter is:
\Device\NPF_{C4806338-FDAE-4AD4-9E8C-2654B73223CF}, with complete format
NIC parameter is captured. The next is how to bridge? Here I will state net file and bat file separately.
?Bridge net file
Use Dynagen as front end. E.g. simulate a 7200 router. Insert slot0 into C7200-IO-FE module, and bridge Fa0/0 interface to local network card. You only need the following parameter:
Fa0/0=\Device\NPF_{C4806338-FDAE-4AD4-9E8C-2654B73223CF}
note that only Ethernet interface can bridge local NIC.
?Bridge bat file (batch file)
Use original command directly to complete simulation, but it is somewhat complex. Here we suggest you use DynamipsGUI to deal with batch file. with net file example, the steps are:
Choose device types, bridge to PC and configure main parameters of 7200. Like the following:
2007-9-26 02:15
Click “confirm bridge parameter” after configuration (note that after confirmation NIC parameter would disappear, which is normal), then click “NEXT”. Slot setting is as following:
2007-9-26 02:15
Click “NEXT”, enter into interface connection:
2007-9-26 02:15
Click “create BAT file”. “. Bat” file parameters explanation is as follows:
e.g.
dynamips-wxp.exe -T 2001 -P 7200 -r 128 –disk0 4 -t npe-400 -c 0×2102 -p 0:C7200-IO-FE -s 0:0:gen_eth:”\Device\NPF_{C4806338-FDAE-4AD4-9E8C-2654B73223CF}” ..\c7200-is-mz.122-37.bin –idle-pc=0×6067d29c
Simple explanation on the parameters of the bridge
Copy the contents to the clipboard
code
-p 0:C7200-IO-FE insert C7200-IO-FE into slot0
-s
0:0:gen_eth:”\Device\NPF_{C4806338-FDAE-4AD4-9E8C-2654B73223CF}” Bridge Fa0/0 interface to local network card.
———————————————————————————–
FAQ in bridging:
1.Question: how to configure local NIC correctly so that they can communicate with router?
Answer: configure IP of local NIC and IP of router NIC in the same network segment. (Of course you can choose router interface as default gateway).
2.Question: I configured IP and NIC parameter correctly, but they cannot ping each other. Why?
Answer: Check your firewall, maybe it banned communications, configure firewall Release. (We suggest that you close your firewall)
3. Question: When running bat file, dead cycle appeared. Do you know why?
Answer: check your NIC parameter format and make sure that you have chosen the right NIC parameter.
4.Question: when using VM virtual NIC to bridge, if we want to use virtual machine to communicate with dynamips simulation device, how to bridge?
Answer: it is similar to normal bridging. You only need to capture VM virtual NIC parameter and configure according to the above method. Pay attention to the IP address configuration. The simplest way is to use VM bridging mode, as the following diagram
VM virtual machine————-local network card————-Dynamips simulation router
5.Question: In multi-virtual NIC- bridging, I was unable to recognize the needed Virtual NIC parameters when using dynamips to capture NIC parameters.
Answer: when we use opencpn to create a number of TAP NIC (virtual NIC created by VM), we cannot identify which NIC parameter is the one you need. There are no differences except different parameters. The reason is the same.
There are two methods to identify virtual NIC parameter VM created:
1? First, we set a number of NIC name in “network connections”. When we need more than bridge, we can choose to stop some VM virtual NIC, leaving only one, and then use e-dynamips to capture parameters. Now there is only one VM virtual NIC. Select it and make records and markings. Then close this VM virtual NIC and start others (one for each time). Then you can ascertain all the VM virtual NIC parameters.
2? confirm open registry through the registry, locate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}
You can see a series of sub-keys under it: 0000?0001?0002 etc., open them one by one until you find the sub-key VMnet1 card locates. The parameter of VMnet1 is available in NetCfgInstanceId string. Record it in a notebook. Thus you can recognize each NIC parameter of VMnet
As to identify TAP virtual NIC parameter created by Openvpn, you can try the first method.
PassGuide Cisco Training Materials Dumps
No comments yet.
Leave a comment
PassGuide practice Test
