This thread is for a combined place to track changes to WMS scripts.
I’m getting ready to roll out WMS v33 to CTWUG.
The main changes here are:
- Change the
ctwugSNMP community to read-only and make it accessible from the wug. See ac113e96. - Create WMS user with public key access (only on ROS 6.31+). See a3adbc20.
The first change is just because nothing is using the existing community and I’d like to make it more usable for NMS.
The second change is a WMS user that will be used by backup but also in future in other ways to run automated scripts. This user is being setup securely. It gets a large random password (unique to each router) that is not saved. It also get’s a public key from centrifuge and in this way it will only be usable from centrifuge. This user will only be able to use SSH access. This only works from 6.31+ because that’s the ROS version that introduced the strong-crypto setting (under /ip ssh).
1 Like
This is rolling out now.
4 Likes
I just deployed v34 as WMS seems to have a problem dealing with Router OS versions where there is a space in the name.
For example: 6.39.2 (stable) was not captured by WMS properly. I’ve update it to capture it as 6.39.2.
Added another update to change script ownership to WMS.
v35 rolling out 
In the process of making the above changes I realised some of the changes I learnt that a lot of the changes are actually not compatible with older versions of RouterOS. So I had to undo most of them. So we are now at WMS v39
We have to do this first.
WMS v40
This is rolling out now.
Main change here is that I’ve added logging to nms. This means all wms managed rbs will be sending logging info to nms and this is viewable on the nms interface.
WMS v41 rolling out
Main change is to add Mumble to gametime ports (64738/tcp and 64738/udp).
1 Like
WMS v43 rolling out.
Updated IP for logging. Now logging to nms again.
For example:
https://nms.ctwug.za.net/device/device=82/tab=logs/section=syslog/
Skipped 42 (had a small bug).