Connecting Flowpoint routers with TunnelBuilder or TunnelMaster

TunnelBuilder for Windows configuration
Flowpoint configuration for Windows TunnelBuilder
TunnelBuilder for Mac configuration
Flowpoint configuration for Mac TunnelBuilder

Using a Flowpoint router to connect into TunnelMaster VPN server

TunnelBuilder can connect successfully into Flowpoint routers as long as encryption is not selected.  The reason is that Flowpoint supports DES (IPSEC) encryption, and TunnelBuilder only supports RSA encryption (MPPE).  

TunnelBuilder for Windows configuration

Setting up the Windows TunnelBuilder is easy.  In this case, place the IP Address of the FlowPoint router in the VPN Server address field. Be sure to clear the checkbox for Require encryption.  

Next, you will need to include the name of the Tunnel identifier in the user name field, after the user name.  The default Tunnel Identifier is "localhost".  This is appended after the username with a "^" character separating them.  In the figure below, the user name is "tbuser" and the Tunnel Identifier is "tbtunnel"

If using the Chap Secret for L2TP tunnel authentication, you should add this password in the password field in the same manner.  In the following example, the user password is "tbpassword", and the Chap secret is "tbtunnelpassword".

Flowpoint configuration for Windows TunnelBuilder

To set up the Flowpoint for access from a TunnelBuilder client,  do the following:

Configure the addresses under the DHCP mode:

TunnelBuilder for Mac configuration

When using the Mac TunnelBuilder, there are two limitations to consider:  It doesn't support the L2TP tunnel Authentication, and it doesn't offer a configurable tunnel Identifier for the Flowpoint Hostname.  To configure the TunnelBuilder, simply enter the Flowpoint VPN address, the username and password as seen in the following figure.  Remember to select None for the type of Encryption:

Flowpoint configuration for Mac TunnelBuilder

When configuring the Flowpoint for Mac TunnelBuilder access, configure it the same as above, only use the name "localhost" as the L2TP identifier.  Remember to leave out the chap secret.
 

Remember to save the Flowpoint configuration before exiting.  When restarting, you may need to restart the remote entry, ie:

remote start tbuser

Further support for Flowpoint issues

Once TunnelBuilder makes the connection, any further configuration issues are with the Flowpoint router.  Check the Flowpoint manual for information on how to set up for routing considerations.

Using a Flowpoint router to connect into TunnelMaster

A Flowpoint router can connect successfully into a Tunnelmaster VPN server.  In this situation the Flowpoint is the client and the TunnelMaster is the LNS (TunnelMaster does not source VPN tunnels, it can only terminate them).

As usual, you need to turn off encryption since the Flowpoint uses DES, and TunnelMaster assumes RSA.  The TunnelMaster configuration can be set up using the following example:  

TunnelMaster configuration:

1. Set TM Server -> PPTP/L2TP

Check for L2TP Tunnel Authentication
Enter a valid hostname

2. Set TM Server -> Security

Check Encrypted Authentication (CHAP)
Uncheck Require Encryption

3. Set Database -> L2TP Authentication -> Add l2tp Tunnel Entry

Name = flowpoint
Password = fpsecret

4. Add Database -> User

Name=fpclient
Password=fppassword

5. By hand, change TMaster for Flow Control = Static Timeout.

This needs to be done by hand, because the HTML manager has a bug.  Save the *.ini files after editing, because changes to the HTML manager will cause this to revert back to off.  Edit the nts-vpn.ini:
        DataChannelFlowControl=1
        FlowControlTimeoutSeconds=10

Flowpoint configuration:

As usual, routing and ethernet information will need to reflect your network.