The problem is not with the VPN server, because the routes are applied correctly when I connect to it from Windows 10. These routes should be added automatically, because they are present in split-include, on the VPN server: /ip ipsec mode-configĪdd address-pool=vpn.my.server.hu address-prefix-length=32 name="modeconf vpn.my.server.hu" split-include=192.168.13.0/24,10.0.88.0/24 static-dns=10.0.88.1 system-dns=no It seems that packets for 192.168.13.0/24 are transformed and routed to the VPN server correctly. The first route given in split-include is added as an ip transformation. a direct route to the local (home) router 192.168.14.1.a link-local default address 169.254.0.0.a route to the public WAN address (replaced with 1.2.3.4).VPN client IP (offered by the VPN server): 10.0.88.100.It also has other internal networks connected (this is why I need to push multiple routes from the VPN server).Public WAN address 1.2.3.5 (replaced the real IP).FQDN *.my.server.hu (replaced the real name).Pool reserved for VPN clients: 10.0.88.0/24.This is the question: why doesn't it apply all routes? How can I fix this? I can connect to the server, but not all routes pushed by the server are applied on the client side. The server uses x509 certificates and private/public key pairs for authentication. I have an IPSEC/IKEv2 VPN server (on a MikroTik router) and I'm trying to connect to it from my Ubuntu 20.04.1 LTS system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |