I've also commented about this issue in this thread:
viewtopic.php?f=1&t=173952
That this may be caused by DHCP is new to me though.
@rextended
Happens with newest available WinBox version (v3.27).
Here is a log trace:
ACCESS VIOLATION EXCEPTION at address: _________ 46b46c
rip=_________ 46b46c eflags=__ 10213
rdi=_______________0 rsi=________ 2144c50 rbp=____________ 12c rsp=_________ 32e
0e0
rax=_________ 52fc08 rbx=________ 2ec62f4 rcx=_______________0 rdx=_____________
__1
r8=_________ 32e108 r9=________ 36b0000 r10=_______________0 r11=_________ 32e
018
r12=_________ 32e108 r13=_________ 32e110 r14=_________ 32e1f8 r15=________ 2e90
9c0
winbox version: 3.27
backtrace:
_________ 46b46c
_________ 4d0aed
_________ 4f1fb7
_________ 455b53
_________ 4565ca
_________ 45d738
_________ 42f0f3
_______ 6eba0695
_______ 6eba28c9
_______ 6eb627d1
_________ 42b717
_________ 4b3065
_________ 4013b4
_________ 4014db
_______ 7b62c669
_______ 7bc5a8e3
stack:
_________ 32e2d0 _________ 32e108 ____________ 12c _________ d003c9 __________ 1
004f _________ 52fc08 _________ 580358 _________ 580380
______ 600000042 _____ 2000000000 _______________0 ________ 2ec7c60 ____________
___0 _______________0 _______________1 _________ 32e2d0
_________ 32e1f8 ________ 2eb6e60 _________ 32e1f8 _________ 4d0aed _________ d0
03c9 __________ 10020 _______________0 ________ 2144c90
________ 2144c90 _________ 4f1fb7 ________ 2e909c0 _________ 437724 _____ 2d0000
000d _____ 3a00f00021 ________ 2eb6e60 ________
code:
48 8b 01 ff 50 18 84 c0 74 1a 4c 89 e9 ba 40 00
I think this is a bug in RouterOS, since routing does not work properly with the VRF. In my case it also doesn't matter if a DHCP server at the VRF interface is running.