Description Fires when user wants to open incoming
connection through remote wodVPN peer.
Syntax
Private Sub object_SocksBind(Chan, User, RemoteAddress, RemotePort, Login, Password, Allow)
The SocksBind Event syntax has these parts:
|
| object | A wodVPN object. | | Chan | A VPNChannel
object. Reference to channel used. | | User | A VPNUser
object. Reference to user that wants to bind a remote port. | | RemoteAddress |
A String value. IP address of the bound interface. | | RemotePort |
A Long value. Port on remote side that should be opened for
listening. | | Login |
A String value. Login/Username supplied by the application, if any. | | Password |
A String value. Password supplied by the application, if any. | | Allow |
A Boolean value. When set to False, wodVPN aborts the
request. |
Remarks SocksBind event is only fired 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 event is fired, you will get information
about this socks request so you can evaluate it and Allow
(default value) if needed.
This event 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 that case the appropriate event will be fired (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.
|
SocksBind Event
