Re: legacy behavior: bind to all local addresses (General questions)

by rs4u, Friday, November 11, 2005, 12:25 (6750 days ago) @ wodSupport

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

2103 views

Complete thread:

legacy behavior: bind to all local addresses - rs4u, 2005-11-11, 08:32
- Re: legacy behavior: bind to all local addresses - wodSupport, 2005-11-11, 12:18
  - Re: legacy behavior: bind to all local addresses - rs4u, 2005-11-11, 12:25
    - Re: legacy behavior: bind to all local addresses - wodSupport, 2005-11-11, 12:42
      - Re: legacy behavior: bind to all local addresses - rs4u, 2005-11-11, 13:32

Count us as a satisfied WeOnlyDo customer. We appreciate your terrific support to get the secure Telnet working properly.

Don Fitzpatrick

InterNetworx Systems

I've heard that you are amazing with your replies coming back so quickly - and now I've seen the speed in which you reply first hand.

Andrew Narracott

Sun Computer Consultancy

May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?

Michael Barnett

Full Spectrum Telecommunications