CAPsMAN evolved - central AP management for WiFi6

Поделиться
HTML-код
  • Опубликовано: 2 ноя 2024

Комментарии • 107

  • @JCJADIN
    @JCJADIN 11 месяцев назад +9

    wished I had this video a few weeks ago, extremely informative ! thanks a lot for clear and simple explanations. As suggested already in previous comments we'll now be waiting for part 2 with vlans.

  • @XxSpYxX
    @XxSpYxX 11 месяцев назад +2

    This is the topic I've been waiting for. I've been struggling with this setup for a while now. Hopefully I can take some points and apply them over the next days.

    • @XxSpYxX
      @XxSpYxX 11 месяцев назад

      And I've successfully setup my stuff! Things I learned along the way.
      No connection to capsman is displayed for some reason on the cap wifi - I forgot to set the country in the profile and setting it fixed that!
      Set the correct bridge on the caps!
      Use the provision button! I did not know about provisioning!
      For VLAN management I set the provisioning to static - and on the cap there is in [Wireless -> CAP -> Slave Static] so I can name the interfaces and assign the correct VLANs on the bridge.
      As explained in the roaming video I've enabled FT and FT (DS) in the security profile. I've tested a couple of android phones and they are roaming. Roaming is also displayed in the logs.

  • @MustaMT
    @MustaMT 11 месяцев назад +6

    The video and upgrade I have been waiting for, for so long 😁 thank you!
    I can see great work being done on the wireless packages! Keep it up 👍

  • @hexatested
    @hexatested 11 месяцев назад +8

    Thank you Mikrotik. Please add chapters to this video. ❤

  • @kwinsch7423
    @kwinsch7423 5 месяцев назад +1

    Excellent. Please assign TOMS to more WiFi topics. Extending the topic to configuration with multiple VLANS and corresponding SSID's, including reference to his fast roaming video would be the logical next step.

  • @VoklavTube
    @VoklavTube 11 месяцев назад +5

    All this hype and the last minutes hit you hard...

  • @Ebakoba
    @Ebakoba 11 месяцев назад +6

    Please explain the black magic of datapaths. What are they? How to configure them? Etc. made huge mistake by going with 3 ax devices for my country house- cannot configure them to use a VLAN through WiFi to save my life.

  • @sashadimitr2852
    @sashadimitr2852 8 месяцев назад +2

    And how do you provision Virtual APs on 30+ physical units with Capsman? Nohow. Manually need go form one to another and create them.

  • @psycho160
    @psycho160 11 месяцев назад +1

    Thank you. I can finally buy a wifi6 CAP

  • @Saeglopur89
    @Saeglopur89 11 месяцев назад

    Quality of production and how clear is voice - perfect!
    Thank you! I've commented few times months ago and you made it literally perfect now :)

  • @Cheebful
    @Cheebful 11 месяцев назад +3

    Most complicated WiFi network configuration besides all vendors, great job Mikrotik)

  • @elijahzeida5030
    @elijahzeida5030 11 месяцев назад +2

    Thank you! You make my dreams come true!

  • @peterkovacs233
    @peterkovacs233 8 месяцев назад +2

    Why there is no option to set datapath as local-forwarding like in old versions, for adding the wifi interfaces as a dynamic bridge port via CAPsMAN datapath? In CAPsMAN datapath it shows the manager's bridges which absolutely useless in this scope..

    • @udenspasaule
      @udenspasaule 7 месяцев назад

      All you find workaround?

  • @dejanslo
    @dejanslo Месяц назад +1

    can someone, please, guide me through steps mentioned in 8:18-8:30? I get my cAP running, but I cant seem to manage to get an IOT network to a different bridge. I had everythinng set-up until now with the old capsman, now an ax lite joined the network.

  • @ForesthusForesthus
    @ForesthusForesthus 22 дня назад

    really cool video. it helped a lot to understand. thnx

  • @TheGhostLV
    @TheGhostLV 11 месяцев назад

    Any milestones to combine old AC APs into new capsman? I see that there is good feature FT and roaming works great on AX.

  • @arty158
    @arty158 7 месяцев назад +1

    Hi, new capsman with driver wifi-qcom-ac datapath doesn't work. Can you fix it asap?

  • @madmuchoCZ
    @madmuchoCZ 11 месяцев назад +13

    Please add back central forwarding to new capsman.

    • @stephanszarafinski9001
      @stephanszarafinski9001 11 месяцев назад

      Yes we really need that for better security on the network!

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад

      @@stephanszarafinski9001 I didn't find the performance hit worth it. The router or caps-man ager CPU would really get taxed. The slow radios got slower...
      And it made it that much harder to replace Mikrotik radios later. If you used local forwarding... It was simple.

    • @shaunclarke94
      @shaunclarke94 8 месяцев назад

      @@stephanszarafinski9001 how does it improve security? I don't get this one...

  • @zeratoss5008
    @zeratoss5008 6 месяцев назад

    Hi MikroTik,
    How can I know (or check) which MikroTik AP or hAP support FT (Roaming) 802.11r?
    Thank you in advanced for your answer!

  • @udenspasaule
    @udenspasaule 7 месяцев назад

    Hi, CAPSMAN not add interfaces to the bridge?
    All wifi networks keep geting swich port brige only.
    How to make 2 caps men wlans and 2 briges?

  • @wint3rmut3
    @wint3rmut3 8 месяцев назад

    Thank you so much for this video and wifiwave2 update. I've updated hap ac2 and hap ac3 routers, and results are astonishing. I will really appreciate if you provide a guide for the proper setup of several Audience devices with wifi-qcom-ac package on board.

  • @Lennypl1
    @Lennypl1 11 месяцев назад

    Hi there is possibility atatch bridge from capsman manager device not from local Bridge on local CAP interface ?

  • @donorbin6990
    @donorbin6990 9 месяцев назад

    Great video, Toms... explained a lot to me and where the missing packages went. lol
    HOWEVER, I am battling to see where SSID is set for CAPsMAN . My local (on the hap-AX3) wifi interfaces show "managed by CAPsMAN" which is running on the same hap-AX3... but I do not see a SSID to connect to.

    • @donorbin6990
      @donorbin6990 9 месяцев назад

      Additionally - beneath "managed by CAPSMAN", there is no channel/freq info - as I am used to seeing on my previous config. Makes me think I am missing something on the configurations. I previously set this under "CAP Interface" on the CAPsMAN menu (gui).

  • @prmfeddema
    @prmfeddema 11 месяцев назад +1

    Thanks Toms - very helpful video. Here is another question: i saw you putting in 3 frequencies for the wifi config - my questions: a) what is a correct frequency strategy when using multiple accesspoints in 1 house? b) why did you put in 3 frequencies in 1 config? If you have 3 ap's in the house - how do you avoid the access points using the same frequency. In my case i created 3 different configs - each having it's own frequency but this feels somehow wrong. Any advise that you give here?

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад +1

      It looked like he gave caps-man the ability to pick between channels 1,6,11 in 2.4

    • @prmfeddema
      @prmfeddema 11 месяцев назад

      @@ChrisNicholson Yes - but the question now is: which one is being selected by the AP? Is this random or is there some kind of logic behind? And if you have more than 1 CAP - is there any (automatic?) logic in offering the various channels. Reason for asking is that ended up with the same channel being selected in multiple AP's - resulting in interference - resulting in bad connections. Would love to see a guide on how to do this (note that this should be common work practices when deploying this in offices..)

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад +1

      @@prmfeddema it used to pick at boot time. No rescan frequency at all.
      As I stated... After the serious financial losses from Caps-Man 1... I am not gonna be putting anything on the bench from Mikrotik wireless for a while.

  • @DeLcHa37105
    @DeLcHa37105 9 месяцев назад +1

    I have an issue where all my cap interfaces are visible and broadcasting however it seems that the bridge and Dhcp pool do not work.

    • @udenspasaule
      @udenspasaule 7 месяцев назад +1

      same., Do you find workaround?

  • @ManiaciiBlink
    @ManiaciiBlink 9 месяцев назад

    From the AX router where the Capsman is enabled, to I need to also enabled CAP on that router?

  • @stephanszarafinski9001
    @stephanszarafinski9001 11 месяцев назад

    Great video! Thanks for making it possible to run both versions of capsman on the same router! Sidenote, I think some people would like to know that you can add a vlanid to the datapath of the central configuration. That is added to traffic on the bridge that is set on the local datapath.

  • @georgesdibeh7826
    @georgesdibeh7826 9 месяцев назад

    Hello
    I updated my hap ac3 and cap c to 7.13
    And added the wifi qcom ac package
    After i set up capsman
    It turns out that the capsman wireless ports work only on local manager even if it connected to capsman
    And the other cap has no status information in wifi interface MB but its there and running but no tx rx info
    How do i solvd this

  • @aseimel
    @aseimel 5 месяцев назад

    I have to admit I thinks this makes things more confusing I have CCr2004 pcie card running router os 7.8 but I still only get the old menu. Is that because it does not have wifi interfaces itself? I would still like to use it for central management

  • @johnr9243
    @johnr9243 11 месяцев назад +1

    hey I have ax3 and ax2 and trying to connect them with caps man but I am failing to assign the vlan ids for main and IoT 😢 lans, so the question is how it should be done as datapath is not working for me

    • @udenspasaule
      @udenspasaule 7 месяцев назад

      All you find workaround?

  • @wreckedzilla
    @wreckedzilla 11 месяцев назад +2

    cool, would be great to get rid of slave,master naming. :D
    if capsman goes down, still the APs go down too? no forwarding without the boss?

  • @MustaMT
    @MustaMT 11 месяцев назад

    I have a second comment.. the decision of splitting the packages is to mainly allow further development of future products.
    Could you give me hints of those future products? I promise I won’t tell anyone 🤫😁

  • @sirius6beta
    @sirius6beta 11 месяцев назад +1

    Finally 🙏 after being through hell and back

  • @marine1718
    @marine1718 7 месяцев назад

    when will be available capsman for mesh devices? i would love to add devices without cable

  • @pedromartinezdeaguilar9187
    @pedromartinezdeaguilar9187 11 месяцев назад

    Very good video, thanks

  • @MarcelGavalier
    @MarcelGavalier 5 месяцев назад

    Anybody who can help with Access list? I m struggling on new Capsman on WIFI(2) version... old capsman was sharpt new does not works how i think they have...

  • @michalpavlikpb
    @michalpavlikpb 11 месяцев назад +2

    Do WiFiWave2 package for older devices (CAP AC for example) witch have driver support ... pls .. Thx ..

    • @xgamer
      @xgamer 11 месяцев назад

      no they don't support devices with 16MB flash
      even the cap ac XL witch was releases after the creation of their wave2 package is not compatible.

    • @michalpavlikpb
      @michalpavlikpb 11 месяцев назад

      @@xgamer i know ..but .. some new package ?? or ...

    • @michalpavlikpb
      @michalpavlikpb 11 месяцев назад

      @@pavelbartek8784 Oh man .. looks good .. - Diki moc za info

    • @Rob_Turner_UK
      @Rob_Turner_UK 11 месяцев назад

      two winbox places for capsman 😂

  • @ChrisNicholson
    @ChrisNicholson 11 месяцев назад +3

    No 4x4 radios. No 6E or 7. No Outdoor Radios. No radios with more than a 1Gig LAN port...
    Gonna wait this one out.

  • @enlace101
    @enlace101 10 месяцев назад

    Excelente video, sería muy conveniente poder tenerlo en español. (sé que es posible traducir los subtítulos, pero créeme no es lo mismo)

  • @nikolashuminosky6987
    @nikolashuminosky6987 3 месяца назад

    be honest, the new CAPsMAN, the lease we use the better will be!!!

  • @Coldphoenix44
    @Coldphoenix44 6 месяцев назад

    I am sorry but it when i do what they did in the video exactly i get no connection to CapsMan message, i did not have problem with the old wifi APs.

    • @XtrAMassivE
      @XtrAMassivE 6 месяцев назад

      Yes I had the same issue. The solution was to go to the Radios tab and manually provisioning it there, it won't be done automatically because of some limitations.

  • @edieryovannycarvajalsepulv6789
    @edieryovannycarvajalsepulv6789 4 месяца назад

    Puedo bajar de la versión 7.8 a la versión 6 de un cAP xl

  • @smilelove757
    @smilelove757 4 месяца назад

    i tried enverything and it sayw no connection to capsman

  • @aphroti
    @aphroti 11 месяцев назад

    is it necessary to connect CAPs directly to CAPsMAN device or as long as in the same network is ok

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад +1

      Even across the interwebz... As long as the 2 can talk to each other via either broadcast, forwarding, VPN, etc.

    • @aphroti
      @aphroti 11 месяцев назад

      @@ChrisNicholson That's what i thought🤔, but it's just not working for me right now, will do more tests, thanks

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад

      @@aphroti Firewall rules can be the issue locally. But you can tell a cap WHERE TO FIND the manager. So if you are not on the same layer2... That can get you connected.

  • @materangics6984
    @materangics6984 10 месяцев назад +1

    This is a very brief, messy explanation, you should focus much more on settings, e.g. using internal radio managed by capspman, what is a known issue. Also provisioning older cAP, eg. wAP or cAP is not possible at the moment based on the description, neither documentation exist.

  • @muradmondol4247
    @muradmondol4247 5 месяцев назад

    How to control more access point cap ax

  • @dvreshta
    @dvreshta 11 месяцев назад

    Well Done

  • @jonathancolby9179
    @jonathancolby9179 5 месяцев назад

    Please add NV2 to capsman. I run many deployments of moving vehicles using NV2 clients.

  • @Big_George
    @Big_George 7 дней назад

    Жодного слова про те, як на самій CAP-ax, без іншого роутера включити caps контролер. а все тому, що він не включається, ніяк ((

  • @GreDi_PL
    @GreDi_PL 11 месяцев назад

    I have a RB4011iGS+RM with RouterOS v7.12 (latest stable version currently available) and there is no WiFi button at Webfig. Why are you not consistent? :/

    • @mikrotik
      @mikrotik  11 месяцев назад +3

      Starting v7.13 we are renaming Wifiwave2 to just WiFi

    • @jurgen824
      @jurgen824 11 месяцев назад

      The RB4011iGS+RM is the rackmount version without any wireless (only 10x Gigabit Ethernet interfaces), so would make sense that it has no WiFi button. Or did you perhaps mean to say that you have the RB4011iGS+5HacQ2HnD-IN model (which does have built-in WiFi as well)?

    • @GreDi_PL
      @GreDi_PL 11 месяцев назад

      @@jurgen824 It's true of the RB4011iGS+RM that there are no WiFi interfaces, which means that when I click on the WiFi button (which Mikrotik claims will appear from v7.13), I will have an empty list. But it's not the WiFi local interfaces that are the issue, it's the virtual interfaces. I don't need to have WiFi interfaces locally to run the CAPsMAN server.
      See ruclips.net/video/37aff6d14Xk/видео.htmlsi=znPOwHlbgOLmQ2hx&t=491 Only two are of all are local WiFi interfaces. BR.

    • @jurgen824
      @jurgen824 11 месяцев назад

      @@GreDi_PL Ah ok, misunderstood you initially, thanks for the clarification! :)

  • @PetrKrenzelok
    @PetrKrenzelok 10 месяцев назад +1

    The decision of reshuffling the menus for 7.13. went a wrong way imo 😕 1) I don't like the Wifi menu item name. It should stay with more generous / nicer Wireless one and Wifi should be used for legacy stuff imo 2) Moving CAPsman into one of millions Wifi's tabs, plus having a CAP button on one of the other tab suggests, that CAPsman should have stayed in the root menu and never be integrated into a Wifi UI, which is already crowded with lot's of tabs / options. So - for me, the UI/UX decisions are kind of a step backwards ...

    • @mikrotik
      @mikrotik  10 месяцев назад +2

      There are many wireless technologies now, LoRA, LTE, 60GHz, Bluetooth. WIFI is more accurate

    • @shaunclarke94
      @shaunclarke94 8 месяцев назад

      The reason the CAPsman stuff was moved into the Wifi menu is because most of the settings apply to interfaces and CAPsman so now things aren't needlessly duplicated. Same config can be used locally or for CAPsman etc.

  • @XtrAMassivE
    @XtrAMassivE 6 месяцев назад +1

    It's worth mentioning that if you want to manage local wifi (like on ax2) it won't connect to capsman automatically. You need to provision it manually. You can do it by going to the "Radios" tab and selecting the interface and then pressing "Provision". Otherwise it just says that it can't connect to capsman. Sadly not the most intuitive video.

  • @deepspacecow2644
    @deepspacecow2644 11 месяцев назад

    I have that same laptop

  • @xgamer
    @xgamer 11 месяцев назад +15

    My god, what a piece of crap.
    Now I need to use 2 capsman with difference command syntax if i have some wifi5 devices.
    Completely useless.
    It's better to do a bash script to configure the access points.

    • @taylorcs89
      @taylorcs89 11 месяцев назад

      i dont think you do?

    • @Nevexo287
      @Nevexo287 11 месяцев назад +1

      It's not as bad as wifiwave2 was on it's own.
      Some of the AC devices support this new CAPsMAN.

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад +1

      I moved to another wifi manufacture years ago. Learned my lesson the costly way with Mikrotik old radios.
      Complaints and trouble tickets stopped dead when we went back to the other wifi vendor.

    • @MarianCampeanu
      @MarianCampeanu 11 месяцев назад

      @@ChrisNicholson Who? "another wifi manufacture"!

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад

      ​@@MarianCampeanuhad to pay the money and go back to Ruckus. We are getting closer with Cambium.
      But cost difference is quickly forgotten when you can "set and forget" systems. Compared to constant tickets. Attempted driver updates. Bug reports. Ohh... And clients getting so sick of it they bought other wifi gear and either fired us or asked us to put it in and toss the caps.

  • @panuoe5866
    @panuoe5866 9 месяцев назад

    Web interface WiFI for UI

  • @Problembaer4
    @Problembaer4 11 месяцев назад +18

    Extremely overcomplicated and confusing for such simple steps. Of course, good to have now two CAPSMANs in one router, but come on, even chepo China-vendors offer a more convenient way. Its so extremely time-consuming to do the simplest steps with mikrotik. For every step you have to read endless documentation and in the end you are totally confused.

    • @Saeglopur89
      @Saeglopur89 11 месяцев назад +1

      Well it's for extremally professional use cases but yes Mikrotik really needs also more user friendly solutions for regular people - this will open huge market for them :) I've seen on forum that they are working on something

    • @BARTeNARUTO
      @BARTeNARUTO 9 месяцев назад +1

      I think it's done on purpose

    • @shaunclarke94
      @shaunclarke94 8 месяцев назад +4

      To be fair, Mikrotik's main benefit is power and flexibility, not being dumbed down.

    • @andrewzasidko6595
      @andrewzasidko6595 5 месяцев назад +1

      What's complicated though? It's literally as easy as configuring the main AP as if it was standalone and then activating same config for managed APs.
      And also to add, you'd be surprised (I was 😂) that Mikrotik has a working 802.11rkv.

  • @Fatmacheto
    @Fatmacheto 11 месяцев назад +12

    That is a pure crap. Mikrotik still haven’t figured it out how to create a proper centralized wifi management system. At least put some kind of graphical statistics and more tools to troubleshoot the Caps…

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад +2

      Close... The Old CAPS-MAN WAS AWESOME... Problem was it could only control lousy radios with drivers that could/have NEVER been fixed.

  • @italex9766
    @italex9766 11 месяцев назад +1

    Mikrotik has reduced CAP and AC2 memory so that customers buy AX and CAP AX expensively. This is not good. Normally all chips are 128 MB. But AC2 and CAP have software reduced to only 16 MB. That's not enough for the large WIFI package. We need roaming function. This is only in WIFIWAVE2 + Capsman

    • @mikrotik
      @mikrotik  11 месяцев назад

      Sorry what do you mean? We can't reduce memory for already manufactured devices. It is the same as it always was.

    • @ChrisNicholson
      @ChrisNicholson 11 месяцев назад

      I think he means you used too little ram in the old models, to be able to do Wave2.

    • @italex9766
      @italex9766 11 месяцев назад

      Not the ram it is flash hdd where is 15MB. But i have seen the new 13 Beta. Mikrotik hat this fixed in the Future. And Cap AC is not old. This is the best Cap compared with the size from the Cap AX@@ChrisNicholson

    • @shaunclarke94
      @shaunclarke94 8 месяцев назад

      They've actually released wifiwave2 for several older devices now.

  • @husseinadil6290
    @husseinadil6290 8 месяцев назад

    Not a straight forward and somehow is complicated

  • @dindin4072
    @dindin4072 11 месяцев назад

    Dynamicaly created Slave interfaces are not added to bridge on CAPs automaticaly. So every reboot causes that i must add this interface to bridge manualy. Any solution for that?

    • @udenspasaule
      @udenspasaule 7 месяцев назад

      All you find workaround?

    • @dindin4072
      @dindin4072 7 месяцев назад

      @@udenspasaule yes, static slaves option