To begin with, I am not a Network GURU and I’m new to open VPN, so go gently on me…
I’m trying to connect remote OpenVPN SIP clients to a home SIP server and make calls between the remote and the local phones as well as route calls out SIP trunks from the SIP server.
I am able to get the VPN client to connect but can pass absolutely nothing after that, including pings or even a trace route. It would seem that pings are making it to the OpenVPN client as I can see the UPD packets on the Bridged NTW adapter interface via Wireshark.
I suspect that it is a routing issue and possibly a bridging issue.
Note: if the SIP server and phones are all on the same subnet as the OpenVPN bridged network (all on 10.10.1.0) I can get the remote phone to connect, but have uni-directional RTP data transfer. The RTP packets leaving the SIP Server side of the network are sent to the local IP address of the remote phone rather than the VPN IP address for which there is not visibility on the VPN 10.10 network.
Ultimately I want to connect Yealink SIP clients at a home network.
Basic Topology –
Remote Client
local IP 192.168.1.141 255.255.255.0 192.168.1.1
OpenVPN Server (Windows 7)
NIC1 10.10.1.2 255.255.255.0 10.10.1.1 (Bridged to OpenVPN Tap adapter)
NIC2 10.10.2.1 255.255.255.0 10.10.1.1
SIP Server
10.10.2.22 255.255.255.0 10.10.2.1
Home SIP Endpoints
10.10.2.101 255.255.255.0 10.10.2.1
10.10.2.102 255.255.255.0 10.10.2.1
Server Config...
local 10.10.1.2
port 1194
proto udp
dev tap
ca c:\\work\\openvpn\\keys\\ca.crt
cert c:\\work\\openvpn\\keys\\server.crt
key c:\\work\\openvpn\\keys\\server.key
dh c:\\work\\openvpn\\keys\\dh1024.pem
ifconfig-pool-persist ipp.txt
server-bridge 10.10.2.100 255.255.255.0 10.10.2.150 10.10.2.199
server-bridge
push "route 10.10.2.0 255.255.255.0"
duplicate-cn
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 6
mute 20
Server “route print”
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.1.1 10.10.1.2 266
10.10.0.0 255.255.0.0 On-link 10.10.2.1 266
10.10.1.0 255.255.255.0 On-link 10.10.1.2 266
10.10.1.2 255.255.255.255 On-link 10.10.1.2 266
10.10.1.255 255.255.255.255 On-link 10.10.1.2 266
10.10.2.0 255.255.255.0 On-link 10.10.2.1 20
10.10.2.1 255.255.255.255 On-link 10.10.2.1 266
10.10.2.255 255.255.255.255 On-link 10.10.2.1 266
10.10.255.255 255.255.255.255 On-link 10.10.2.1 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 169.254.42.43 286
169.254.42.43 255.255.255.255 On-link 169.254.42.43 286
169.254.255.255 255.255.255.255 On-link 169.254.42.43 286
192.16.2.0 255.255.255.0 192.16.2.1 10.10.1.2 20
192.16.2.0 255.255.255.0 192.16.2.1 10.10.2.1 20
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 169.254.42.43 286
224.0.0.0 240.0.0.0 On-link 10.10.2.1 266
224.0.0.0 240.0.0.0 On-link 10.10.1.2 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 169.254.42.43 286
255.255.255.255 255.255.255.255 On-link 10.10.2.1 266
255.255.255.255 255.255.255.255 On-link 10.10.1.2 266
Client Config…
client
dev tap
proto udp
remote 70.70.70.70 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca keys/ca.crt
cert keys/client1.crt
key keys/client1.key
comp-lzo
Client “route print”
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.148 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.148 192.168.1.148 20
192.168.1.148 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.148 192.168.1.148 20
224.0.0.0 240.0.0.0 192.168.1.148 192.168.1.148 20
255.255.255.255 255.255.255.255 192.168.1.148 192.168.1.148 1
255.255.255.255 255.255.255.255 192.168.1.148 3 1
Default Gateway: 192.168.1.1
===========================================================================