What is the correct way to differentiate VPN route and LAN route?

Question

Computer networks

Hello.
Sometimes you need to connect to a VPN to perform certain tasks.
Until some time, everything suited me: both the home network and the VPN network worked in parallel.
The turn has come to update the windows 10 kernel version in order to start operating Docker.
In general, Docker worked, BUT there was a big problem: when the VPN was activated, it became impossible to contact the local network hosts.
To connect to the VPN I use Cisco Any Connect 4.5.00058 (I tried the previous 4.4.02034, 4.4.00243).
In general, before VPN IPv4, the route table is:
======================================== ==================================
Active Routes:
Network Address Net Mask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.21 257
127.0.0.0 255.0.0.0 ON-LINK 127.0.0.1 331
127.0.0.1 255.255.255.255 On-Link 127.0.0.1 331
127.255.255.255 255.255.255.255 255.255.255.255 On-Link 127.0. 0.1 331
192.168.0.0 255.255.255.0 ON-LINK 192.168.0.21 257
192.168.0.21 255.255.255.255 On-Link 192.168.0.21 257
192.168.0.255 255.255.255.255 On-Link 192.168.0.21 257
224.0.0.0 240.0.0.0 On-Link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.0.21 257
...
================================================= =====================================================================
_
_ ================================================= ====
Active routes:
Network Address Mask Mask Address Gateway Metric Interface
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.21 257
7.0.0.0 255.0.0.0 7.7.194.193 7.7.194.20155.255.255
7.7.194.193 7.7.194.201 2
7.11.164.100 255.255.255.255 7.7.194.193 7.7.194.2012
7.7.194.192 255.255.255.192 On-link 7.7.194.2017
7.7.194.2015.255.255.255.255.255.255 On-Link 7.7.194.20155 On-Link 7.7.194.2015
7.7.194.255 255.255.255.255 On-Link 7.7.194.201 257
127.0.0.0 255.0.0.0 On-Link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-Link 127.0.0.1 331
127.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255. On-Link 127.0. 0.1 331
172.16.0.0 255.240.0.0 7.7.194.193 7.7.194.201 2
192.168.0.0 255.255.0.0 7.7.194.193 7.7.194.2012.193.0.0
255.255.25.0 On-Link 192.168.0.21 257
192.168.0.0 255.255.255.0 7.7.194.193 7.7.194.201 2
192.168.0.1 255.255.255.255 On-link 192.168.0.21 2
192.168.0.21 255.255.255.255 On-link 192.168.0.21 257
..
=================================== =======================================
How can I solve this problem?

Answer 1

managed to find such a solution,
manual definition of interface metrics for a real network connection - 1, for VPN - 2.
And changing Cisco Any Connect to OpenConnect: it turned out that Cisco Any Connect, no matter what you install, it does arrange the interface metrics in its own way discretion, regardless of the settings of the OS administrator.