anchor.diff:  
   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
  +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. If you spot an outlet at our Colab feel free to use it.
  +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
  +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. We sysadmins are pretty much the only fans of cabled connection and we love the convenience of cables
  -and because we had a lot of LAN Ports in this building where a school was located
  -back in the day, 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 other
  -half 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 got them).
  +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 less people use
  +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.
  +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) - Alot of DIY, so it'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
  
positive.code: * [hAP ac](https://routerboard.com/RB962UiGS-5HacT2HnT) - like the wAP ac but with
  a built-in switch
  
  We were also pretty harsh when it comes down to kicking people out of our access points,
  because if you got a bad connection you're giving a bad time to all the other people
  using that access point. When we lowered the connectivity threshold to our sweet spot
  of 65dBm we had an awesome connection, but somehow all the other users were having a
  bad time. This is the point you have to realize that you obviously have another perception
  of "things going well" (although you're right). At the moment we're having 20 AP's on 3
  floors, serving over 300 clients during peak hours.
  
  ![ClientsPerAP](ClientsPerAP.jpg)
  
  With all those different devices and total freedom for our coworkers there are
  always some people having connectivity issues nonetheless, so the bigger we get,
  the more important is that we know how to monitor our network and how to distribute
  the load that's hammering on our infrastructure.
  
  ![TrafficPerAP](TrafficPerAP.jpg)
  
  ## Monitoring
  If you're responsible for something which quite a few people rely on every day, you
  as a sysadmin should be able to tell someone where the problem comes from.
  So it's quite important to monitor your radio waves, so you can start investigating
  rising issues before a lot of people are affected by it and to troubleshoot specific
  clients' issues.
  
negative.code: [![Youtube:Steve Jobs 500 WiFi Basestations](jobs.jpg)]
  (https://youtu.be/1-oIL9cLHDc?t=19 "Steve Jobs WiFi")
  
  In this blog post, we'd like to give you a little bit of insight into our configuration
  and how we're troubleshooting our network. 
  Our WiFi runs exclusively on [Mikrotik](https://mikrotik.com/) devices because this gives us a lot of flexibility. Their devices come at a fair
  price and we're not forced to pay fees to use their products.
  When we first came to the new Colab, we had nothing but an empty rack, an old DIY router and
  some broken cables. Step by step we built up the infrastructure, adjusting it to our needs.
  
  ## The dawn of WiFi
  