Problem removing local ports with the fwd command

[Senyoret1]

If you use skywire-cli fwd -d{port} to stop sharing a local port, it does not work. In fact, if you call skywire-cli fwd -d{port} and then skywire-cli fwd –l, the port will not appar on the list, as if thge port were removed correctly. However, if you have previously stableshed a connection to that port from a remote visor (using skywire-cli rev), you will still be able to get data from the port as if nothing were changed, unless you restart the visor that is serving the port, or use skywire-cli rev -d from the client visor.

This should not happend, if the server visor calls skywire-cli fwd -d{port}, all remote visor should stop being able to get data from the port at that moment.

I tested this serving ports from Windows and accessing them from Linux, and the other way arround.

[0pcom]

You have to deregister them by their ID, not by the port number

view the IDs of the currently forwarded connections with skywire-cli fwd -l

they should start at 1, so if you have only one set up you can do

skywire-cli fwd -d 1

[Senyoret1]

I checked again and the problem is still present. skywire-cli fwd -d needs the port number, not the ID, the cli command that needs the ID is skywire-cli rev -d. I tested various times with the latest develop and the problem still persists.