SocksBind Method
      
 

Description

Called when user wants to open incoming connection through remote wodVPN peer.

Return Type

None  

Syntax

object.SocksBind Owner, Chan, User, RemoteAddress, RemotePort, Login, Password, Allow

The SocksBind Method syntax has these parts:

PartDescription
objectAn expression evaluating to an object of type IwodVPNNotify.
Owner A wodVPNCom object. Reference to the wodVPNCom instance that called this notification method.
Chan A VPNChannel object. Reference to channel used.
User A VPNUser object. Reference to user that wants to bind a remote port.
RemoteAddressA String value. IP address of the bound interface.
RemotePortA Long value.

Port on remote side that should be opened for listening.

LoginA String value. Login/Username supplied by the application, if any.
PasswordA String value. Password supplied by the application, if any.
AllowA Boolean value. When set to False, wodVPN aborts the request.

Remarks

This method is called only if you have implemented the IwodVPNNotify interface in your application and the wodVPN1.Notification property has received a reference to an instance of your implementation.

SocksBind notification method is only called when you created TCPSocksProxy channel, and local application wants to open port on remote wodVPN peer that services should connect to in order to be forwarded locally. When this notification is called, you will get information about this socks request so you can evaluate it and Allow (default value) if needed.

This notification informs you that request has been made. This doesn't yet necessarily mean that connection is established (it may still fail with an error), but in this case the appropriate notification will be called (such as UserDisconnected).

wodVPN cannot know the IP address of the interface actually used for listening on remote side. Typically, this will be same IP address of the interface where you got connected to him, but this doesn't have to be 100% correct information. So, in order for applications to receive correct IP address, you will need to fill up RemoteAddress argument. When doing so, please use IP address of the interface, not its hostname.