9) Test the tunnel
We'll use ping to check that everything is working. First, try pinging the OpenVPN router LAN IP address (the default is 192.168.1.1). It should respond. Next try to ping the IP address of a LAN machine. In my test case, the Win 8.1 LAN computer was at 192.168.1.149. The screenshot below shows a successful ping, indicating that the OpenVPN configuration provided connection to LAN clients.
OpenVPN tunnel test passed
10) Use the tunnel
At this point, you are up and running! Since this is a TAP connection, you should be able to see and browse machines on the OpenVPN router's LAN side.
I had three NETGEAR routers handy for testing. My go-to IxChariot performance test tool would not work through the OpenVPN tunnel. So I had to resort to drag-and-dropping a >1 GB Windows backup .bkf file for testing. Drag-and-drops were initiated from the remote (WAN side) machine to ensure that traffic flowed through the tunnel.
|Router||CPU||Firmware||Remote > Server||Server > Remote|
|NETGEAR R7000||Broadcom BCM4709
dual core, 1 GHz
|NETGEAR R7500||QCA IPQ8064 dual-core @ 1.4 GHz||v220.127.116.11||5.2||5.2|
|NETGEAR R8000||Broadcom BCM4709
dual core, 1 GHz
Table 1: File copy throughput - OpenVPN tunnel (MBytes/sec)
All three products use dual-core processors, so the results are very similar. The R7000 and R8000 results using a Broadcom BCM4709 processor are essentially the same as obtained with the ASUS RT-AC87U, which uses the same main CPU.
I wouldn't assign any significance to the slightly higher results for the R7000 because I was relying on the numbers provided in the Windows filecopy window.
I hope the step-by-step helps you get up and running quickly with NETGEAR routers supporting OpenVPN. If you find an error, please let me know so that I can correct it.