I’m in process of understanding CAPsMAN work. Since CAPsMAN v2 is the one that’s under developing (am I right? as i suspect v1 won’t be developed any more), I’ve added v2 to my test routers and try to implement what it can offer.
First of all, I would ask: am I right that there is mostly no config difference between v and v2, but just the difference in protocol? So if I read howto (oh, very few are available!) I should not care for the CAPsMAN version, the basic commands will be the same?
Second, how can I enable L2 Path MTU discovery (which is the http://wiki.mikrotik.com/wiki/Manual:CAPsMAN#CAPsMAN_v2 feature of v2) and make it work?
Third, which way can I setup auto upgrade of CAPs? I think this should be done by uploading new CAP image to folder in Files, then set this folder name in
/caps-man manager
set package-path=/pub upgrade-policy=suggest-same-version
(where /pub is the folder which contains files like routeros-mipsbe-6.29.npk)
But the question is, when the upgrade takes place (who “decide” it should be done now, which is the order of upgrade if a lot of CAPs are there), which way it’ll be done (which protocol is used, which ports etc should be open, what bandwidth it uses and may it be controlled), how the devices know who’s “on the other end” (that is, how CAP “trust” the source of image, and CAPsMAN controller know which CAP is this, via DTLS or what?). How CAP decide which image to take (can I put images for different hw platform at the same folder?).
Good example section for v2 may be very useful!
P.S. My tests given me some miraculous result: I have downgrade one device (CAP) to 6.28, another one (CAPsMAN) was at 6.29.1. Then I added CAP to CAPsMAN and got in logs:
17:59:23 caps,info [4C:5E:0C:E7:2F:4C/66/8823,IssueCert,CAP-4C5E0CE72F4C] joined, provides radio(s): 4C:5E:0C:E7:2F:51
17:59:23 caps,info [4C:5E:0C:E7:2F:4C/66/8823,Run,CAP-4C5E0CE72F4C] should auto upgrade
17:59:23 caps,info [4C:5E:0C:E7:2F:4C/66/8823,Run,CAP-4C5E0CE72F4C] ask to upgrade, version 6.29.1
17:59:49 caps,info [4C:5E:0C:E7:2F:4C/66/8823,Run,CAP-4C5E0CE72F4C] upgrade status: rebooting, disconnect
18:00:24 caps,info [4C:5E:0C:E7:2F:4C/66/90b,Join,CAP-4C5E0CE72F4C] joined, provides radio(s): 4C:5E:0C:E7:2F:51
so the upgrade took place! What I wasn’t able to understand at all is how the wireless-cm2-6.28-mipsbe.npk which was on CAP upgraded to wireless-cm2-6.29.1-mipsbe.npk? To be honest, I’ve put both routeros-mipsbe-6.29.1.npk and wireless-cm2-6.29.1-mipsbe.npk to the same folder on CAPsMAN router, but I see no trace of such upgrade in the log, so I think it tried to download it from the Internet, or not?
I ask sinc now the CAP is in Internet-enable VLAN, but as I finish my tests it goes to VLAN without any external traffic, so “from the www” upgrade be available. Please advice!