On thing may create problem for you. You have added lan IP on an interface and not an bridge.
You are not the first and for sure 100% not the last one to make this error.
DHCP server is correctly configured on the bridge, so why did you miss the main IP?
I guess you have upgraded from an older version <6.44
You can upgrade the Splunk script to get more information. You are on 3.2, latest 4.0 found here with CAPsMan support:
http://forum.mikrotik.com/t/tool-using-splunk-to-analyse-mikrotik-logs-3-3-graphing-everything/121810/1
Also you should remove your email from the above post. Its listed under /tool e-mail
Second router config is this set correctly.
Wrong
/interface bridge port
add bridge=bridgeLAN comment=defconf interface=ether2-CAPsMAN
add bridge=bridgeLAN comment=defconf interface=ether3-LAN
add bridge=bridgeLAN comment=defconf interface=ether4
add bridge=bridgeLAN interface=wlan2GHz/ip dhcp-server
add address-pool=dhcp disabled=no interface=> bridgeLAN > lease-time=1d name=
defconf/ip address
add address=192.168.0.1/24 interface=> ether3-LAN > network=192.168.0.0
Correct
/interface bridge port
add bridge=bridgeLAN comment=defconf interface=ether2-CAPsMAN
add bridge=bridgeLAN comment=defconf interface=ether3-LAN
add bridge=bridgeLAN comment=defconf interface=ether4
add bridge=bridgeLAN interface=wlan2GHz/ip dhcp-server
add address-pool=dhcp disabled=no interface=> bridgeLAN > lease-time=1d name=
defconf/ip address
add address=192.168.0.1/24 interface=> bridgeLAN > network=192.168.0.0