To be honest the left menu makes me NUTS because the items can be in different places even on 2 identical devices. Maybe it has something to do with the order packages are installed but IPv6 and PPP seem to be the biggest offenders. Sometimes IPv6 is above IP, sometimes below and on my ccr, it’s between Tools and Radius.
Interesting, I have not seen that problem. IPv6 is in a strange position (not just below IP) but it does not vary for me.
Maybe it depends on the browser or the way the system was installed.
I am still on RC25 and read that the DHCP-Client has got script fields. Is this also available on up/down of IPv6?
The Wiki is updated with variables for DHCP-IPv6: http://wiki.mikrotik.com/index.php?title=Manual:IPv6/DHCP_Client&curid=5613&diff=29063&oldid=29062#Script
It is possible to add a script that will be executed when a prefix or an address is acquired and applied or expires and is removed using DHCP client. There are separated sets of variables that will have the value set by the client depending on prefix or address status change as the client can acquire both and each of them can have a different effect on the router configuration.
Available variables for dhcp-client
pd-valid - value - 1 or 0 - if prefix is acquired and it is applied or not
pd-prefix - value ipv6/num (ipv6 prefix with mask) - the prefix inself
na-valid - value - 1 or 0 - if address is acquired and it is applied or not
na-address - value - ipv6 address - the address
Thanks for working on the Wiki to keep it up to date and it great to use to implement/lookup things and a must read before posting in the forum.
Version 6.39rc33 has been released.
Changes since previous version:
!) winbox - minimal required version is v3.11;
*) capsman - added support for static virtual interfaces on CAP;
*) chr - fixed problem when transmit speed was reduced by interface queues;
*) defconf - fixed Groove 52 ac band settings;
*) dhcp-client - added “script” option which executes script on state changes;
*) dhcpv4-server - added “lease-hostname” script parameter;
*) dhcpv6-server - require “address-pool” to be specified;
*) export - do not show “read-only” IRQ entries;
*) gps - added “fix-quality” and “horizontal-dilution” parameters;
*) ike1 - fixed unnecessary Radius accounting requests;
*) ike1 - fixed “xauth” Radius login;
*) ike2 - update peer identity after successful EAP authentication;
*) irq - properly detect all IRQ entries;
*) log - added “gps” topic;
*) log - make SNMP logs more compact;
*) lte - buffer AT events while info command is active;
*) ppp-client - added support for Datacard 750UL and DWR-730;
*) snmp - “No Such Instance” error message is replaced with “No Such Object”;
*) snmp - fixed “/tool snmp-get” crash on session timeout;
*) snmp - fixed CAPsMAN registration table OID print;
*) snmp - fixed situation when SNMP could not read “/system health” values after reboot;
*) snmp - improved response speed when multiple requests are received within short period of time;
*) tile - added initial support for NVMe SSD disk drives;
*) tr069-client - fixed “traceroute” parameter IDs;
*) userman - show warning when no users are selected for CSV file generation;
*) winbox - added GPS menu;
*) winbox - allow to not specify certificate in IPSec peer settings;
*) winbox - allow unhide SNMP passwords;
*) winbox - do not hide “power-cycle-after” option;
*) winbox - do not show empty LTE fields in Info menu;
*) winbox - hide advertise tab in Hotspot user profile configuration if “transparent-proxy” is not enabled;
*) winbox - properly name CAP Interface on new interface creation;
*) winbox - properly show BGP communities in routing filters table filter;
*) wireless - added Egypt 5.8 country settings;
*) wireless - fixed scan tool stuck in background;
*) wireless - improved compatibility with Intel 2200BG wireless card;
*) x86 - added support for NVMe SSD disk drives;
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
capsman - added support for static virtual interfaces on CAP;
What it means?
As I understand, now you should be able to create child (virtual) interfaces under the physical interface that’s being managed by CAPsMAN. I have not tried it myself yet, though.
As I understand, now you should be able to create child (virtual) interfaces under the physical interface that’s being managed by CAPsMAN. I have not tried it myself yet, though.
That function was already
Nope. It was possible to added slave interface on CAPsMAN (controller), but you could not add slave interface locally on a CAP (managed board) itself. It appears to be possible now.
When you connect CAP to CAPsMAN virtual interface on CAP becomes disabled. I just tested it, and it works same as 6.38.1. So it’s not it, but would be awesome if it was that 
CAP supports static interfaces instead of dynamic ones, they do not disappear after reboot and count number is not changed all the time (recognised by mac-address).
So it seams you don’t have to do the copy caps setting to a new one just to set a custom name and make the cap static. nice!
Edit:
mm perhaps i didn’t understand it right
what i wrote up can already be done by adding a cap manually.
I’m still getting the same incorrect output.
Help people!
I have a script that was reading snmp individual mac address from capsman registration table. After upgrade I can not read any of them.
What is the SNMP oid to get all the wireless clients MAC on capsman (not the count)???!
I posted above (ignore the minor bug they’re working on)
/caps-man registration-table print oid reports 1.3.6.1.4.1.14988.1.1.1.4.1…
but snmpwalk shows that it is really 1.3.6.1.4.1.14988.1.1.1.5.1…
So if you walk that, you’ll see stats for all registered capsman clients, including mac address. Does that make sense?
I get the following which does not have any MAC address of the clients 
snmpwalk -c public -v 2c 192.168.10.1 1.3.6.1.4.1.14988.1.1.1.5.1
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.0.4.32.239.134.9.195 = Timeticks: (140225400) 16 days, 5:30:54.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.40.16.123.35.106.44.202 = Timeticks: (114602300) 13 days, 6:20:23.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.44.240.238.73.164.89.204 = Timeticks: (101436600) 11 days, 17:46:06.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.60.51.0.51.170.194.202 = Timeticks: (151901200) 17 days, 13:56:52.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.72.238.12.124.113.215.201 = Timeticks: (290717300) 33 days, 15:32:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.1.138.227.193 = Timeticks: (160445600) 18 days, 13:40:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.92.207.127.129.10.170.195 = Timeticks: (160445300) 18 days, 13:40:53.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.148.16.62.205.37.201.204 = Timeticks: (304600) 0:50:46.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.168.68.54.194 = Timeticks: (160439000) 18 days, 13:39:50.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.164.119.51.239.164.100.193 = Timeticks: (3174200) 8:49:02.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.168.129.149.141.101.106.195 = Timeticks: (160424800) 18 days, 13:37:28.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.1.85.60.200 = Timeticks: (26533200) 3 days, 1:42:12.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.2.156.36.201 = Timeticks: (290776200) 33 days, 15:42:42.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.3.112.103.201 = Timeticks: (290739400) 33 days, 15:36:34.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.176.197.84.5.105.150.202 = Timeticks: (131831600) 15 days, 6:11:56.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.3.238.34.128.108.26.145.206 = Timeticks: (271971200) 31 days, 11:28:32.00
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.0.4.32.239.134.9.195 = Counter32: 5821244
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.40.16.123.35.106.44.202 = Counter32: 73790913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.44.240.238.73.164.89.204 = Counter32: 14501780
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.60.51.0.51.170.194.202 = Counter32: 3251847
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.72.238.12.124.113.215.201 = Counter32: 428737
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.1.138.227.193 = Counter32: 135337
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.92.207.127.129.10.170.195 = Counter32: 480132
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.148.16.62.205.37.201.204 = Counter32: 2090
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.168.68.54.194 = Counter32: 68642196
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.164.119.51.239.164.100.193 = Counter32: 498267
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.168.129.149.141.101.106.195 = Counter32: 72654044
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.1.85.60.200 = Counter32: 47798728
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.2.156.36.201 = Counter32: 230505304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.3.112.103.201 = Counter32: 11839456
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.176.197.84.5.105.150.202 = Counter32: 11044643
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.4.238.34.128.108.26.145.206 = Counter32: 2126093
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.0.4.32.239.134.9.195 = Counter32: 1536484
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.40.16.123.35.106.44.202 = Counter32: 1608283769
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.44.240.238.73.164.89.204 = Counter32: 1464379
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.60.51.0.51.170.194.202 = Counter32: 3173338763
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.72.238.12.124.113.215.201 = Counter32: 829923
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.1.138.227.193 = Counter32: 104828
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.92.207.127.129.10.170.195 = Counter32: 511559
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.148.16.62.205.37.201.204 = Counter32: 4048
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.168.68.54.194 = Counter32: 6079397
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.164.119.51.239.164.100.193 = Counter32: 170935
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.168.129.149.141.101.106.195 = Counter32: 5243963
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.1.85.60.200 = Counter32: 1952933251
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.2.156.36.201 = Counter32: 908878507
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.3.112.103.201 = Counter32: 2161636
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.176.197.84.5.105.150.202 = Counter32: 541918651
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.5.238.34.128.108.26.145.206 = Counter32: 5897834
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.0.4.32.239.134.9.195 = Counter32: 17605
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.40.16.123.35.106.44.202 = Counter32: 1127441
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.44.240.238.73.164.89.204 = Counter32: 11616
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.60.51.0.51.170.194.202 = Counter32: 35534
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.72.238.12.124.113.215.201 = Counter32: 7080
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.1.138.227.193 = Counter32: 1268
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.92.207.127.129.10.170.195 = Counter32: 7985
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.148.16.62.205.37.201.204 = Counter32: 32
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.168.68.54.194 = Counter32: 64529
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.164.119.51.239.164.100.193 = Counter32: 1744
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.168.129.149.141.101.106.195 = Counter32: 61812
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.1.85.60.200 = Counter32: 878525
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.2.156.36.201 = Counter32: 4235450
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.3.112.103.201 = Counter32: 87886
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.176.197.84.5.105.150.202 = Counter32: 177603
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.6.238.34.128.108.26.145.206 = Counter32: 26254
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.0.4.32.239.134.9.195 = Counter32: 18520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.40.16.123.35.106.44.202 = Counter32: 1360940
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.44.240.238.73.164.89.204 = Counter32: 12007
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.60.51.0.51.170.194.202 = Counter32: 5942883
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.72.238.12.124.113.215.201 = Counter32: 8389
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.1.138.227.193 = Counter32: 1323
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.92.207.127.129.10.170.195 = Counter32: 8088
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.148.16.62.205.37.201.204 = Counter32: 48
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.168.68.54.194 = Counter32: 49427
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.164.119.51.239.164.100.193 = Counter32: 1304
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.168.129.149.141.101.106.195 = Counter32: 64913
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.1.85.60.200 = Counter32: 4306854
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.2.156.36.201 = Counter32: 9719647
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.3.112.103.201 = Counter32: 33413
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.176.197.84.5.105.150.202 = Counter32: 3597021
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.7.238.34.128.108.26.145.206 = Counter32: 81421
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.0.4.32.239.134.9.195 = Gauge32: 120000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.40.16.123.35.106.44.202 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.44.240.238.73.164.89.204 = Gauge32: 104000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.60.51.0.51.170.194.202 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.92.207.127.129.10.170.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.148.16.62.205.37.201.204 = Gauge32: 26000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.164.119.51.239.164.100.193 = Gauge32: 58500000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.2.156.36.201 = Gauge32: 57700000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.176.197.84.5.105.150.202 = Gauge32: 108000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.8.238.34.128.108.26.145.206 = Gauge32: 270000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.0.4.32.239.134.9.195 = Gauge32: 54000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.40.16.123.35.106.44.202 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.44.240.238.73.164.89.204 = Gauge32: 130000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.60.51.0.51.170.194.202 = Gauge32: 81000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.72.238.12.124.113.215.201 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.1.138.227.193 = Gauge32: 48000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.92.207.127.129.10.170.195 = Gauge32: 18000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.148.16.62.205.37.201.204 = Gauge32: 135000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.168.68.54.194 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.164.119.51.239.164.100.193 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.168.129.149.141.101.106.195 = Gauge32: 72200000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.1.85.60.200 = Gauge32: 150000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.2.156.36.201 = Gauge32: 52000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.3.112.103.201 = Gauge32: 65000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.176.197.84.5.105.150.202 = Gauge32: 27000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.9.238.34.128.108.26.145.206 = Gauge32: 243000000
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.0.4.32.239.134.9.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.40.16.123.35.106.44.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.44.240.238.73.164.89.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.60.51.0.51.170.194.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.72.238.12.124.113.215.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.1.138.227.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.92.207.127.129.10.170.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.148.16.62.205.37.201.204 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.168.68.54.194 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.164.119.51.239.164.100.193 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.168.129.149.141.101.106.195 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.1.85.60.200 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.2.156.36.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.3.112.103.201 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.176.197.84.5.105.150.202 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.10.238.34.128.108.26.145.206 = INTEGER: 0
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.0.4.32.239.134.9.195 = INTEGER: -60
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.40.16.123.35.106.44.202 = INTEGER: -39
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.44.240.238.73.164.89.204 = INTEGER: -65
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.60.51.0.51.170.194.202 = INTEGER: -49
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.72.238.12.124.113.215.201 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.1.138.227.193 = INTEGER: -69
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.92.207.127.129.10.170.195 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.148.16.62.205.37.201.204 = INTEGER: -66
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.168.68.54.194 = INTEGER: -59
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.164.119.51.239.164.100.193 = INTEGER: -41
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.168.129.149.141.101.106.195 = INTEGER: -44
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.1.85.60.200 = INTEGER: -61
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.2.156.36.201 = INTEGER: -57
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.3.112.103.201 = INTEGER: -51
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.176.197.84.5.105.150.202 = INTEGER: -55
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.11.238.34.128.108.26.145.206 = INTEGER: -62
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.0.4.32.239.134.9.195 = INTEGER: 4607184
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.40.16.123.35.106.44.202 = INTEGER: 4596448
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.44.240.238.73.164.89.204 = INTEGER: 4596072
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.60.51.0.51.170.194.202 = INTEGER: 4597208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.72.238.12.124.113.215.201 = INTEGER: 4664576
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.1.138.227.193 = INTEGER: 4602992
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.92.207.127.129.10.170.195 = INTEGER: 4600792
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.148.16.62.205.37.201.204 = INTEGER: 4596960
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.168.68.54.194 = INTEGER: 4619216
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.164.119.51.239.164.100.193 = INTEGER: 4584736
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.168.129.149.141.101.106.195 = INTEGER: 4544520
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.1.85.60.200 = INTEGER: 4601120
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.2.156.36.201 = INTEGER: 4607384
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.3.112.103.201 = INTEGER: 4664208
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.176.197.84.5.105.150.202 = INTEGER: 4538888
SNMPv2-SMI::enterprises.14988.1.1.1.5.1.12.238.34.128.108.26.145.206 = INTEGER: 4542200
looking around I see that THERE IS NO oid for MAC address as there was before! Mikrotik fixed wrong entry issue removing the MAC entry? 
/caps-man registration-table print oid
0 uptime=.1.3.6.1.4.1.14988.1.1.1.4.1.3.176.197.84.2.156.36.201 tx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.4.176.197.84.2.156.36.201 rx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.5.176.197.84.2.156.36.201
tx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.6.176.197.84.2.156.36.201 rx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.7.176.197.84.2.156.36.201 tx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.8.176.197.84.2.156.36.201
rx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.9.176.197.84.2.156.36.201 tx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.10.176.197.84.2.156.36.201 rx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.11.176.197.84.2.156.36.201
ssid=.1.3.6.1.4.1.14988.1.1.1.4.1.12.176.197.84.2.156.36.201
Well, look at that. Not only did they not fix the misprint of oid, they did in fact remove mac from the tree. I’m guessing someone just removed they wrong thing by accident. They’ll need to fix that clearly.
In the meantime, I am able to get the mac-address values in rc31 for entries there using a mikrotik script (your original issue?). For example:
foreach client in=[/caps-man registration-table find] do={put [/caps-man registration-table get $client mac-address]}
I could have sworn it was in there, but I downgraded to the last release (rc27) and still didn’t see mac listed in oid tree. So either that changed in an earlier version (perhaps unintentionally) or this just needs to be a feature request. It’s gotta be in there in the future though, right?
I do not know if there was on rc27 because I jumped to the latest (6.39rc33) from the 6.38. I hope to be fixed fast as the script I use to get mac address is a geo-location script that reports users availability on the network. fingers crossed!
Yeah, I also jumped from 6.38rc to 6.39rc, so could have been lost in an earlier version. If we both thought it was there, maybe it was? Either way, I’ve asked in my ticket they make sure to add it.
6.38.1 is a good version to downgrade and get back mac address oid. I just did it and all are back to normal