Change Routeros Software Identity
The most typical software used is a Mikrotik’s own Winbox client. It has a user friendly window- based interface. The software is available for Windows users by default. It can be acquired from mt. Arsip Software MikroTik RouterOS. Tweet: Pilihlah file yang akan di download: Nama File: Ukuran: Download: all MikroTik RouterOS Training Class.
3118 new words, 3118 deleted words, 47% change. × MD5 routeros-mmips- 6.42rc24. × MD5 routeros-mmips- 6.41.2.npk. Ca1150 MD5 routeros-x86-6.41.2.npk.
E5 MD5 routeros-smips-6.41.2.npk. E3478 MD5 routeros-arm-6.41.2.npk. 764b MD5 routeros-tile-6.41.2.npk.
4dcb MD5 routeros-arm-6.41.2.npk. E5 MD5 all packages-smips-6.41.2.zip. MD5 all packages-tile-6.41.2.zip. MD5 all packages-mipsbe-6.41.2.zip.
MD5 all packages-mmips-6.41.2.zip. × MD5 routeros-mmips. Ca1150 MD5 routeros-x86-6.41.2.npk.
Routeros Vs Pfsense
E5 MD5 routeros-smips-6.41.2.npk. E3478 MD5 routeros-arm-6.41.2.npk. 764b MD5 routeros-tile-6.41.2.npk. MD5 all packages-mipsbe-6.41.2.zip. MD5 all packages-mmips-6.41.2.zip.
MD5 all packages-smips- 6.41.2.zip: c9c7c613 db 71 a 54c72aeef03210c879 b. SHA256 all packages-smips- 6.41.2.zip: ada48a1d 6 eacbda7020fee 2 ed3a 7 ef0693 b 6bf04654cf. × MD5 routeros-mmips- 6.42rc24. × MD5 routeros-mmips- 6.41.2.npk. 4dcb MD5 routeros-arm-6.41.2.npk.
E5 MD5 all packages-smips-6.41.2.zip. MD5 all packages-tile-6.41.2.zip. MD5 all packages-ppc- 6.41.2.zip: 339 db 966 a 839912a33 b 9e2e. Aa24a736 SHA256 all packages-ppc- 6.41.2.zip: fd37b7dca 6 bd15d 2 ab1ebaafaee 7 a1a13a589 b 5dcb7ec. Ac7d3 MD5 all packages-mipsbe-6.41.2.zip: 18ed2760aba4fef1 d 2534f7ff542aaed.
2511 new words, 2483 deleted words, 40% change. × MD5 routeros-arm-6.42rc24. 4ae MD5 routeros-mmips-6.42rc24. 43c MD5 routeros-x86-6.42rc24. 4ae MD5 routeros-smips-6.42rc24. Dff2 MD5 routeros-arm-6.42rc24.
F85 MD5 routeros-tile-6.42rc24. MD5 all packages-tile-6.42rc24. MD5 all packages-mmips-6.42rc24. MD5 all packages-smips-6.42rc24. MD5 all packages-x86-6.42rc24. 2e MD5 allpackages-tile-6.42.
43c MD5 routeros-x86-6.42rc24. 4ae MD5 routeros-smips-6.42rc24. Dff2 MD5 routeros-arm-6.42rc24. F85 MD5 routeros-tile-6.42rc24. MD5 all packages-tile-6.42rc24.
MD5 all packages-mmips-6.42rc24. MD5 all packages-smips-6.42rc24. MD5 all packages-x86-6.42rc24. Netinstall-6.42rc24- ppc.zip: ccead.
Routeros Ipv6
Netinstall-6.42rc24- ppc.zip: 0. Netinstall-6.42rc24- mmips.zip: ccead. × MD5 routeros-arm-6.42rc24. 4ae MD5 routeros-mmips-6.42rc24. 2e MD5 allpackages-tile-6.42. 63487c MD5 mikrotik-6.42rc24.
Netinstall-6.42rc24- mmips.zip: ccead. Netinstall-6.42rc24- mmips.zip: 0. Netinstall-6.42rc24- arm.zip: ccead. Netinstall-6.42rc24- arm.zip: 0. 5 netinstall-6.42rc 24-ppc.zip: ccead. 256 netinstall-6.42rc 24-ppc.zip: 0. Netinstall-6.42rc24- tile.zip: ccead.
497 new words, 508 deleted words, 9% change. 6.41.2.zip: 26fc218ccf12cca 339db966a. 9e2e 3 f8eb879 aa24 a 8c495f18 736 SHA256 all.
6.41.2.zip: 9 fd 0f569dd. D4bfd686011145 37 b 19a864 7dca6bd15 d 59e238 2ab1ebaafaee7 a 0bacaa 1a13a589b5dcb 7 c0fdc396b49273e65 ec9263ac7d3 MD5 all. 6.41.2.zip: 11bcf ff48bdebfb 1 c8a4 f94654f1 cd 7842a64c. A64f6 692fe50e269 SHA256 all. 6.41.2.zip: 6f409409ef2b4007 095 e7b 8cc2c7fda7 145aa4447aaf358 e 7eea13 730f1ecabd0f541. 6.41.2.zip: 339db966a.
9e2e 3 aa24 a 736 SHA256 all. Fd 37 b 7dca6bd15 d 2ab1ebaafaee7 a 1a13a589b5dcb 7 ec9263ac7d3 MD5 all.
6.41.2.zip: ff48bdebfb 1 f94654f1 cd 692fe50e269 SHA256 all. 6.41.2.zip: 095 e7b 145aa4447aaf358 e 730f1ecabd0f541 e 6fe58 e 6f2aed131 b 8be205ba4c MD5 all. 86-6.41.2.zip: 14 a 72dbce485 f 6d341e11 b 981857 c 6de SHA256 all. A 62243cfa348 f 1b6fddbb92ad2166 c 053bd803c. 6.41.2.zip: 26fc218ccf12cca 3 f8eb879 a 8c495f18 SHA256 all. 6.41.2.zip: 9 fd 0f569dd.
D4bfd686011145 b 19a864 d 59e238 a 0bacaa 7 c0fdc396b49273e65 MD5 all. 6.41.2.zip: 11bcf 1 c8a4 cd 7842a64c. A64f6 SHA256 all.
6.41.2.zip: 6f409409ef2b4007 e7b 8cc2c7fda7 e 7eea13 e 7cb8b3730 e 3a3 b 32d MD5 all. 86-6.41.2.zip: d12 a 13547283fe89 f 0ee0 b 59603ca83 c. 86-6.41.2.zip: ae5c9cce339526 a 35a4e5 f 317 c 707e9f7553f2. 3250 new words, 3848 deleted words, 51% change. × MD5 routeros-arm-6.42rc24. F85 MD5 routeros-x86-6.42rc24.
4ae MD5 routeros-mmips-6.42rc24. 43c MD5 routeros-smips-6.42rc24. Cfbf0 MD5 routeros-arm- allpackages-mmips- 6.42rc24. Npk zip: 078d6ece0879cef68 76 c 881eaec34d1832 9affcfc43480596bbabd95f836eaa SHA256 routeros-arm- allpackages-mmips- 6.42rc24.
Npk zip: da0607cc2062 11ff934c. D4c4 f 6fc9ab16 80 d 423b0c7bcc 5eab 2b39ea.
× MD5 routeros-arm-6.42rc24. F85 MD5 routeros-x86-6.42rc24. 4ae MD5 routeros-mmips-6.42rc24. 43c MD5 routeros-smips-6.42rc24. Cfbf0 MD5 allpackages-mmips- 6.42rc24. Zip: 76 c 9affcfc43480596bbabd95f836eaa SHA256 allpackages-mmips- 6.42rc24.
Zip: 11ff934c. D4c4 f 80 d 423b0c7bcc 5eab 5 a 90cb MD5 allpackages-x86-6.42 rc24. Zip: b 2e 8 c64dc697bbd 0 b7acda SHA256 allpackages-x86-6.42 rc24. Cfbf0 MD5 routeros-arm- 6.42rc24. Npk: 078d6ece0879cef68 c 881eaec34d1832 SHA256 routeros-arm- 6.42rc24. Npk: da0607cc2062 f 6fc9ab16 d. E859890bbe6 a 0b353b.
Fc2f85 MD5 routeros-mmips-6.42 rc24. Npk: 67470d7d4bafc0 b. 08aa92aa SHA256 routeros-mmips-6.42 rc24.
Npk: 128 f 45974a57dd10017 d 3210cb508f44cb 81. F 5 e 4047bf237b 9. 24.npk: 9 c5546f2. F2fc9 a 640e SHA256. 4caf15c 2f 3372cba1771b. 2203 new words, 2006 deleted words, 33% change.
× MD5 routeros-mmips-6.42 routeros-x86-6.42 rc 20 24.npk: f e 4 ce929ce6c884452 bdc1218ec80113b54 d 8855 0448f2dc68b3 SHA256 routeros-mmips-6.42 routeros-x86-6.42 rc 20 24.npk: 89758cccfef. Ebe55734eaaf3 a482988f62. Cb672f7 d 0a 70d 2 a5364 cd6ded1c4 ae 328049 MD5 routeros-mipsbe- routeros-smips- 6.42rc 20 24.npk: 20 1cba32 a 653002718a8a456a6a 7 SHA256 routeros-mipsbe-6.42.
98ad5a cc906cb560cc. × MD5 routeros-x86-6.42 rc 24.npk: e 4 bdc1218ec80113b54 d 0448f2dc68b3 SHA256 routeros-x86-6.42 rc 24.npk: a482988f62. Cb672f7 d 70d 2 cd6ded1c4 ae.
MD5 routeros-smips- 6.42rc 24.npk: 1cba32 a. 7 cc906cb560cc 0. B 09fc8 c 8770 SHA256 routeros-smips-6.42rc 24.npk: 042ea43f. B82592ee95 e 02ab98956bd4a 6 a4170ec62b7467db6226 c 05 d 02dff2 MD5 routeros-tile-6.42rc 24.npk: 673cc45c. Bb7d573816 SHA256 routeros-tile-6.42rc 24.npk.
× MD5 routeros-mmips-6.42 rc 20.npk: f 4 ce929ce6c884452 d 8855 SHA256 routeros-mmips-6.42 rc 20.npk: 89758cccfef. Ebe55734eaaf3 d 0a 2 a5364 ae 328049 MD5 routeros-mipsbe- 6.42rc 20.npk: 20 a 653002718a8a456a6a 7 SHA256 routeros-mipsbe-6.42.
98ad5a 0 MD5 routeros-smips-6.42.: 936f7317 b 62bac587a3 c 66ad4b24d586 SHA256 routeros-smips-6.42rc 20.npk: 4611c1cf. Fe9bddca757217 e 9ca1584830dc 6. Link to this change log Changes to the page www.mikrotik.com/download are logged on this page as they are detected.
You can link to this log by pasting the HTML below into your page. It produces a link which looks like this: change log log in.
Contents. Overview Controlled Access Point system Manager (CAPsMAN) allows centralization of wireless network management and if necessary, data processing. When using the CAPsMAN feature, the network will consist of a number of 'Controlled Access Points' (CAP) that provide wireless connectivity and a 'system Manager' (CAPsMAN) that manages the configuration of the APs, it also takes care of client authentication and optionally, data forwarding. When a CAP is controlled by CAPsMAN it only requires the minimum configuration required to allow it to establish connection with CAPsMAN. Functions that were conventionally executed by an AP (like access control, client authentication) are now executed by CAPsMAN. The CAP device now only has to provide the wireless link layer encryption/decryption.
Depending on configuration, data is either forwarded to CAPsMAN for centralized processing ( default) or forwarded locally at the CAP itself. CAPsMAN features. RADIUS MAC authentication. WPA/WPA2 security. TBA MISSING CAPsMAN features. Nstreme AP support.
Nv2 AP support. TBA CAPsMAN v2 NOTE: CAPsMAN v2 is NOT compatible with current CAPsMAN v1 (CAPsMAN v1 CAP devices will not be able to connect to CAPsMAN v2 and CAPsMAN v2 CAP devices will not be able to connect to CAPsMAN v1).
It means that both CAPsMAN and CAP devices should have wireless-cm2 package enabled/installed in order to make CAPsMAN v2 system to work. If you want to try out the CAPsMAN v2 upgrade all the CAPs and the CAPsMAN to latest RouterOS version and enable/install wireless-cm2 package. CAPsMAN v2 features:. CAPsMAN automatic upgrade of all CAP clients (configurable).
improved CAPCAPsMAN data connection protocol. added 'Name Format' and 'Name Prefix' setting for Provision rules. improved logging entries when client roams between the CAPs.
added L2 Path MTU discovery Upgrade options from v1 to v2: Option1: Install a new temporary CAPsMAN v2 router in same network where the current CAPsMAN router is and start enabling/upgrading wireless-cm2 package on the CAPs. All CAPs with the v2 will connect to the new temporary CAPsMAN v2 router. After every CAP is upgraded to v2, upgrade your current CAPsMAN to v2 and then turn off the temporary CAPsMAN v2 router. Option2: Upgrade your CAPs and then CAPsMAN to v2 at the same time. In this case you could have little more downtime unless you schedule all the CAPs to reboot/install at the same time. Requirements CAPsMAN works on any RouterOS device from v6.11, wireless interfaces are not required (since it manages the wireless interfaces of CAPs) CAPsMAN v2 is working starting from RouterOS v6.22rc7. CAP device should have at least Level4 RouterOS license Limitations unlimited CAPs (access points) supported by CAPsMAN 32 Radios per CAP 32 Virtual interfaces per master radio interface CAP to CAPsMAN Connection For the CAPsMAN system to function and provide wireless connectivity, a CAP must establish management connection with CAPsMAN.
A management connection can be established using MAC or IP layer protocols and is secured using 'DTLS'. A CAP can also pass the client data connection to the Manager, but the data connection is not secured. If this is deemed necessary, then other means of data security needs to be used, e.g. IPSec or encrypted tunnels. CAP to CAPsMAN connection can be established using 2 transport protocols (via Layer 2 and Layer3). MAC layer connection features:. no IP configuration necessary on CAP.
CAP and CAPsMAN must be on the same Layer 2 segment - either physical or virtual (by means of L2 tunnels). IP layer (UDP) connection features:. can traverse NAT if necessary. CAP must be able to reach CAPsMAN using IP protocol. if the CAP is not on the same L2 segment as CAPsMAN, it must be provisioned with the CAPsMAN IP address, because IP multicast based discovery does not work over Layer3 In order to establish connection with CAPsMAN, CAP executes a discovery process. During discovery, CAP attempts to contact CAPsMAN and builds an available CAPsMANs list.
CAP attempts to contact to an available CAPsMAN using:. configured list of Manager IP addresses. list of CAPsMAN IP addresses obtained from DHCP server. broadcasting on configured interfaces using both - IP and MAC layer protocols. When the list of available CAPsMANs is built, CAP selects a CAPsMAN based on the following rules:. if caps-man-names parameter specifies allowed manager names ( /system identity of CAPsMAN), CAP will prefer the CAPsMAN that is earlier in the list, if list is empty it will connect to any available Manager.
suitable Manager with MAC layer connectivity is preferred to Manager with IP connectivity After Manager is selected, CAP attempts to establish DTLS connection. There are the following authentication modes possible:. no certificates on CAP and CAPsMAN - no authentication.
only Manager is configured with certificate - CAP checks CAPsMAN certificate, but does not fail if it does not have appropriate trusted CA certificate, CAPsMAN must be configured with require-peer-certificate=no in order to establish connection with CAP that does not possess certificate. CAP and CAPsMAN are configured with certificates - mutual authentication After DTLS connection is established, CAP can optionally check CommonName field of certificate provided by CAPsMAN. Caps-man-certificate-common-names parameter contains list of allowed CommonName values. If this list is not empty, CAPsMAN must be configured with certificate. If this list is empty, CAP does not check CommonName field.
If the CAPsMAN or CAP gets disconnected from the network, the loss of connection between CAP and CAPsMAN will be detected in approximately 10-20 seconds. CAP Auto Locking to CAPsMAN CAP can be configured to automatically lock to particular CAPsMAN. Locking is implemented by recording certificate CommonName of CAPsMAN that CAP is locked to and checking this CommonName for all subsequent connections. As this feature is implemented using certificate CommonName, use of certificates is mandatory for locking to work. Locking is enabled by the following command: admin@CAP /interface wireless cap set lock-to-caps-man=yes Once CAP connects to suitable CAPsMAN and locks to it, it is reflected like this: admin@wtp /interface wireless cap print.
Locked-caps-man-common-name: CAPsMAN-000C424C30F3 From now on CAP will only connect to CAPsMAN with this CommonName, until locking requirement is cleared, by setting lock-to-caps-man=no. This approach needs to be used if it is necessary to force CAP to lock to another CAPsMAN - by at first setting lock-to-caps-man=no followed by lock-to-caps-man=yes. Note that CAP can be manually 'locked' to CAPsMAN by setting caps-man-certificate-common-names. Auto Certificates To simplify CAPsMAN and CAP configuration when certificates are required (e.g. For automatic locking feature), CAPsMAN can be configured to generate necessary certificates automatically and CAP can be configured to request certificate from CAPsMAN. Automatic certificates do not provide full public key infrastructure and are provided for simple setups. If more complicated PKI is necessary - supporting proper certificate validity periods, multiple-level CA certificates, certificate renewal - other means must be used, such as manual certificate distribution or SCEP.
CAPsMAN has the following certificate settings:. certificate - this is CAPsMAN certificate, private key must be available for this certificate.
If set to none, CAPsMAN will operate in no-certificate mode and none of certificate requiring features will work. If set to auto, CAPsMAN will attempt to issue certificate to itself using CA certificate (see ca-certificate description). Note that CommonName automatically issued certificate will be 'CAPsMAN-' and validity period for will be the same as for CA certificate. ca-certificate - this is CA certificate that CAPsMAN will use when issuing certificate for itself if necessary (see certificate description) and when signing certificate requests from CAPs. If set to none, CAPsMAN will not be able to issue certificate to itself or sign certificate requests from CAPs.
If set to auto, CAPsMAN will generate self-signed CA certificate to use as CA certificate. CommonName for this certificate will take form 'CAPsMAN-CA-' and validity period will be from jan/01/1970 until jan/18/2038. Note: The CAP wireless interfaces that are managed by CAPsMAN and whose traffic is being forwarded to CAPsMAN (ie. They are not in local forwarding mode), are shown as disabled, with the note Managed by CAPsMAN. Those interfaces that are in local forwarding mode (traffic is locally managed by CAP, and only management is done by CAPsMAN) are not shown disabled, but the note Managed by CAPsMAN is shown CAP behaviour of AP is configured in /interface wireless cap menu. Note: If no rule matches radio, then implicit default rule with action create-enabled and no configurations set is executed.