Sticky console port numbers

[fryguy_pa]

I upgraded to EVE-NG pro and have now noticed that the console port numbers for devices change when you reboot. Is there a way to make this sticky as it is causing issues with my setup. I have remote users who I work with and permit access over public internet for testing to a device, and when he reboots it - he loses access to the device.

Every time I need to log back in and change the NAT rule to the new port. I do not want to open up a range to him as he only needs access to a single router for testing.

[Uldis (UD)]

EVE Pro is using dynamic ports for reasons:
EVE Pro supports 1024 nodes er lab and thats why we cannot dedicate static ports for Pro labs. Because of multiuser support and 1024 nodes support
For that it is impossible to make EVE Pro with static ports for nodes..

EVE Pro will use dynamic ports only

[davparker]

Interesting. With the Community Edition I would use SuperPutty and build out folders for each lab with all the router names and console port numbers so all I needed to do was start my lab, then do everything else in SuperPutty. It would be cool if you could export a SuperPutty SESSIONS.XML file after the lab was started so you'd have all the dynamically assigned port numbers for your devices. Is there an api we can access to query that info?

[ecze]

Spy your web browser to see API calls...
and see documentation https://www.eve-ng.net/index.php/docume ... ve-ng-api/

E.