wodVPN For 1 Server - N Client Scenario (wodVPN)

by Tanmay, Friday, October 10, 2008, 17:54 (5678 days ago)

Hello,
We have wodVPN component [v2.0.1 July 20, 2008], to achieve our SIMPLE (!!) requirement, which we are not able to get through. As it's becoming much urgent, we would like to get specific and timely response, which we have observed, to occur, at support forum.

Our requirement is as below [which should be very familiar]:
1. A dedicated server, which would run Mediator [script or application, doesn't matter at this stage].
2. A LAN Server, which would act as application and DB server to our enterprise application; this server MUST provide a mean for N-Clients to connect to it using wodVPN.
3. A client application, that would connect to server [by looking up at mediator].

The key concern here is, implementation of wodVPN at server side, to enable multiple connections at any given point of time.

Per our interpretation of wodVPN behavior, we expected to achieve this by doing following AT SERVER SIDE:
1. Create wodVPN instance.
2. Call wodVPN.Start for port 'p'.
3. Whenever a client would need to connect, it would send SEARCH request to mediator; mediator would respond with server's IP and port 'p'; and then, client invokes CONNECT to server with given IP and port.
4. When CONNECTING event fires at server, respond to the request to accept the connection [after some business checks] which causes CONNECTED event to fire.
5. At CONNECTED event, create a NEW CHANNEL, for this client and ensure all NOW-ON communication for THIS client, occurs through THIS NEW CHANNEL only.
6. This leaves our original port 'P' FREE FOR NEW CLIENT requests.

Having this interpretation, we tried a lot to achieve 5 and 6, but NO SUCCESS. The result was, once any one client connected to server on port 'p', even after creating a new channel with ANOTHER port of server, with that client, the server DID NOT ACCEPT connections from any other client.

After a while, we received new version of SDK that used virtual adapter; and we came to know it automatically handles this; but still we do NOT find this to occur.

This makes wodVPN usage in question, if it misses such basic thing OR guidance to achieve such basic thing/objective. Still, we are inclined to believe that we might be missing something, due to lack of clear documentation [real classes have certain +/- then pdf!!].

We would like to know the SPECIFIC STEPS, at SERVER and CLIENT side [for our above requirement] that we should implement with wodVPN, to achieve our objectives 1 to 6 above.

Additionally, it would help us greatly if we get answers on some of our fundamental questions, to clarify our doubts:

1. Given that we are using Adapter based wodVPN, is it MUST to have MORE THEN ONE instance of wodVPN, to support N-clients [or incoming connections] OR is it possible through SINGLE wodVPN instance?

2. Given that we are using Adapter based wodVPN, does channel and port forwarding concepts have any significance now? better, what is the impact on channel and port-forwarding concepts, by inclusion of Adapter in wodVPN?

A thorough and timely response would be MUCH MUCH appreciated.