It is currently Tue Mar 28, 2017 12:23 am


All times are UTC




Post new topic Reply to topic  [ 25 posts ]  Go to page Previous  1, 2, 3  Next
Author Message
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 8:54 pm 
Offline

Joined: Sun Sep 16, 2012 9:55 pm
Posts: 541
Location: England
With regards to people not finding python3-netifaces... it is only present in jessie(testing) or sid(unstable).

I shall need time to test, but I should be able to get any packages not in stable backported (at least to a private archive)



_________________
Daniel
Forum Moderator & Debian Package Maintainer for GNS3, Dynamips & VPCS.
Standalone DEB Packages are available from http://gns3.serverb.co.uk - To be updated!


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 8:59 pm 
Offline

Joined: Tue Apr 01, 2014 9:08 pm
Posts: 12
josephraa wrote:
shtivis wrote:
When I try to start the dynamips I get the following error:
server error [-3200]: Dynamips doesn't exist
server error [-3200]: uncaught exeption <class 'KeyError>: None

Any ideas?

Have you installed the required version of dynamips? If not, try the following:

Code:
sudo apt-get install libelf-dev
sudo apt-get install uuid-dev
sudo apt-get install libpcap-dev
wget https://github.com/GNS3/dynamips/archive/master.zip
unzip master.zip
cd dynamips-master/
sudo make
sudo mv dynamips.stable /usr/bin/dynamips


That worked for me to install the latest version of dynamips on Ubuntu 13.10



Hi,
Thanks for the replay.
I followed your instruction but still no result.
still get the server error [-3200]: Dynamips doesn't exist
when i issue the commad dynamips it's give me output.


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 9:05 pm 
Offline

Joined: Tue Apr 01, 2014 2:11 pm
Posts: 43
Location: Ohio, US
Maybe you need to set the path to dynamips under preferences? If you followed my instructions for installing, then it would be /usr/bin/dynamips

_________________
Joe Amen - Enterprise IT Consultant
CompTIA A+, Net+
CCNA in progress


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 9:08 pm 
Offline

Joined: Tue Apr 01, 2014 9:08 pm
Posts: 12
shtivis wrote:
josephraa wrote:
shtivis wrote:
When I try to start the dynamips I get the following error:
server error [-3200]: Dynamips doesn't exist
server error [-3200]: uncaught exeption <class 'KeyError>: None

Any ideas?

Have you installed the required version of dynamips? If not, try the following:

Code:
sudo apt-get install libelf-dev
sudo apt-get install uuid-dev
sudo apt-get install libpcap-dev
wget https://github.com/GNS3/dynamips/archive/master.zip
unzip master.zip
cd dynamips-master/
sudo make
sudo mv dynamips.stable /usr/bin/dynamips


That worked for me to install the latest version of dynamips on Ubuntu 13.10



Hi,
Thanks for the replay.
I followed your instruction but still no result.
still get the server error [-3200]: Dynamips doesn't exist
when i issue the commad dynamips it's give me output.


I retried again and get:
ERROR: gns3.modules.dynamips.nodes.router: error while starting R1 uncaught exception <class 'keyerror'>: None


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 9:16 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Quote:
I retried again and get:
ERROR: gns3.modules.dynamips.nodes.router: error while starting R1 uncaught exception <class 'keyerror'>: None


There is something more than just a Dynamips path problem here.

Can you manually start the GNS3 server in a console, then start the GUI? You should see a detailed error message in that console. Please post it here.

Thanks,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 9:42 pm 
Offline

Joined: Tue Apr 01, 2014 9:08 pm
Posts: 12
grossmj wrote:
Quote:
I retried again and get:
ERROR: gns3.modules.dynamips.nodes.router: error while starting R1 uncaught exception <class 'keyerror'>: None


There is something more than just a Dynamips path problem here.

Can you manually start the GNS3 server in a console, then start the GUI? You should see a detailed error message in that console. Please post it here.

Thanks,


Hi, Here is the full log:
[email protected]:/home/omer# gns3
GNS3 GUI version 1.0-alpha1
Copyright (c) 2007-2014 GNS3 Technologies Inc.

(process:4468): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(python3:4468): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
INFO:gns3.modules.dynamips:Dynamips module reset
INFO:gns3.modules.iou:IOU module reset
INFO:gns3.topology:topology has been reset
INFO:gns3.main_window:creating temporary topology file: /tmp/gns3-9cf3mr.net
INFO:gns3.main_window:creating temporary project files directory: /tmp/gns3-9cf3mr-files
INFO:gns3.modules.dynamips:local working directory for Dynamips module: /tmp/gns3-9cf3mr-files
INFO:gns3.servers:new local server connection ws://127.0.0.1:8000 registered
INFO:gns3.modules.iou:local working directory for IOU module: /tmp/gns3-9cf3mr-files

(python3:4468): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
INFO:gns3.main_window:starting local server /usr/local/bin/gns3server on 127.0.0.1:8000
INFO:gns3.servers:starting local server process with /usr/bin/python3 /usr/local/bin/gns3server --host=127.0.0.1 --port=8000
GNS3 server version 1.0-alpha1
Copyright (c) 2007-2014 GNS3 Technologies Inc.
[W 140403 00:18:45 config:82] no configuration file could be found or read
[W 140403 00:18:45 __init__:69] iouyap binary couldn't be found!
[I 140403 00:18:45 base:121] dynamips module running with PID 4477
[I 140403 00:18:45 base:74] ZeroMQ client (dynamips) connecting to 127.0.0.1:50117
[I 140403 00:18:45 server:194] ZeroMQ server listening to 127.0.0.1:50117
[I 140403 00:18:45 base:121] iou module running with PID 4478
Starting server on 127.0.0.1:8000
[I 140403 00:18:45 base:74] ZeroMQ client (iou) connecting to 127.0.0.1:50117
INFO:gns3.websocket_client:connected to 127.0.0.1:8000
[I 140403 00:18:45 jsonrpc_websocket:112] Websocket client e7251335-02db-46a9-bad8-615572b64967 connected
INFO:gns3.modules.dynamips:creating node <class 'gns3.modules.dynamips.nodes.c7200.C7200'>
INFO:gns3.modules.dynamips:adding server 127.0.0.1:8000 to Dynamips module
INFO:gns3.modules.dynamips:sending Dynamips settings to server 127.0.0.1:8000
INFO:gns3.modules.dynamips.nodes.router:router c7200 is being created
[I 140403 00:18:48 __init__:252] this server is local
INFO:gns3.modules.dynamips:configuring node Router c7200
[I 140403 00:18:48 __init__:218] starting the hypervisor manager with Dynamips working directory set to '/tmp/gns3-9cf3mr-files'
[I 140403 00:18:48 hypervisor_manager:199] base aux port set to 2501
[I 140403 00:18:48 hypervisor_manager:222] base UDP port set to 10001
[I 140403 00:18:48 hypervisor_manager:155] base hypervisor port set to 7201
[I 140403 00:18:48 hypervisor_manager:177] base console port set to 2101
[I 140403 00:18:48 hypervisor_manager:467] creating new hypervisor 127.0.0.1:7201
[I 140403 00:18:48 hypervisor:204] starting Dynamips: ['dynamips', '-N1', '-H', '127.0.0.1:7201']
[I 140403 00:18:48 hypervisor:206] logging to /tmp/gns3-9cf3mr-files/dynamips-7201.log
[I 140403 00:18:48 hypervisor:212] Dynamips started PID=4485
[I 140403 00:18:49 hypervisor_manager:426] Dynamips server ready after 0.8463 seconds
[I 140403 00:18:49 hypervisor_manager:471] hypervisor 127.0.0.1:7201 has successfully started
[I 140403 00:18:49 dynamips_hypervisor:275] hypervisor a new base UDP 10001
[I 140403 00:18:49 router:104] router c7200 "R1" [id=1] has been created
[I 140403 00:18:49 router:1003] router "R1" [id=1]: console port updated from None to 2101
[I 140403 00:18:49 router:1033] router "R1" [id=1]: aux port updated from None to 2501
[I 140403 00:18:49 router:1181] router "R1" [id=1]: adapter C7200-IO-2FE inserted into slot 0
[I 140403 00:18:49 router:391] router "R1" [id=1]: has a new IOS image set: "/home/omer/Desktop/c7200-ipbasek9-mz.150-1.M10.bin"
[I 140403 00:18:49 router:626] router "R1" [id=1]: sparse memory enabled
[I 140403 00:18:49 router:593] router "R1" [id=1]: mmap enabled
[I 140403 00:18:49 router:116] creating a new ghost IOS file
[I 140403 00:18:49 router:391] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2]: has a new IOS image set: "/home/omer/Desktop/c7200-ipbasek9-mz.150-1.M10.bin"
[I 140403 00:18:49 router:861] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2]: ghost status set to 1
[I 140403 00:18:49 router:816] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2]: ghost file set to c7200-ipbasek9-mz.150-1.M10.bin-256.ghost
[I 140403 00:18:49 router:529] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2]: RAM updated from 128MB to 256MB
[I 140403 00:18:49 router:276] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2] has been started
[I 140403 00:18:50 router:285] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2] has been stopped
[I 140403 00:18:50 router:263] router "ghost-c7200-ipbasek9-mz.150-1.M10.bin-256.ghost" [id=2] has been deleted
[I 140403 00:18:50 router:861] router "R1" [id=1]: ghost status set to 2
[I 140403 00:18:50 router:816] router "R1" [id=1]: ghost file set to c7200-ipbasek9-mz.150-1.M10.bin-256.ghost
[E 140403 00:18:50 base:232] uncaught exception <class 'KeyError'>
Traceback (most recent call last):
File "/usr/local/lib/python3.3/dist-packages/gns3_server-1.0_alpha1-py3.3.egg/gns3server/modules/base.py", line 230, in _decode_request
self.modules[self.name][destination](self, params)
File "/usr/local/lib/python3.3/dist-packages/gns3_server-1.0_alpha1-py3.3.egg/gns3server/modules/dynamips/backends/vm.py", line 243, in vm_start
router = self._routers[router_id]
KeyError: None
[I 140403 00:18:50 base:185] ZeroMQ client (dynamips) sending JSON-RPC custom error: uncaught exception <class 'KeyError'>: None for call id c10a3efe-548a-4537-a170-140a84f6fcd1
INFO:gns3.modules.dynamips.nodes.router:router setting up and updating mac_addr from 'None' to 'ca01.1185.0000'
INFO:gns3.modules.dynamips.nodes.router:router setting up and updating console from 'None' to '2101'
INFO:gns3.modules.dynamips.nodes.router:router setting up and updating name from '' to 'R1'
INFO:gns3.modules.dynamips.nodes.router:router setting up and updating aux from 'None' to '2501'
INFO:gns3.modules.dynamips.nodes.router:router setting up and updating image from '' to '/home/omer/Desktop/c7200-ipbasek9-mz.150-1.M10.bin'
ERROR:gns3.modules.dynamips.nodes.router:error while starting R1: uncaught exception <class 'KeyError'>: None


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Wed Apr 02, 2014 11:39 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Hi,

Ok time to get the heavy artillery. Can you redo exactly what you did but this time start the server like this:

Code:
gns3server --logging=debug


Thanks,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Thu Apr 03, 2014 7:04 am 
Offline

Joined: Tue Apr 01, 2014 9:08 pm
Posts: 12
grossmj wrote:
Hi,

Ok time to get the heavy artillery. Can you redo exactly what you did but this time start the server like this:

Code:
gns3server --logging=debug


Thanks,


No problem:
[email protected]:~$ gns3server --logging=debug
GNS3 server version 1.0-alpha1
Copyright (c) 2007-2014 GNS3 Technologies Inc.
[W 140403 00:38:35 config:82] no configuration file could be found or read
[D 140403 00:38:35 jsonrpc_websocket:104] registering builtin.stop as a destination for the <bound method Server._cleanup of <gns3server.server.Server object at 0xb67bc12c>> module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.allocate_udp_port as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.allocate_udp_port as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.allocate_udp_port as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.create as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.delete_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.reload as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.stop as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.create as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.update as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.delete_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.save_config as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.update as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.add_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.delete_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.update as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.settings as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.create as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.delete as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.add_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.delete as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.suspend as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethsw.delete as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.delete as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.delete as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.create as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.create as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.delete_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.add_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.delete_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.start as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.add_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.nio.get_interfaces as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.reset as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.idlepcs as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.ethhub.allocate_udp_port as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.add_nio as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.vm.update as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.frsw.update as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.echo as a destination for the dynamips module
[D 140403 00:38:35 jsonrpc_websocket:104] registering dynamips.atmsw.allocate_udp_port as a destination for the dynamips module
[W 140403 00:38:35 __init__:69] iouyap binary couldn't be found!
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.stop as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.delete_nio as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.create as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.delete as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.echo as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.settings as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.update as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.reset as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.allocate_udp_port as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.start as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.reload as a destination for the iou module
[D 140403 00:38:35 jsonrpc_websocket:104] registering iou.add_nio as a destination for the iou module
[I 140403 00:38:35 base:121] dynamips module running with PID 5815
[I 140403 00:38:35 base:74] ZeroMQ client (dynamips) connecting to 127.0.0.1:59901
[I 140403 00:38:36 base:121] iou module running with PID 5816
[I 140403 00:38:36 server:194] ZeroMQ server listening to 127.0.0.1:59901
Starting server on 0.0.0.0:8000
[I 140403 00:38:36 base:74] ZeroMQ client (iou) connecting to 127.0.0.1:59901
[C 140403 00:38:36 server:142] socket in use for port 8000

–--------------------------------------------------------------------------------------------------


[email protected]:~$ gns3
GNS3 GUI version 1.0-alpha1
Copyright (c) 2007-2014 GNS3 Technologies Inc.
INFO:gns3.modules.dynamips:Dynamips module reset
INFO:gns3.modules.iou:IOU module reset
INFO:gns3.topology:topology has been reset
INFO:gns3.main_window:creating temporary topology file: /tmp/gns3-myy2xo.net
INFO:gns3.main_window:creating temporary project files directory: /tmp/gns3-myy2xo-files
INFO:gns3.modules.dynamips:local working directory for Dynamips module: /tmp/gns3-myy2xo-files
INFO:gns3.servers:new local server connection ws://127.0.0.1:8000 registered
INFO:gns3.modules.iou:local working directory for IOU module: /tmp/gns3-myy2xo-files
INFO:gns3.websocket_client:connected to 127.0.0.1:8000
INFO:gns3.main_window:use an already started local server on 127.0.0.1:8000
INFO:gns3.modules.dynamips:creating node <class 'gns3.modules.dynamips.nodes.c7200.C7200'>
INFO:gns3.modules.dynamips:adding server 127.0.0.1:8000 to Dynamips module
INFO:gns3.modules.dynamips:sending Dynamips settings to server 127.0.0.1:8000
INFO:gns3.modules.dynamips.nodes.router:router c7200 is being created
INFO:gns3.modules.dynamips:configuring node Router c7200
ERROR:gns3.modules.dynamips.nodes.router:error while setting up : Dynamips executable dynamips doesn't exist


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Fri Apr 04, 2014 11:35 pm 
Offline

Joined: Wed Apr 02, 2014 7:48 pm
Posts: 10
^
Hey guys, I got the similiar issue above. When I try to console into a switch I get

[I 140404 19:31:40 iou_device:428] logging to /tmp/gns3-vc6zyi-files/device-2/iou.log
[I 140404 19:31:40 iou_device:435] IOU instance 2 started PID=3207
[I 140404 19:31:40 iou_device:380] starting ioucon for IOU instance IOU2 to accept Telnet connections on 0.0.0.0:4002
[I 140404 19:31:40 iou_device:350] IOU IOU2 [id=2]: iouyap.ini updated
[I 140404 19:31:40 iou_device:394] starting iouyap: ['/usr/local/bin/iouyap', '514']
[I 140404 19:31:40 iou_device:396] logging to /tmp/gns3-vc6zyi-files/device-2/iouyap.log
[I 140404 19:31:40 ioucon:352] Telnet server ready for connections on 0.0.0.0:4002
[I 140404 19:31:40 iou_device:403] iouyap started PID=3209
INFO:gns3.modules.iou.iou_device:IOU2 has started
INFO:gns3.telnet_console:starting telnet console "xterm -T IOU2 -e 'telnet 127.0.0.1 4002' >/dev/null 2>&1 &"
Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

The console window also shows

xterm: Can't execvp telnet 127.0.0.1: 4001: No such file or directory


Top
 Profile  
 
 Post subject: Re: Howto first alpha release on Linux Debian
PostPosted: Sat Apr 05, 2014 12:24 am 
Offline

Joined: Wed Apr 02, 2014 7:48 pm
Posts: 10
willtech10577 wrote:
^
Hey guys, I got the similiar issue above. When I try to console into a switch I get

[I 140404 19:31:40 iou_device:428] logging to /tmp/gns3-vc6zyi-files/device-2/iou.log
[I 140404 19:31:40 iou_device:435] IOU instance 2 started PID=3207
[I 140404 19:31:40 iou_device:380] starting ioucon for IOU instance IOU2 to accept Telnet connections on 0.0.0.0:4002
[I 140404 19:31:40 iou_device:350] IOU IOU2 [id=2]: iouyap.ini updated
[I 140404 19:31:40 iou_device:394] starting iouyap: ['/usr/local/bin/iouyap', '514']
[I 140404 19:31:40 iou_device:396] logging to /tmp/gns3-vc6zyi-files/device-2/iouyap.log
[I 140404 19:31:40 ioucon:352] Telnet server ready for connections on 0.0.0.0:4002
[I 140404 19:31:40 iou_device:403] iouyap started PID=3209
INFO:gns3.modules.iou.iou_device:IOU2 has started
INFO:gns3.telnet_console:starting telnet console "xterm -T IOU2 -e 'telnet 127.0.0.1 4002' >/dev/null 2>&1 &"
Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

The console window also shows

xterm: Can't execvp telnet 127.0.0.1: 4001: No such file or directory



GOT IT WORKING. Had to install putty and then specify Putty as the console. For my how-to on installing, please visit my blogpost http://www.nycnetworkers.com/study-tips ... y-release/

Thanks for everyone on the forum for helping out!




Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 25 posts ]  Go to page Previous  1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO