The time for a workaround and rewriting all other script is too high and I am using the scheduler instead netwatch. Don't waiste time with netwatch! Here the example for our case: # check if server is up and run script :global srvstat :global srv :if ([/ping $srv count=2 size=64] = 2) do={ :global s...

I have the same issue with netwatch on v6.42.1 (current).

Not able to write global variables by netwatch up or down event and scripts will not be launched.

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS. tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2 Looks like up event is not working. Version 6.42 has this chang...

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS.

tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2
Looks like up event is not working.

To view current channel of the interface in <cap interface list, you have to enable the hidden column "current channel". The fields in column "channel" only have entries, if channel is set manually.

Big Thank to MikroTik developpers! capsman and 25 caps updated in no time and without any problems (different devicec)! Specially for the new capsman features. -extension channel auto matching-mode -possibility to specify channel list -save last channel option -background scan / rescan interval Afte...

Hi Folks I am running into the scripting file-size limitation of 4096bytes problem. On a CCR1036 with far enough power, I have several text-files with each one line of data. These are status files of remote stations. For monitoring reasons, I have a script, that consolidates all these files into one...

dude is working fine now on the new RouterOS Ver. 6.38 with server and agents.

Don't know where the problem is. We have dude currently on a CHR running on version 6.36.3. When I update routerOS and dude to 6.37, I am not able to connect to dude server anymore (client on windows is updated as well to 6.37). Of course to the new dude port 8291. Status bar in dude shows <getting ...

1. for provison also a surfix instead only prefix

---> would be great. specially if custom scan-list on provisioned interfaces could be used.


3. It would be nice to have <host names> and <IP Adress> columns in capsman registration table.

The old environment is currently still running until the new setup is working correctly. So, I can use the new version (server on a chr and agents on two arm's) for testing.

Just would like to know if anyone else is experiencing the same agent behaviour with the new dude versions?

Hi there, We currently have a older dude version running on a windows server with two agents on windows PC's (The Dude Ver.4.0 beta3). The server is on the local LAN and the two agents behind other networks. This way we can monitor devices behind those networks. Everything is working fine since we s...

If all interfaces are provisioned, the ssid is set to them by the provisioning rule automatic. Then it looks like this: Clipboard01.jpg The output then looks like this: > put message=[/caps-man interface find configuration.ssid~"c-net"] ...means, it did not find any entries, even interface...

<:put [/caps-man interface find configuration.ssid="myssid"]> only finds entries, if in the cap the ssid is set manually, but like normal the cap gets the ssid for each virtual ap by the provisioning rule (in the CAPsMAN interface list, ssid is grey not black, when set automatic). If ssid ...

The only way I could make it work, was that I made a comment to each Interface (only virtual AP's) with the actual SSID. So, then I could disable this SSID on all devices with one scheduler task. /caps-man interface disable [/caps-man interface find comment=myssid] But this should not be the solutio...

Thanks for your advice, but it doesn't work. The function is not finding any entries in configuration.ssid. I tested it like this: [admin@myrouter] > /put message=[/caps-man interface find configuration.ssid=myssid] The output line was emtpy If I just surch for any entries it looks like this: [admin...

Hi guys, We are running several cap's with CAPsMAN on a CCR1036 Router. The manager does its job pretty well and all cap's and SSID's are working fine. Now, we have a guest SSID and I want to disable this during night time. At the moment I did this by access list, where I reject clients on that SSID...

We currently have 4 new wAP ac devices running in different locations managed by CAPsMAN on a CCR1036 Router. After many tests and a lot of trouble I came to the conclusion that the wAP ac's may have huge problems on the 2.4ghz module due to the hardware design of their internal antennas. First I en...

We have several wAP ac's running in different locations. Currently only 2.4ghz module is enabled and managed by CAPsMAN. In this mode the system temperature is not higher than 46°C (room temp. around 27°C).

Hi We are using several wAP ac and other devices controlled by CAPsMAN. The setup is working just fine (most of the time). I experienced, that the wAP ac devices have some issues with certain frequencies on 2.4GHz module and all 3 chains enabled! After many tests, my results are like fallowing: CAPs...

The product is very nice, but I don't know why Mikrotik is putting that kind of default configuration where you can't connect from ethernet, same as with mAP-lite. It is frustrating trying to connect with it. A 5 sec job turns into 5 min. Not every one has in their labs laptops. So the only way for...

Hi guys!!! I have similar issues with the new <hAP ac lite> and <wAP ac> devices. 2.4 ghz: If I set up a local SSID on each AP, auto frequency seems to work fine. First it scans all channels and chooses one with lowest usage. Problems start, when I connect it to CapsMan (wireless-cm2 package). Manag...

heydude, what country setting you have specified in the CAPsMAN configuration as it selected 5740mhz as a center channel? Thanks for the tip. The country setting is really the problem. In the configuration I set it to Switzerland. So, strangely it selects 5740MHz as center channel, which is not all...

Hi, I just loaded the newest rc Release on our Test equippment (6.35rc33). -Central router (PC with x86 Router OS), acts as CAPsMAN Manager -CAP (Groove A-52HPn) controlled by CAPsMAN -Client (Groove 52HPn) set in station mode as client First I tryied to test all available frequency modes on the AP ...

Hi, I experienced the same behaviour with Groove 52HPn after testing and setting the CPU frequency to 400MHz. Device started, Link is up, but not reachable by IP. Here is what I did to solve the problem: -hold reset button before powering device on startup for 3 seconds and then release (bevore ligh...

Hey Dudes :-) We are using The Dude as a local monitoring tool for many devices and special snmp probes. It is really a great and very lean program for such a purpose. Since we started using the dude, its data base file got bigger and bigger and we experienced some missbehave of notifications and ot...