Qbik Helpsys

VPN Participants

VPN Participants are machines on the network of either the Master Node (VPN Host) or VPN Client Nodes, that have been configured to participate in the VPN.

Their participation can be either in the form of sharing resources on their machine, or being a user on that machine who is accessing other VPN Participant resources in the WinGate VPN.

VPN Participants

Node participation

Each VPN Node that will be involved in the VPN (including the Master Node) can set what type of participation its network will provide.

  • For the Master Node:

    These options are set in the Host VPN properties.

    1. No participation

      The Master Node will simply be the host and facilitator of other Nodes joining the VPN. Neither the Master Node machine or its network will be accessible to the VPN.

    2. Local machine only

      The Master Node machine will be a VPN Participant and share resources. The network of the Master Node will be inaccessible to the VPN.

    3. Local Network

      Computers on the network of the Master Node can be VPN participants and make resources available in the VPN. When choosing this setting, you have to determine how many VPN Participants there will be on the network of the Master Node LAN. This is to ensure that the Master Node machine has an adequate VPN License to cover them.

  • For each VPN Node that will connect to the VPN:

    • Local machine

      Only the VPN Client Node machine will participate in the VPN.

    • Local network

      This VPN Client Node machine and all other configured machines on it's LAN will participate in the VPN.

Configuring VPN Participants

Since WinGate VPN is a routing based VPN there is no special software requirements for setting up non Node machines as VPN Participants. A VPN Participant only needs to know the way to the other machines on the VPN with correct routing.

There are three possible ways to do this:

  1. Default gateway

    In the network properties of the LAN interface for each VPN Participant, the default gateway should be set to the IP address of the appropriate WinGate VPN Node (machine) for the LAN. This forces all network traffic that the VPN Participant does not consider local to be sent through to the VPN Node machine, who will then route the appropriate traffic to the remote network.

  2. RIP listener

    WinGate VPN can broadcast route updates as it becomes aware of new VPNs becoming available. If you install a RIP v 2 compatible listener on the VPN Participant machine, it will receive these RIP broadcasts and be able to route traffic destined for the remote subnet to the VPN Node.

    If the VPN Node machine on the LAN is not your Internet Gateway, it is possible that your Internet Gateway will support RIP v 2. (Most DSL/NAT boxes have a RIP v 2 Listener built in) If thisis the case, you can turn it on for the gateway.

    Read more on the scenario where the WinGate VPN machine is not the default gateway for the network

  3. Static route

    By adding a static route to the operating system route table of the VPN Participant workstation, so that it knows how to route to the remote subnet.

You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:

  • event management (no quotes) will find all pages containing the words "event" OR "management"
  • "event management" (with quotes) will find all pages containing the phrase "event management"
  • +event -management will find all pages containing the word "event", AND NOT the word "management"