Community discussions

MikroTik App
 
AndreyMoiseev
just joined
Topic Author
Posts: 1
Joined: Tue Aug 03, 2021 4:16 pm

ipsec ikev2 + Windows 10 klient Routes are not transmitted to the client

Tue Aug 03, 2021 4:39 pm

Sorry for my English, it is far from ideal.
When connecting, the client (Windows 10) does not receive a route.
192.168.10.0/24 network route to which I want to transfer to the client (split-include=192.168.10.0/24)
Mikrotik
/interface bridge
add name=bridge1
/interface list
add name=Lan
add name=Wan
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip ipsec policy group
add name=ikev2
/ip ipsec profile
add name=ikev2Pr
/ip ipsec peer
add exchange-mode=ike2 name=peerikev2 passive=yes profile=ikev2Pr
/ip ipsec proposal
add name=Ikev2Prop pfs-group=none
/ip pool
add name=dhcp_pool1 ranges=192.168.10.2-192.168.10.254
add name=ipsecpool ranges=10.20.0.100-10.20.0.199
/ip dhcp-server
add address-pool=dhcp_pool1 disabled=no interface=bridge1 name=dhcp1
/ip ipsec mode-config
add address-pool=ipsecpool name=MdIkev2 split-include=192.168.10.0/24 \
    system-dns=no
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
/ip neighbor discovery-settings
set discover-interface-list=Lan
/interface list member
add comment=INTERNET interface=ether1 list=Wan
add comment=LOKALKA interface=ether2 list=Lan
add interface=ether3 list=Lan
add interface=ether4 list=Lan
add interface=bridge1 list=Lan
/ip address
add address=192.168.10.1/24 interface=bridge1 network=192.168.10.0
/ip dhcp-client
add disabled=no interface=ether1 use-peer-dns=no
/ip dhcp-server network
add address=192.168.10.0/24 gateway=192.168.10.1
/ip dns
set allow-remote-requests=yes servers=8.8.8.8,77.88.8.8
/ip dns static
add address=127.0.0.1 name=vk.com
add address=*.*.*.* name=ipsec.ru
****************************
settings firewall and skip
****************************
/ip ipsec identity
add auth-method=digital-signature certificate=server generate-policy=\
    port-strict mode-config=MdIkev2 peer=peerikev2 policy-template-group=ikev2
/ip ipsec policy
add dst-address=10.20.0.0/24 group=ikev2 proposal=Ikev2Prop src-address=\
    0.0.0.0/0 template=yes
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www disabled=yes
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/system clock
set time-zone-name=Europe/Moscow
/system identity
set name=MikGATE
/tool mac-server
set allowed-interface-list=Lan
/tool mac-server mac-winbox
set allowed-interface-list=Lan
/tool mac-server ping
set enabled=no
I don’t understand why the route doesn’t go to the client when connecting ?
 
nagylzs
Member
Member
Posts: 354
Joined: Sun May 26, 2019 2:08 pm

Re: ipsec ikev2 + Windows 10 klient Routes are not transmitted to the client

Wed Aug 04, 2021 7:10 pm

After connecting to the vpn server, please send the output of this (as administrator):

router print -4
 
rajo
newbie
Posts: 45
Joined: Tue Aug 16, 2011 11:12 pm

Re: ipsec ikev2 + Windows 10 klient Routes are not transmitted to the client

Thu Aug 12, 2021 7:18 pm

For split-include to work on Windows 10, modify your VPN connection properties as follows:

1. Select the VPN connection to modify, in the "Settings" applet and choose "Change adapter options" under "Related Settings"
2. In the "Network Connections" window, right-click the VPN connection and choose "Properties"
3. Choose the "Networking" tab and for each protocol (IPv6 and/or IPv4) you wish to configure:
a) Highlight the protocol and click "Properties"
b) Click "Advanced"
c) Uncheck "Use default gateway on remote network"
d) Check "Disable class based route addition"

Once all changes are done, that's it. Now Windows respect RouterOS split-include configuration.

I have already sent this information to MikroTik support, so hopefully they will update the Wiki with the solution.

Who is online

Users browsing this forum: Bing [Bot], cyrq, NetworqAndy, Phaere and 68 guests