B is in the form of public IP server (public IP=121.4.131.141, Intranet IP=172.17.16.13),
C of a and B are in the same network server (network IP=172.17.16.4)
I install the configuration in the B a VPN Server, virtual LAN IP for: 10.192.122.1
I configure the VPN Client installation, on A virtual network card IP for: 10.192.122.2
After the success of the VPN connection, in win10 system on virtual IP can ping B=10.192.122.1 and Intranet IP=172.17.16.13, but can't C IP=172.17.16.4
How to configure to get WIN10 ping C?
C routing is as follows:
[root @ VM - 16-4 - centos ~] # route
The Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
The default _gateway 0.0.0.0 UG 100 0 0 eth0
172.17.16.0 0.0.0.0 255.255.240.0 U 100 0 0 eth0
B routing is as follows:
[root @ - 16-13 - VM centos ~] # route
The Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
The default _gateway 0.0.0.0 UG 100 0 0 eth0
10.192.122.0 0.0.0.0 255.255.255.0 U 0 0 0 wg0
172.17.16.0 0.0.0.0 255.255.240.0 U 100 0 0 eth0
WIN10 routing is as follows:
IPv4 routing table
===========================================================================
Routing:
Target network mask gateway interface jump points
0.0.0.0 0.0.0.0 192.168.1.1 192.168.29.18 35
10.192.122.0 255.255.255.0 10.192.122.2 across the link 291
10.192.122.2 255.255.255.255 10.192.122.2 across the link 291
10.192.122.255 255.255.255.255 10.192.122.2 across the link 291
127.0.0.0 255.0.0.0 127.0.0.1 331 across the link
127.0.0.1 255.255.255.255 127.0.0.1 331 across the link
127.255.255.255 255.255.255.255 127.0.0.1 331 across the link
172.17.0.0 255.255.255.0 10.192.122.1 10.192.122.2 135
172.17.16.0 255.255.255.0 10.192.122.1 10.192.122.2 135
192.168.0.0 255.255.224.0 192.168.29.18 across the link 291
192.168.29.18 255.255.255.255 192.168.29.18 across the link 291
192.168.31.255 255.255.255.255 192.168.29.18 across the link 291
192.168.106.0 255.255.255.0 192.168.106.1 across the link 291
192.168.106.1 255.255.255.255 192.168.106.1 across the link 291
192.168.106.255 255.255.255.255 192.168.106.1 across the link 291
192.168.154.0 255.255.255.0 192.168.154.1 across the link 291
192.168.154.1 255.255.255.255 192.168.154.1 across the link 291
192.168.154.255 255.255.255.255 192.168.154.1 across the link 291
255.255.255.255 255.255.255.255 127.0.0.1 331 across the link
255.255.255.255 255.255.255.255 192.168.29.18 across the link 291
255.255.255.255 255.255.255.255 192.168.106.1 across the link 291
255.255.255.255 255.255.255.255 192.168.154.1 across the link 291
255.255.255.255 255.255.255.255 10.192.122.2 across the link 291
CodePudding user response:
Lack of routing to 10.192.122 said at least C,