[2.0.0dev2] Remote Server wrong Console IP.

[gcasella]

Hey Again,

Don't know how else I should've titled this but what I noticed was when running the TightVNC packaged with GNS3 I start a QEMU node located on a remote server when I try to console in I get the following error;

QEMU VNC
Telnet vRIN

[gcasella]

Dug a bit deeper, it looks like the code in compute_manager.py only has the option for two types of computes, VM or LOCAL.

When it uses local it seems to carry over to the GNS3-GUI with the 127.0.0.1 address instead of the actual IP address of the main remote server address.

[gcasella]

Correction...
I fixed this myself.

This is how i did it;

1. Modify the gns3_server.conf file on your remote server and make sure the host= variable is set properly. (added host = dns_hostname/ip)

2. Restart your remote gns3 service.

[julien-duponchelle]

Thanks for the informations it will help to fix the issue.

[julien-duponchelle]

Ok I got the issue. By default the server start on 0.0.0.0 and the code will replace it by 0.0.0.0 as console host.

[julien-duponchelle]

Fixed will be include in alpha2

[gcasella]

Cool!

Sounds good @noplay , I just saw the update to the code. I'll test it out after the nightly build!

Glad i could help out

[gcasella]

Fyi @noplay latest nightly build of dev3 (i'd assume is Alpha 2) did not have the fix.

When the server starts it will start as 0.0.0.0:3080 but the controller will listen to 127.0.0.1

[julien-duponchelle]

This it should be good