search

Ylianst / MeshCommander

MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
Apache License 2.0
326 stars 71 forks source link

Feature Request: Allow for multiple meshcmd routes #60

Open frakman1 opened 2 years ago

frakman1 commented 2 years ago

My use case is that I have multiple devices that I want to route SSH through. So on one local PC, I want to be able to have these tunnels open simultaneously.

localhost:1022 -> remote1:22
localhost:2022 -> remote2:22
localhost:3022 -> remote3:22
etc...

Currently, meshcmd accepts no inputs (other that password/token) and expects a single meshaction.txt file to be in that same directory for a single tunnel.

In order to do what I want,(I think) I would have to have multiple directories (one for each remote) with different, preset meshaction.txt files for each remote I want to connect through and a copy of meshcmd to run in that folder alongside its corersponding meshaction.txt file. e.g:

├── remote1
│   ├── meshaction.txt
│   └── meshcmd
├── remote2
│   ├── meshaction.txt
│   └── meshcmd
└── remote3
    ├── meshaction.txt
    └── meshcmd

Ideally, I would like to populate a single meshaction.txt file with all the tunnels I want to connect to and run a single instance of meshcmdto open all those tunnels locally.

Less ideally, I suppose you could have a parameter that specifies the path to the action file you want to use. However, this would method still end up with multiple instances of meshcmd running (one for each tunnel)