无法访问OpenVPN服务器背后的LAN设备

我有OpenVPN运行在Ubuntu服务器16.04（10.122.224.2）。 在与OpenVPN服务器（10.122.224.0/24）相同的LAN上，我有一个VoIP PBX（10.122.224.5）。

就我而言，我在同一个子网上有一台IP电话（192.168.10.110）和一台Windows电脑。 我可以将Windows PC和IP电话都成功连接到VPN，并在10.122.222.0/24 VPN子网中获取IP。 Windows PC和IP Phone可以通过10.122.222.0/24子网相互ping通，也可以ping 10.12.224.2的OpenVPN服务器，但是无法ping通10.122.224.5的集团电话。 OpenVPN服务器可以ping所有设备没问题。

我已经在OpenVPN服务器上启用IPv4转发，我在我的OpenVPN服务器configuration中添加了推送路由。 我似乎无法通过连接到VPN的客户端访问OpenVPN服务器后面的子网。

这是我的服务器configuration看起来像

• 同一networking上的服务器不通信
• 主机重启后如何重启KVM网桥？
• 我只能ping一台电脑之后，其他电脑ping我之前
• 与firewalld和libvirt / KVM的多个networking
• 可以远程连接本地服务器，但不能本地连接（ssl）

local PUBLIC_IP port 1194 proto udp dev tun ca /etc/openvpn/keys/ca.crt cert /etc/openvpn/keys/cloudco.crt key /etc/openvpn/keys/cloudco.key dh /etc/openvpn/keys/dh2048.pem server 10.122.222.0 255.255.255.0 push "route 10.122.224.0 255.255.255.0" client-to-client comp-lzo no keepalive 10 120 persist-key persist-tun verb 3 tls-server log-append /var/log/openvpn.log 

这里是客户端configuration

 remote PUBLIC_IP client dev tun resolv-retry infinite ping 10 persist-key persist-tun float comp-lzo no proto udp ca keys/ca.crt cert keys/pctest.crt key keys/pctest.key ns-cert-type server pull 

我搜查了一下，发现了一些解决scheme，为别人工作，但似乎并没有为我工作。 寻找一些方向。

编辑我已经从Ubuntu切换到VyOS。 VPN服务器启动后，我可以连接到VPN，但我仍然无法访问VPN后面的LAN设备。 VyOS盒是LAN的网关。

路由跟踪

10.122.224.5至10.122.222.2

 traceroute to 10.122.222.2 (10.122.222.2), 30 hops max, 60 byte packets 1 gw.sv2.orionvm.net (23.90.82.1) 0.955 ms 1.039 ms 0.884 ms 2 192.168.50.1 (192.168.50.1) 1.071 ms 0.971 ms 0.956 ms 3 206.16.209.233 (206.16.209.233) 1.205 ms 0.919 ms 1.185 ms 4 mdf001c7613r0001-gig-10-3.wdc1.attens.net (63.240.192.137) 32.565 ms 32.557 ms 32.426 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 

10.122.222.2至10.122.224.5

 λ tracert 10.122.224.5 Tracing route to 10.122.224.5 over a maximum of 30 hops 1 41 ms 41 ms 39 ms 10.122.222.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. 

10.122.222.2给vyos public

 λ tracert 23.90.82.138 Tracing route to 23-90-82-138.sv2.orionvm.net [23.90.82.138] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.10.1 2 1 ms 8 ms 10 ms agg15.lncsnycd01h.northeast.rr.com [24.58.27.213] 3 9 ms 9 ms 9 ms agg37.lkwnnyad02r.northeast.rr.com [24.58.38.24] 4 16 ms 13 ms 15 ms be29.albynyyf01r.northeast.rr.com [24.58.32.58] 5 24 ms 26 ms 21 ms bu-ether16.nycmny837aw-bcr00.tbone.rr.com [66.109.6.74] 6 17 ms 17 ms 17 ms unk-426d0577.adelphiacom.net [66.109.5.119] 7 17 ms 19 ms 19 ms nyk-b6-link.telia.net [62.115.156.214] 8 17 ms 17 ms 18 ms nyk-b5-link.telia.net [213.155.130.32] 9 35 ms 36 ms 36 ms 192.205.34.53 10 40 ms 39 ms 42 ms cr2.n54ny.ip.att.net [12.122.130.110] 11 40 ms 43 ms 39 ms cr2.wswdc.ip.att.net [12.122.28.42] 12 131 ms 134 ms 66 ms gar3.ascva.ip.att.net [12.122.113.89] 13 80 ms 39 ms 40 ms 12.122.251.206 14 49 ms 48 ms 47 ms mdf002c7613r0002-gig-12-1.wdc1.attens.net [63.240.192.142] 15 39 ms 39 ms 40 ms 206-16-217-10.attens.net [206.16.217.10] 16 * * * Request timed out. 17 37 ms 37 ms 38 ms 23-90-82-138.sv2.orionvm.net [23.90.82.138] Trace complete.