anchor.diff:  
   ![SignalLevel](SignalLevel.jpg)
   
  -We went on to develop our own self service portal where you can send us a rating
  +We went on to develop our own self-service portal where you can send us a rating
   to our company chat as well as chasing the issue yourself. We've also open sourced
   it and you can get it [here](https://git.panter.ch/open-source/mikrotik_SS_java) and tinker with it however you like. 
   It should work on all [CapsMan](https://wiki.mikrotik.com/wiki/Manual:CAPsMAN) enabled Mikrotik Networks (make sure to
  
positive.code: 
  We started with an emergency setup (2 access points) because we had to move on
  faster than expected, there was not much of a concept, but it worked for us Panters
  who were pretty much alone at that time. While we were having our office on a
  construction site which was quite dusty at the time, we even managed to nearly
  kill our router because he suffocated in the dust (the whole rack was accidentally
  covered in dust) but it was nothing a little bit of compressed air couldn't solve.
  
negative.code: 
  Working on a construction site has its downsides, but it also gives you the
  freedom to plan your LAN outlets and whatnot, or so we thought, but everything got built quite
  differently as planned, so those outlets are still a vision. We had to reverse engineer
  every single one of a bunch of cables because documentation of the existing network was nonexistent.
  
  When we moved to the Colab, our rack was neat and clean and there were almost no cables.
  We also had to install the cables by ourselves because our top floor was a dusty
  attic which looked like it hadn't been touched for the last half of the decade. Since then all visible and non-visible LAN
  outlets were patched. So if you spot an outlet at our Colab, feel free to use it.
  
  ![Before and after](beforeAfter.jpg)
  
  With the help of our network crack (koa), we got a solid setup and started to
  use Mikrotiks Capsman, which is a bit of a pain to get into and a little bit of
  a hassle to wrap your head around it, but it works like a
  charm after the initial setup (and 10 factory resets later).
  
  ## Perception
  There's always a gap between sysadmins and users when it comes to quality. Us sysadmins are pretty much the only fans of cabled connection and we love the convenience of cables.
  And sinc we had a lot of LAN Ports in this building, where a school was located
  back in the days, we had this sweet vision of small access points and switch combos on every
  table so people who preferred WiFi could get it from the ether and the others could use cables as they desire. But well, that idea got chased out of town
  pretty fast (Except the [makerZspace](https://makerzspace.ch/), they love cables and so they have them).
  
  We decided to aim for total 5g coverage and slowly starve out 2.4g because it's
  way faster and it allows you to put up a higher density of access points and if fewer people use
  one access point everyone will have a faster connection. And since we were living in
  the year 2015 where every device is capable of 5g there shouldn't be an issue with
  partially dropping 2.4g, right? TOTALLY WRONG
  
  ![ClientBandDistribution](ClientBandDistribution.jpg)
  
  As it turns out, the 5g capable devices aren't consistently great with 5g connectivity.
  Most of those devices only support the lower bands 5-036 and 5-044 and hollow glass
  bricks are apparently the death of every 5g connection. There are also quite some
  differences between mikrotiks different products. Here's a list of a few which
  we went through and the ones we're currently using.
  
  ### Legacy AP's
  * [Netmetal](https://routerboard.com/RB922UAGS-5HPacT-NM) - A lot of DIY, so it's
  time consuming and thus not quite cheap, but nearly indestructible and perfect
  for outdoors
  * [Netbox](https://routerboard.com/RB911G-5HPacD-NB) - Also DIY, pretty huge and
  