Answer the question
In order to leave comments, you need to log in
OpenVpn Access Server+Elastix. Why can't I connect via sip?
The DC has a server with OpenVpn Access Server + Elastix. The task is to drive sip and internet traffic through vpn.
After connecting, I get the address 10.1.1.136
below the routing table
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
0/1 10.1.1.129 UGSc 46 0 utun0
default
192.168.4.1 UGSc 12 95 en0
10.1.1.128/27 10.1.1.136 UGSc 17 0 utun0
10.1.1.136 10.1.1.136 UH 3 6 utun0
127 localhost UCS 1 0 lo0
localhost localhost UH 21 952659 lo0
client.openvpn.net client.openvpn.net UH 1 209 lo0
128.0/1 10.1.1.129 UGSc 15 0 utun0
148.251.xxx.xxx/32 192.168.4.1 UGSc 2 0 en0
Why default gateway is 10.1 .1.129 and not 10.1.1.1?
Below is the route table on the VPN server itself
default via 148.251.xxx.xxx dev eth0 proto static metric 100
10.1.1.0/27 dev as0t0 proto kernel scope link src 10.1.1.1
10.1.1.32/27 dev as0t1 proto kernel scope link src 10.1.1.33
10.1.1.64/27 dev as0t2 proto kernel scope link src 10.1.1.65
10.1.1.96/27 dev as0t3 proto kernel scope link src 10.1.1.97
10.1.1.128/27 dev as0t4 proto kernel scope link src 10.1.1.129
10.1.1.160/27 dev as0t5 proto kernel scope link src 10.1.1.161
10.1.1.192 dev as0t6 proto kernel scope link src 10.1.1.193
10.1.1.224/27 dev as0t7 proto kernel scope link src 10.1.1.225
148.251.xxx.xxx/28 dev eth0 proto kernel scope link src 148.251.xxx.xxx metric 100
192.168.4.0/ 24 dev as0t5 proto static
from this we see that the route for my connection is raised
10.1.1.128/27 dev as0t4 proto kernel scope link src 10.1.1.129
Why does openvpn create its own route for each connection? And does not use one common 10.1.1.0/27 dev as0t0 proto kernel scope link src 10.1.1.1?
And now back to the main problem. If I connect to vpn from a computer, then I can connect via sip to 10.1.1.1
, I can also connect to all server services (ssh, http, etc.) ping works before it. But if I create a vpn connection on my home router, then I can no longer connect via the sip protocol, although the ping to the host 10.1.1.1 goes on.
How to make that for all connections the same gateway 10.1.1.1 was issued?
Or everything is in order but I configured something wrong?
Thanks in advance for your help
Answer the question
In order to leave comments, you need to log in
Damn, too lazy to delve into, but it looks like there is no static route to vpn on the router
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question