# Bugreport: Split-include buggy for (at least) IKEv2 (6.40.2 current and 6.41rc18)

**URL:** <https://forum.mikrotik.com/t/bugreport-split-include-buggy-for-at-least-ikev2-6-40-2-current-and-6-41rc18/111635>\
**Category:** General\
**Created:** [August 25, 2017, 2:29pm UTC](https://forum.mikrotik.com/t/bugreport-split-include-buggy-for-at-least-ikev2-6-40-2-current-and-6-41rc18/111635 "2017-08-25T14:29:41Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![emils](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/emils/32/1457_2.png) [@emils](https://forum.mikrotik.com/u/emils)\
**Post date:** [October 29, 2018, 9:42am UTC](https://forum.mikrotik.com/t/bugreport-split-include-buggy-for-at-least-ikev2-6-40-2-current-and-6-41rc18/111635/13 "2018-10-29T09:42:54Z")

</div>

> [@](#):
>
> **What’s new in 6.44beta28 (2018-Oct-29 07:58):**
> 
> \*) ike2 - send split networks over DHCP (option 249) to Windows initiators if DHCP Inform is received;

IKEv2 can now respond to DHCP Inform requests from Windows devices. This feature currently works on peers with specific Vendor ID which should include all Windows operating systems. One thing to keep in mind - Windows always requests TSr of 0.0.0.0/0, so it is necessary to allow the responder to generate policy with src-address=0.0.0.0/0.

As for iOS and macOS - they only accept the first split-network provided to them. It is a limitation on their side and there currently is no workaround.

---

_[View the full topic](https://forum.mikrotik.com/t/bugreport-split-include-buggy-for-at-least-ikev2-6-40-2-current-and-6-41rc18/111635)._
