Re: [44net] AMPR VPN

You will have to forgive me. I know VPNs from the Cisco IPSec point of view. The concepts should be the same. When you connect to the VPN, you should be assigned a 44 address from your VPN server pool. You should also be assigned a secured route table and a DNS server if configured. Now, depending on your VPN server policy config, if you are using split tunneling, any traffic that matches your secured route will flow over the VPN tunnel back to the VPN server and be routed from there. If the traffic does not match the secured route, it uses your device's routing table and tries to route over the public internet. That is why you still see your public IP when you are connected. Maybe there is an option to disable split tunneling so any traffic will use the secure route when you are connected to the VPN server. I assume you are using OpenVPN server on Linux? If so, does this link help? https://openvpn.net/index.php/access-server/docs/admin-guides/215-how-to-se… Is anyone out there more familiar with OpenVPN? Thanks Jesse - WC3XS Sent from my iPhone