MikroTik Enterprise Wireless Networks. How to have a working CAPsMAN in 5 minutes

แชร์
ฝัง
  • เผยแพร่เมื่อ 4 ส.ค. 2024
  • MikroTik Enterprise Wireless Networks. How to have a working CAPsMAN in 5 minutes, Erion Demiri (ENS - Easy Network Solutions, Albania). Wireless Networks have been in continuous evolution. The presentation will focus on MikroTik Enterprise Wireless Networks based on CAPsMAN. What hardware and software can be used, with samples from real life, mid to high-scale installations. We will see the base options needed for a working CAPsMAN installation in 5 minutes. More advanced options and the reasons to use them will also be covered.. PDF: mum.mikrotik.com/presentation....
  • วิทยาศาสตร์และเทคโนโลยี

ความคิดเห็น • 9

  • @drreality1
    @drreality1 5 ปีที่แล้ว +1

    Great tutorial

  • @aakashrajput6309
    @aakashrajput6309 3 ปีที่แล้ว

    Hi, can I run capsman on hex S and use Power Box, RB2011UiAS-2HnD-IN & CAP AC as ap?
    Also I will try to terminal FTTH connection on power box but Hex S is gateway thanks in advance

  • @ChrisNicholson
    @ChrisNicholson 5 ปีที่แล้ว

    The only problem being that Mikrotik Wireless has SERIOUS Problems with noisy, interference laden environments.
    Also the APs themselves have pretty serious hardware limits that other manufactures don't. But if you are working with a system that "NO BODY IS GONNA BITCH" when they can't get over about 285Megs on the wireless. You might be ok. But if you start loading down the systems with lots of connections... you will run into problems.
    While I love Mikrotik for routing and I can do "A LOT" with Caps-Man... I have to accept that it just doesn't perform as well as other vendors as a straight up radio.

    • @ErionDemiri
      @ErionDemiri 5 ปีที่แล้ว

      As with everything else, it is a matter of choice. The hotels and companies that I have configured with CAPsMAN have always needed much less than 285Megs/client in wireless. Working carefully with frequencies, choosing how to spread the APs, their positions when mounted etc, permitted us to create big/stable networks and with a fraction of the cost of other vendors. The cost should be kept in consideration because it is The most important value the customer sees :). To tell the truth I haven't got experience with many many vendors (only 2-3 more) because I simply didn't like to experiment and loose time and money, when already having something that made possible everything I needed.

    • @ChrisNicholson
      @ChrisNicholson 5 ปีที่แล้ว +2

      @@ErionDemiri I ran into a clear cut case of radio vs noise and Mikrotik could not handle it. Support emailed back that they reproduced the exact same problem when I demonstrated how. They also finally admitted that they don't currently have a way to fix it.
      Removed cap-ac. Placed the exact same settings on a Ruckus R510 I got off Amazon. Problems vanished.
      I did a bar with Caps-man and it suffers from the same problem. The other 50 or so bars... Don't have the disconnect problems. I have a steadfast rule that my commercial installs get Ruckus.
      While price may SEEM like the most "Valued" thing. Having it actually WORK is the most valuable thing.

    • @ErionDemiri
      @ErionDemiri 5 ปีที่แล้ว

      @@ChrisNicholson interesting

    • @ChrisNicholson
      @ChrisNicholson 5 ปีที่แล้ว

      I finally have to give up on Tik wireless. I am sick and tired of all the customer complaints. I am seeing more and more sites where clients will show hundreds of disconnects an hour. Then I waste hours trying to fix it and email with support. Most get no reply until I bitch on the forum. Then you find out the issues you have have been reported by other users for years.

    • @PetrKrenzelok
      @PetrKrenzelok 4 ปีที่แล้ว

      Well, we used MT for a production company, creating a mesh network for wireless bar code readers, but it was rather clean environment. Then I have friend using an Unifi. And in terms of the recent company I work for, we are using Arubas. If you think, that those are hassle free, then you are actually wrong.