legacy behavior: bind to all local addresses (wodSSH / wodSSH.NET)

by rs4u @, (7160 days ago)

Hi Kreso,

as much as I love the enhanced feature of SSHTunnel to only bind to the specified address instead of all available for local port forwardings I could use a 'backwards compatibility' feature too:
It would be great if a PF definition of 0.0.0.0:1234:remotehost:1234 bound to all local IP addresses (127.0.0.1 - 127.255.255.254; + all local addresses).
This would emulate the behavior of most other SSH clients when told
ssh -L 1234:remotehost:1234

Is that possible?

Thank you, Rainer

locked

Re: legacy behavior: bind to all local addresses

by Jasmine, (7160 days ago) @ rs4u

Rainer,

I'm not following you. You talk about channels, right? Can you rephrase your suggestion?

locked

Re: legacy behavior: bind to all local addresses

by rs4u @, (7160 days ago) @ Jasmine

Kreso,

tunnel.channel.add (0, 127.0.0.1, 1234, remotehost, 1234) binds to 127.0.0.1:1234 and forwards to remotehost:1234.
tunnel.channel.add (0, 0.0.0.0, 1234, remotehost, 1234) binds to no local address.
Legacy clients only provide -L port:remotehost:port and bind to all available local addresses.

I liked this feature too, my suggestion was to use 0.0.0.0 to indicate wodSSHTunnel shall bind to all local addresses.


I am not sure if that is more clear?

Rainer

locked

Re: legacy behavior: bind to all local addresses

by Jasmine, (7160 days ago) @ rs4u

Rainer,

but I think that even now if you set 0.0.0.0 it binds to all addresses, doesn't it?

This is optional parameter. If you don't set it up, it will also bind to all interfaces.

locked

Re: legacy behavior: bind to all local addresses

by rs4u @, (7160 days ago) @ Jasmine

Kreso,

just tested and as ever so often this was my mistake.
Shame on me.


Thank you, Rainer

locked