Re: wodVPN For 1 Server - N Client Scenario (General questions)

by wodDamir, Friday, October 10, 2008, 21:02 (5886 days ago) @ Tanmay

Tanmay,

Did you set Threads property to true? If not, please try it too.

Also, in order to accept multiple connections, you should do something like this:

[code] VpnServer1.Mediator.Timeout = 15;
VpnServer1.Threads = true;
VpnServer1.MediatorConnected += new WODVPNCOMLib._IwodVPNComEvents_MediatorConnectedEventHandler(VpnServer1_MediatorConnected);

VpnServer1.Mediator.Start(WODVPNCOMLib.SearchEnum.SrchUDPSingle,8000);[/code]

As you can see from the above code, we would use MediatorConnected to detect incoming connection. We do that in order to initiate new wodVPN instance, which will do search (for the incoming peer's ID)and establish connection to it once found.

I've tried the above, and I was able to connect two peers to server instance of wodVPN.

However, please note that wodVPN is peer-2-peer component. There is no Server-client approach available. Server in this case can only be many instances of wodVPN.

Also, in Adapter based wodVPN you still will need multiple component instances for the above mentioned reason. Each wodVPN component can connect only two peers. You need new instances to connect more peers.

As for your last question, when you use Adapter, *all* traffic is redirected between peers, while when using channels, only certain traffic is redirected.

Regards,
Damba