Telnet Proxy Changes in V6 vs V5 question

[rcyoung]

I had to install Wingate fresh due to other unrelated problems on my system . As a result, I decided to install a newer version (V6.x) which I had sitting on my desktop for a long while but simply never got around to. Previously I was running V5. I finally downloaded the latest (V604) and installed it.

I have one problem however. In the earlier version (V5) I could set a Telnet Proxy to take input from the "external" (ie Internet) connection, and send it out on the "internal" (local LAN). This was very useful if I needed to "telnet" back to an internal machine while I was traveling. Now, however, I do not see an entry for the local LAN IP address on my selection list for the gateways for the Telnet Proxy. Only local dialout and the "external" interface are listed.

Is there no way to go from "out to in" anymore? I travel , so the previous ability to go back via telnet was quite useful to reach our "mainframe" systems remotely.

[Pascal]

What you want to do is use "Binding Policies". This is one of the major changes. It is no longer based on a specific IP but on a designation. This way, adapters which connect / disconnect can also be bound to.

In effect, you are now specifying 'rules' rather than 'absolutes' for what to bind to. So, for Telnet to be available on the internet you would need to specify a binding policy which will bind to the external adapter. (You can choose a specific one or all, etc.)

[rcyoung]

Binding to the external interface makes sense, and it does show up under the bind list. What about the gateway however? Correct me if I am wrong, but I was viewing the bind as the point where connections would be initiated on the telnet prozy (for my remote usage), and the "gateway" where the communication would be sent out (eventually to the local mainframe type system). If this interpretatin is correct, then the problem is that the gateway list has no listing for the ethernet port going out to the mainframe (on the internal network). If my interpretation is incorrect, could you describe how I should set it up ?

[Pascal]

You do not need to configure anything on the gateway side. You are correct about the useage for each of those tabs, but the gateways are only if you want to override what normal routing would normally determine. Bindings are where the service 'listens' for connections.

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.60 192.168.0.67 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.67 192.168.0.67 20
192.168.0.67 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.67 192.168.0.67 20
224.0.0.0 240.0.0.0 192.168.0.67 192.168.0.67 20
255.255.255.255 255.255.255.255 192.168.0.67 192.168.0.67 1
Default Gateway: 192.168.0.60

A route table will look something like that. Now, normally, the mainframe system will be, for example, 192.168.0.5. That is on the same subnet reachable by normal routing, so you shouldn't need to configure anything for it.

Gateways are normally only for people who have multiple interfaces and want to ensure that traffic goes out a specific interface (Such as ADSL + Dial-up, with telnet over dialup and HTTP over ADSL, etc.)