Jörg Kost

Since 0.4: It would be cool to drop from shellmode access directly to an interactive shell on the router.

For shellmode the connection is dropped after a command. Maybe it would be wise to have a connection pool with a persistent connection for the second command.

Add constant pull mode

1

There should be a flag to constantly run a command and watch the output, e.g. show interface $x.

Instead printing line by line, there could be a function to split outputs for a constant pull mode horizontally or vertically. Not so sure about Windows-Terminal here.

Instead log.Fatal return a specific error that we can handle.

The apiserver cache download shall check for the peeringdb timestamp and warn if our cache is too old.

The ixworker code shares too many duplicate code lines for configured peer from the INI-file and wildcard peer configuration.

In the peering.ini configuration it would be nice to limit the peering neighbor to a fixed single address instead configure all addresses.

https://www.juniper.net/documentation/en_US/junos/topics/reference/general/junos-xml-protocol-configuration-mapping-to-json.html _Note: Starting in Junos OS Release 16.1, devices running Junos OS emit JSON-formatted configuration data using a new default implementation for serialization._ _Note: Starting in Junos OS Releases 16.1R4,...