Jeremy Grossmann

> Sad enough, it's not fixed. Must be because I haven't properly tested using a GNS3 VM. I will have a closer look then.

> I assume that happens, because for remote GNS3VMs two notification streams are created, one for the remote server and one for the GNS3VM. Correct, I could reproduce the problem....

> Perhaps the milestone could be shifted to 2.3 or even later. For me this is more of a nuisance than a serious problem Agreed, we are in the process...

Yep, that is the point :)

 Hum, do you have the "protect server with password" option ticked in the server preferences? If yes, can you try without it?

@cischology have you tried to disable the password as shown above?

Looks like the problem comes from our embedded Telnet server. Dynamips has it's own server and it is doing things we have not implemented, for instance: https://github.com/GNS3/dynamips/blob/master/common/dev_vtty.c#L1041

Thanks for your PR! :)

> 1. Ignore (with a warning) all environment lines with an empty variable (starting with a `=`). Should have been fixed by https://github.com/GNS3/gns3-server/commit/aea4ae808f18a1031f0b438a7918658882893d6b > 2. Redesign the docker VM, so...

I guess we could add an API param when we call the create node API endpoint. Do you need this to be in the GUI as well?