24 Apr 2017 
Support Center » Knowledgebase » The OpenVPN watchdog program fails to detect the private IP assigned by the OpenVPN server. Why might be wrong?
 The OpenVPN watchdog program fails to detect the private IP assigned by the OpenVPN server. Why might be wrong?
Solution This issue is normally caused as a result of non supported private IPs subnets or blocks of the IP address space for private Internets which is normally assigned to each client upon connection to the OpenVPN server. When using the program with third party OpenVPN service, you might encounter this problem. The Watchdog program heavily relies on these Private IPs to monitor secure connections by using the ipconfig and tracert commands to ensure that the private IP and the Default Gateway assigned to the TUN Virtual Interface belongs to the remote LAN you are connected thereby ensuring that the internet traffic is actually routed across the VPN and hence encrypted. However, since these private IPs allocation do vary from one provider to another, the Wachdog program may not work with your OpenVPN configuration.

Presently the program has been developed to work with the following Private IP ranges:

• 10.0.0.0-10.255.255.255
• 172.16.0.0-172.31.255.255
• 192.168.0.0-192.168.255.255
• 169.254.0.0-169.254.255.255

Before using the program, make sure your OpenVPN server has been configured to use one of the above private IP ranges.


Article Details
Article ID: 2
Created On: 03 Aug 2011 07:56 AM

 This answer was helpful  This answer was not helpful

 Login [Lost Password] 
Email:
Password:
Remember Me:
 
 Search
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | Troubleshooter | News | Downloads
Language:

Help Desk Software By Kayako SupportSuite v3.11.01