Hi,
* stopped router + dead dynamips + save = error
Demo:
1 - Start GNS3
2 - Save a project
3 - Add 2 Routers (Minimum)
4 - Start R2 (R1 must be stopped)
5 - Kill Dynamips :)
6 - Save the project (CTRL+S)
7 - Error while extracting R1 config with normal method :D
The idea is to have a mix of stopped/running devices on the map + a crashed dynamips ...
Code:
01:10:33: DEBUG (1): sending to dynamips at 127.0.0.1:7200 -> vm extract_config R2
01:10:33: Dynamips process 127.0.0.1:7200 has crashed
01:10:33: Exporting R2 configuration to X:\...\configs\R2.recovered.cfg using recovery method
01:10:33: DEBUG (1): sending to dynamips at 127.0.0.1:7200 -> vm extract_config R1
01:10:33: Dynamips process 127.0.0.1:7200 has crashed
---------Traceback lines (saved in exception.log)----------
Traceback (most recent call last):
File "GNS3\Workspace.pyo", line 1368, in __action_Save
File "GNS3\NETFile.pyo", line 984, in export_net_file
File "GNS3\NETFile.pyo", line 947, in export_router_config
UnboundLocalError: local variable 'config' referenced before assignment
-----------------------------------------------------------
* Debug error while adding a new router (R26)
This is happening each time a new hypervisor is created (one error per hypervisor)
By sending this command "set_tsg"....
R4 - c3640
R5 - c1710
R16 - c7206
R20 - c3725
R14 - 2621
R18 - c7206
R25 - c1710
Code:
01:31:23: DEBUG (2): Router R26 created
01:31:23: DEBUG (1): sending to dynamips at 127.0.0.1:7202 -> vm set_tsg R4 0
01:31:23: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:23: DEBUG (1): sending to dynamips at 127.0.0.1:7203 -> vm set_tsg R5 0
01:31:23: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7200 -> vm set_tsg R16 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7201 -> vm set_tsg R20 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7206 -> vm set_tsg R14 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7207 -> vm set_tsg R18 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7205 -> vm set_tsg R8 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
01:31:24: DEBUG (1): sending to dynamips at 127.0.0.1:7208 -> vm set_tsg R25 0
01:31:24: DEBUG (1): returned -> ["202-Unknown command 'set_tsg'"]
* Port Tracker problem!
1 - Add some devices, last of them with console port 2047
2 - Start a daemon on port 2048 (NCAT.exe --nodns --telnet --exec "cmd" --listen 127.0.0.1 2048 --keep-open)
3 - Add a new device (Dynamips here) with console 2048 (same as the test daemon, ports are in order)
4 - Start the device with console port 2048
5 - Start putty on that Router and guess what: Says Microsoft! :)
6 - Stop NCAT daemon (Dynamips remains ON), and try again with putty. Now is ok -> "Connected to Dynamips VM "R27" (ID 48, type c2600) - Console port"
PS: No crashes in the process. All good! (Only on windows) ;)
Code:
netstat -nabt | grep -E "2048|\["
[dynamips.exe] TCP 0.0.0.0:2048 0.0.0.0:0 LISTENING
[ncat.exe] TCP 127.0.0.1:2048 0.0.0.0:0 LISTENING
[ncat.exe] TCP 127.0.0.1:2048 127.0.0.1:16018 ESTABLISHED
[putty.exe] TCP 127.0.0.1:16018 127.0.0.1:2048 ESTABLISHED
Attachment:
Windows_Sockets.jpg [ 16.91 KiB | Viewed 6050 times ]