<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shane Hull on Medium]]></title>
        <description><![CDATA[Stories by Shane Hull on Medium]]></description>
        <link>https://medium.com/@shanehull?source=rss-2fb2aa2ba2ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*QfTgxL0xwQvE9sepsObBvQ.jpeg</url>
            <title>Stories by Shane Hull on Medium</title>
            <link>https://medium.com/@shanehull?source=rss-2fb2aa2ba2ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:36:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shanehull/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Configuring PacketFence for use with DPSK]]></title>
            <link>https://medium.com/beyond-the-helpdesk/configuring-packetfence-for-use-with-dpsk-6519aaf6fe4d?source=rss-2fb2aa2ba2ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/6519aaf6fe4d</guid>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Shane Hull]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 00:40:28 GMT</pubDate>
            <atom:updated>2020-01-10T00:57:35.895Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this article I’ll provide a detailed overview on how to configure PacketFence for use with the DPSK (Dynamic Pre-Shared Key) feature.</em></p><p>We’ll be using a Cisco 3504 Wireless LAN Controller to create our lab test, but the process should be fairly uniform across different vendors.</p><p>First up, you’ll want to install PacketFence using either the ZEN (Zero Effort NAC) option, or on a fresh install of Debian or CentOS.<br>A detailed guide for both options can be found on the <a href="https://packetfence.org/doc/PacketFence_Installation_Guide.html#_installation">PacketFence website</a>.</p><p>Once installed, you’ll get access to a web interface running on port 1443:<br><a href="https://packetfence.noddy.mckinnonsc.vic.edu.au:1443/admin/alt#/configuration/interfaces">https://[PacketFence IP]:1443</a></p><h3>Initial Setup</h3><p>Go through the initial setup wizard, which is pretty straight forward except for a couple of things which I’ll explain below.</p><p>Firstly, ensure you select ‘RADIUS Enforcement’ as the Enforcement mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*Pt0icyQRSamE3oDqNHze-A.png" /></figure><p>On the networks tab, there will be an interface entry pre-populated for ‘eth0&#39;, which should be have the IP address PacketFence got from DHCP (or from you if you’re using a static address).<br>Click this interface and make its type ‘Management’, adding an additional listening daemon for ‘portal’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*lyN8lsuebq35k5FJwWmGag.png" /></figure><p>On the next screen, set your passwords. To create your MySQL root password, just hit ‘Test’ and a pop will appear asking you to set a new password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*BNsN057BVVLK6uHW-kD9Iw.png" /></figure><p>Continue through the steps until all passwords are set.</p><p>Set up Fingerbank if you would like device fingerprinting. <br>This is useful if you want to configure different behaviours based on device type.</p><p>Once everything is filled in as per your environment, start PacketFence’s services and you will be taken to the main admin interface.</p><h3>Authentication Sources</h3><p>You’ll want to set up an Authentication Source such as Active Directory for users and admins to authenticate against.</p><p>Before we do so, head over to Policies and Access Control &gt; Roles and add a Role for each VLAN you’d like to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*KyrEFgfJvuPQUmE4WYeavA.png" /></figure><p>Now head over to Policies and Access Control &gt; Authentication Sources and add a new source of type ‘Active Directory’.</p><p>The settings will depend on your AD setup, but here’s an example of what we ended up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oLYgg5gUyCbSLiUSrUxE8A.png" /></figure><p>Once you’ve configured and tested the settings for AD, you’ll want to give it some rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QTPhcrLakE_K-nNMuOJZA.png" /><figcaption>‘Authentication Rules’ are matched at the time a user logs in to the web portal and are used to assign VLAN’s based on their group in AD.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IyGlvFjqhZIvatOk08ZJPg.png" /><figcaption>‘Administration Rules’ are matched at at the admin interface login page, so we’ve given ‘Tech’ full access and created a catch all for no access.</figcaption></figure><p>To test these rules, PacketFence includes a script by the name of ‘pftest’ which allows you to run an authentication test on any username or password you wish by running the following in the PacketFence ‘bin’ directory (usually located at /usr/local/pf/bin):</p><pre>./pftest authentication [username] [password]</pre><p>We’ll also want to join PacketFence to the domain over at Policies and Access Control &gt; Active Directory Domains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOjz2ELVmy2e2BEA1-ZPLg.png" /></figure><h3>Network Devices</h3><p>Next up you’ll want to add a ‘Switch’, eg. your Wireless Controller.</p><p>Here’s an example of ours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kjw9OwNZuyfVK_lvAnu3nQ.png" /></figure><p>The important part here is to ensure ‘Roles’ is configured correctly, enabling only ‘Role by VLAN ID’ and setting the ID’s as per your network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l1dV9FqzekojEU-muvmNjA.png" /></figure><p>So the WLC knows what PacketFence is talking about, you have to configure an interface for each VLAN you’d like to use and give it a static IP address.</p><p>On the Cisco 3504, this is under Controller &gt; Interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*wjx9skXozlXocAfiSf2aZA.png" /></figure><h3>IP Helpers</h3><p>PacketFence needs to know about DHCP requests on the network to function properly. To forward all relevant requests to PacketFence, you’ll want to add a a ip helper-address address to each VLAN to ensure PacketFence receives these requests.</p><p>I our case we added an ‘ip helper-address’ to each relevant VLAN on our Core Switch, an Aruba, which looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*BO5YI9NS71d_L7E5Dum3Vw.png" /></figure><p>As you add these, you’ll be able to verify it by heading to ‘Nodes’ on the PacketFence admin interface.<br>You should see devices quickly populate this list as PacketFence discovers their DHCP requests.</p><h3>SSID’s</h3><p>You’ll want two SSID’s, one for onboarding and one for secure access.</p><p>Before we begin, we’ll create an ACL for use on the open SSID.<br>The ACL should block everything except the PacketFence web portal, DCHP and DNS and should look something like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HYdXWSxabDBiclkaLlfEA.png" /></figure><p>We’ll also add PacketFence as an authentication server under SECURITY &gt; AAA &gt; RADIUS &gt; Authentication, as well as under Accounting.</p><p>For this lab, I chose ‘PF-WebAuth’ as the onboarding SSID which is open, with MAC filtering enabled and no Layer 2 security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*jJ7yVW-uVPke_ysXHyIJfQ.png" /></figure><p>Under Layer 3, we want to enable Web Policy and apply the ACL from earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*BCvIK9N7Zx2BKmNOt-njGA.png" /></figure><p>On the ‘AAA Servers’ tab, select the PacketFence server as the Authentication Server and the Accounting Server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ELCWZrHqX6ZgQz08nbR1GA.png" /></figure><p>Go to the Advanced tab and ensure ‘Allow AAA Override’ is ticked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*pP11SSgAT5p3S81LldW2Iw.png" /></figure><p>We’ll also want to configure the web portal URL under Security &gt; Web Auth &gt; Web Login Page to be: <a href="https://[packetfence-ip]/captive-portal">https://[PacketFence-ip]/captive-portal</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/1*X7WdaU7W0_6y0N66yoocjg.png" /></figure><p>Now we’ll move on to the Secure SSID.</p><p>Under Security &gt; Layer 2, we’ll want to enable WPA+WPA2, WPA2 Policy and AES. We’ll also want to tick PSK, set ASCII as the PSK Format and input a default PSK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*bJoR5ONdrLHalYTMxxgxRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*47GNrDIn4-ZoOiptz982Pg.png" /></figure><p>Again, set the Authentication and Accounting Servers under ‘AAA Servers’ and ensure ‘Allow AAA Override’ is ticked under the ‘Advanced’ tab.</p><h3>Connection Profiles</h3><p>Next we want to configure some Connection profiles within PacketFence to make use of the SSID’s we configured.</p><p>Before we continue, we’ll create a provisioner for DPSK’s under Advanced Access Configuration &gt; Provisioners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVnypq5QRUBJkN43lftmoQ.png" /></figure><p>Now we’re ready to configure our Connection Profiles.</p><p>Firstly, edit the default profile, ensuring ‘Dot1x recompute role from portal’ is turned on, your authentication source is selected under ’Source’ and the provisioner for DPSK’s you just created is selected under ‘Provisioners’.<br>I’ve also selected the ‘default’ policy under ‘Self service policy’, which as we’ll see later allows users to register their own devices using its MAC address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjthrRetBYPT4W5nfizZog.png" /></figure><p>Next, we’ll create a second Connection Profile to match the secure SSID, configured to filter based on the name of the SSID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56UdQzS9Vc-3Y9oQdFMkxg.png" /></figure><h3>Portal Modules</h3><p>This will depend on what else you want out of PacketFence and is highly customisable, however this is the workflow we ended up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*bNthGO4vzdQidoLx9DXSyQ.png" /></figure><p>In addition to providing a simple login to obtain a DPSK, we wanted to include an easy way for guests to connect by verifying a phone number and we also wanted to include a way to manage your own devices, eg. add a device using its MAC address, or remove a device.</p><h3>The Result</h3><p>In the end, this is what the user experience looks like if I were to connect my phone using my student username and password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnJHp84ecV09LZozJ5Snsw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*imKzBAkbRc-6FUZmLC-7rw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zpqfo7ukeCl83Ao9rhNGw.jpeg" /></figure><p>Users can choose to manage their devices, with the option to connect a device using its MAC address. This is extremely useful in the case of an IoT device such as a Google Home or a Chromecast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCyAFpatEnxMeY81RvWuDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I0tttbr3QVbRVtqQVF9lQA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*miuPR2-7VRIMgGtFP9459A.jpeg" /></figure><p>Guests can easily connect by accepting the terms and verifying a phone number, which provides some accountability without being a barrier to their access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TWzxnxfuvtsRGymEVpqHpg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOYMDg2ZZMAaU-yls8GcIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HCbQBXOeU9DQ_fv4N5dqg.jpeg" /></figure><p>PacketFence is an absolute beast. Figuring all this out was a bit of a roller coaster, but once you get it up and running the experience is about as good as WiFi authentication gets.</p><p>I’m sure I’ve missed something, but I hope this information is able to help someone to get up and running with their own PacketFence solution, while saving their organisation $20,000+ p/a.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6519aaf6fe4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/configuring-packetfence-for-use-with-dpsk-6519aaf6fe4d">Configuring PacketFence for use with DPSK</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Room Monitoring with IoT]]></title>
            <link>https://medium.com/beyond-the-helpdesk/server-room-monitoring-with-iot-5a7d85ae964b?source=rss-2fb2aa2ba2ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a7d85ae964b</guid>
            <category><![CDATA[electronics]]></category>
            <category><![CDATA[esp8266]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[arduino]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Shane Hull]]></dc:creator>
            <pubDate>Fri, 28 Jun 2019 05:13:56 GMT</pubDate>
            <atom:updated>2019-07-18T01:46:38.059Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*ZoL1cFtADI51k_bgLOOduA.png" /></figure><h4>Using an ESP8266 as a sensor node for environmental monitoring</h4><h4>We spent months searching for a simple solution to monitor our server room temperatures, only to be quoted thousands of dollars for rack mountable monstrosities that don’t offer much more than what a cheap ADC sensor and a WiFi enabled Espruino board would.</h4><p>In this guide I’ll explain how we set up a simple temperature/humidity sensor monitor using an ESP8266 board, a DHT11 sensor and <a href="https://www.home-assistant.io/">Home Assistant</a> (using the <a href="https://www.home-assistant.io/hassio/installation/">HassIO virtual appliance</a>).</p><p>I won’t focus so much on Home Assistant or HassIO, as they already have documentation for everything you could ever think of <a href="https://www.home-assistant.io/docs/">here</a>.</p><p>The only additional thing you will require aside from a default install of Home Assistant is the <a href="https://www.home-assistant.io/components/esphome/">ESPhome plugin</a>, which is a one click install if you’re using one of the HassIO options.</p><h4>Parts List</h4><ul><li>NodeMCU ESP8266 v3 (Lolin) — available <a href="https://www.aliexpress.com/item/32266751149.html?spm=a2g0s.9042311.0.0.76304c4dEMPCKW">here</a></li><li>DHT11/DHT22 sensor, preferably with the integrated pull up resistor — available <a href="https://core-electronics.com.au/dht11-temperature-and-relative-humidity-sensor-module.html">here</a></li><li>28 AWG jumper wires — available <a href="https://core-electronics.com.au/premium-female-female-jumper-wires-20-x-12-300mm.html">here</a></li><li>3D printer (optional)</li></ul><h4>Putting it together</h4><p>There are different pinouts depending on the circuit layout of the DHT you have, so make sure you look up the wiring diagram before trying to hook it up, or it may end up <a href="https://www.youtube.com/watch?v=LVchogIdYF0">melting</a>!</p><p>The ones I linked above look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AV90sx4byp-wvUPenqgeww.png" /></figure><p>We want to attach the signal cable to any of the pins beginning with a “D”, the Ground to any pin labelled “G” and the Vcc (+) pin to the pin labelled “VU” (or “VV” on the board I received), which stands for VUSB. The VV/VU pin outputs 5v direct from USB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*7QbVz3kUXYmmE6TC" /></figure><p>I chose to 3D print a case for mine, which I remixed from one posted by another user to make it rack mountable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MUAwnR2-xpzpWHoOW92MZA.jpeg" /></figure><p>The design is available for download <a href="https://www.thingiverse.com/thing:3715761">here</a>.</p><h4>Compiling and Uploading the Firmware</h4><p>Let’s install ESPhome’s CLI tools so we can compile and flash the board with the ESPhome firmware.</p><p>Firstly, make sure you have <a href="https://www.python.org/download/releases/2.7/">Python 2.7</a> (🤔) installed and run:</p><pre>pip install esphome</pre><p>Use ESPhome’s built in wizard to set the values of your configuration file.</p><pre>esphome server_room.yaml wizard</pre><p>It will ask you for some basic configuration values such as a name the platform type etc. You will want to enter something along the lines of:</p><pre>name: server_room<br>platform: ESP8266<br>board: nodemcuv2<br>ssid: MyWiFi<br>psk: extremelysecurewifipassword<br>password: extremelysecureotapassword</pre><p>This will create a basic yaml file, which assists ESPhome in compiling the firmware for your ESP board.</p><p>Now, to upload and run the firmware make sure your ESP8266 board is plugged in to your computer via microUSB and run the following:</p><pre>esphome server_room.yaml run</pre><p>You should be asked what port you wish to use to upload the firmware; USB2.0-Serial or OTA. Select the number corresponding to USB2.0-Serial and hit enter.</p><p>If there are no errors, the output from ESPhome should display its current signal strength, a valid IP and other network information like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/0*0fEqkKscAn-qVmY6" /></figure><p>Once you’ve confirmed that the node connects to the WiFi and obtains an IP, you’ll want to add some more info to your config file and upload your changes.</p><p>Open the yaml file in any text editor you’re comfortable with and update any config, which I’ll explain below:</p><pre>vim server_room.yaml</pre><p>My configuration looks similar to this:</p><pre>esphome:<br>  name: server_room.yaml<br>  platform: ESP8266<br>  board: nodemcuv2</pre><pre>wifi:<br>  ssid: &quot;McKinnonSC&quot;<br>  password: &quot;VerySecurePassword&quot;<br>  manual_ip:<br>    static_ip: 192.168.1.2<br>    gateway: 192.168.1.1<br>    subnet: 255.255.255.0</pre><pre># Enable logging<br>logger:</pre><pre># Enable Home Assistant API<br>api:<br>  password: &quot;VerySecureAPIPassword&quot;</pre><pre>ota:<br>  password: &quot;VerySecureOTAPassword&quot;</pre><pre>sensor:<br>  - platform: dht<br>    pin: D2<br>    model: DHT11<br>    temperature:<br>      name: &quot;Server Room Temperature&quot;<br>    humidity:<br>      name: &quot;Server Room Humidity&quot;<br>    update_interval: 10s</pre><pre>  - platform: wifi_signal<br>    name: &quot;WiFi Signal Sensor&quot;<br>    update_interval: 60s</pre><p>As I had issues with resolving the nodes IP via mDNS, I set the IP to static, reserving it in DHCP. And as I had issues with 2.4Ghz signal when using previous ESP8266 boards, I like to monitor the current RSSI.</p><p>You may wish to go with the bare minimum, eg:</p><pre>esphome:<br>  name: server_room.yaml<br>  platform: ESP8266<br>  board: nodemcuv2</pre><pre>wifi:<br>  ssid: &quot;McKinnonSC&quot;<br>  password: &quot;VerySecurePassword&quot;</pre><pre># Enable logging<br>logger:</pre><pre># Enable Home Assistant API<br>api:<br>  password: &quot;VerySecureAPIPassword&quot;</pre><pre>ota:<br>  password: &quot;VerySecureOTAPassword&quot;</pre><pre>sensor:<br>  - platform: dht<br>    pin: D2<br>    model: DHT11<br>    temperature:<br>      name: &quot;Server Room Temperature&quot;<br>    humidity:<br>      name: &quot;Server Room Humidity&quot;<br>    update_interval: 10s</pre><p>When you’re happy with the config, upload and run it again, or if you just want to upload it, try:</p><pre>esphome server_room.yaml upload</pre><h4>The node is ready to deploy!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrHVvbajmyXKPzuBeM04Uw.jpeg" /></figure><p>Once it’s all plugged in and has been running for a few minutes, your HassIO install should automatically detect the device and notify you, asking you to add it as a new entity.</p><p>If it doesn’t, no stress — just head over to Configuration &gt; Integrations and hit the plus button in the bottom right of the screen. <br>Select ESPhome &gt; and enter the hostname of the node, eg: “server_room.yaml”, or the static IP set in your config.</p><p>If successful, it will now appear as an entity and you’ll be able to create dashboards with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*TB974iUtGf3JS2k5OI8_vQ.png" /></figure><p>You can even create an automation to notify Slack when the sensor reaches a certain temperature!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/383/0*eh--6agWr4e4l4ze" /></figure><p>We now have full visibility on how well our air conditioners are performing.</p><p>Our next project will be leak detection using a <a href="https://core-electronics.com.au/soil-moisture-sensor-arduino-compatible-immersion-gold.html">soil moisture sensor</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a7d85ae964b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/server-room-monitoring-with-iot-5a7d85ae964b">Server Room Monitoring with IoT</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UniFi Switches in an Enterprise Environment]]></title>
            <link>https://medium.com/beyond-the-helpdesk/unifi-switches-in-an-enterprise-environment-2c33b9af7c6c?source=rss-2fb2aa2ba2ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c33b9af7c6c</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[unifi]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[switch]]></category>
            <dc:creator><![CDATA[Shane Hull]]></dc:creator>
            <pubDate>Thu, 21 Dec 2017 22:23:33 GMT</pubDate>
            <atom:updated>2017-12-21T22:23:33.550Z</atom:updated>
            <content:encoded><![CDATA[<p>How we simplified switch management for a quarter of the price.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cWC7s1Z4QhxtxpF1Te8WA.jpeg" /></figure><p>Replacing an entire fleet of switches is a big task and choosing the right solution for your network is one that should be left up to your team, not the sales guys.</p><p>In the lead up to 2017 we came to the realisation that our switch network was getting old, clunky and inefficient to manage.</p><p>We began our search for the most suitable fit and the sales calls started rolling in. We considered all the big guys such as D-Link, HP, Aruba, Cisco, Meraki, Dell and Juniper.</p><p>With Cisco becoming more expensive and convoluted as ever, we considered Juniper and Aruba, which would land us at a price point of $2,000–$4,000AUD per switch, with the added benefit of a better management experience.</p><p>We also had another contender. Despite many doubts around their gear being suitable for enterprise networks, UniFi started to look like a viable option for us.</p><blockquote>And at a quarter of the price, we had little reason not to consider UniFi.</blockquote><h4><strong>Why we decided on UniFi</strong></h4><p>The most important factor in our decision was an easy-to-manage system. With so many team members and so many changes day to day we wanted it to be easy to deploy VLAN’s across the entire network, as well as per node.</p><p>We didn’t require any layer 3 capabilities, as our core switch handles all VLAN routing. Just a simple layer 2 switch capable of carrying VLAN’s will do just fine.</p><p><em>Learn a bit more about our switch topology in Matthew’s article </em><a href="https://medium.com/beyond-the-helpdesk/quickly-improve-your-vlan-security-with-vacls-57e4bdafa6a7"><em>here</em></a><em>.</em></p><h4><strong>What was it like before?</strong></h4><p>Beforehand, our switches were all D-Link DGS series devices, which had all the capabilities, but were an absolute nightmare to manage.</p><p>Although the learning curve was not massive for your average technician, they still required specialised knowledge from all team members to be able to configure correctly and efficiently, and even with the knowledge required, we often spent hours troubleshooting VLAN issues across our network. Most of our time was spent logging in to 5 or so switches through separate interfaces just to tag or untag one port.</p><p>To configure a VLAN, these were the steps required:</p><ul><li>Configure the VLAN on the core switch</li><li>Log in to the web interface of each individual switch in the network</li><li>Add the VLAN ID and name to each individual switch</li><li>Tag the VLAN on each trunk port on each individual switch</li><li>Untag each port where the VLAN is required on each switch required</li></ul><h4><strong>What it’s like after the rollout</strong></h4><p>As we were rolling them out, we found ourselves blaming the UniFi’s for every single unexplained network annoyance, but found we were wrong each and every time.</p><p>If anything, the new hardware made the network run a lot smoother and the UniFi controller made managing devices and VLAN’s a whole lot easier and far less time consuming. Having a central view of what is active and what VLAN the port is on really revolutionised how we view at the network as a whole.</p><p>To configure VLAN’s on the UniFi’s, these are the steps required:</p><ul><li>Configure the VLAN on the core switch</li><li>Log in to the web interface of the UniFi controller</li><li>Add the VLAN ID and name to the Settings &gt; Network menu, making sure to tick “VLAN Only”</li><li>Select each switch from the list in the controller, tick all ports required and select your VLAN</li></ul><h4><strong>Where’s my lifetime warranty?</strong></h4><p>If you’ve looked into the UniFi range at all, you may have noticed that they only ship with a 1 year limited warranty.<br>At the price point we paid, we really didn’t see an issue with this and we didn’t see a need for a support contract. <br>In the unlikely event that we replace the all of the switches once in their lifetime, we’ll still have a solution for half the price. We’ve also found that when it comes to enterprise support, 9 times out of 10 we’ll end up fixing the issue ourselves anyway.</p><p>Would UniFi be a suitable fit for your network? Maybe, maybe not — let us know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c33b9af7c6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/unifi-switches-in-an-enterprise-environment-2c33b9af7c6c">UniFi Switches in an Enterprise Environment</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Printing Volumes and Efforts to Reduce the Numbers]]></title>
            <link>https://medium.com/beyond-the-helpdesk/printing-volumes-and-efforts-to-reduce-the-numbers-b68d26de37b6?source=rss-2fb2aa2ba2ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/b68d26de37b6</guid>
            <category><![CDATA[print]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[paperless]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Shane Hull]]></dc:creator>
            <pubDate>Thu, 29 Jun 2017 02:13:49 GMT</pubDate>
            <atom:updated>2017-06-29T02:45:59.904Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nqjMfc6pwiqWf1EOcNWS0Q.jpeg" /></figure><p>Printing is one of the biggest ongoing expenses of any school. Not to mention it produces huge amounts of waste and is one of the many contributors to the deforestation of national and state parks. <br>Reducing print usage should be on the top of the list for any educational institute, but not at the expense of it’s student’s success.</p><p>Throughout 2016, we printed a total of 1564.45 pages per student. <br>We thought this was particularly high, so in an attempt to compare our usage to other schools, we decided to survey a handful of Victorian Schools on the same data.<br>Out of the 29 schools we surveyed, only 6 were willing to provide data. We found that these schools printed an average of 1415.49 pages per student over the school calendar year.</p><p>To gauge where you might sit compared to these schools, you can follow the trend-line in the graph below based on your total enrolments. For example, if we look at a school of 750 students on the graph we can see where the red line is placed at about 714, 286 pages. This is an example of what most schools are currently printing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eHozqGsQKTmT_pkDAedMKQ.png" /></figure><blockquote>Where does your school fall - above or below the red line?</blockquote><h4>How do we reduce these numbers?</h4><p>Out of all the schools we surveyed there were two reoccurring solutions which seemed to have a positive impact:</p><ul><li>Cloud document solutions (Google Docs/Office365)</li><li>Printing control solutions and tap and release</li></ul><p>And while these solutions are a good start, there are many applications for printed paper which just cannot be substituted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1mKyjKvxEIkGtDvlv0Ymg.png" /><figcaption>McKinnon Secondary College</figcaption></figure><p>The idea is not to put a restriction on printing, but to make schools aware of their volumes, while providing other mediums to which they can use in its place place where they deem appropriate.</p><p>We want to encourage schools to release this information, as ugly as it may be, because without measuring our impact we can’t improve on it.</p><p>Please feel free to share your thoughts and data on your printing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b68d26de37b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/printing-volumes-and-efforts-to-reduce-the-numbers-b68d26de37b6">Printing Volumes and Efforts to Reduce the Numbers</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chromecast in 95 Rooms]]></title>
            <link>https://medium.com/beyond-the-helpdesk/chromecast-in-95-rooms-835d1f0bd040?source=rss-2fb2aa2ba2ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/835d1f0bd040</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[mdn]]></category>
            <category><![CDATA[avahi]]></category>
            <category><![CDATA[chromecast]]></category>
            <dc:creator><![CDATA[Shane Hull]]></dc:creator>
            <pubDate>Thu, 02 Mar 2017 00:59:51 GMT</pubDate>
            <atom:updated>2017-03-02T00:59:51.782Z</atom:updated>
            <content:encoded><![CDATA[<p>In a media driven age, providing a reliable and effective method of presenting content within the classroom is a huge factor in the success of our students.</p><p>The reliability of presenting to a TV or Projector is an important part of every teacher’s day. If a teacher encounters an issue during a presentation, it creates a disruption of learning for those in the classroom, greatly reducing the effectiveness of the lesson.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0v3Zx-3Zrbi52uzuvQSecg.jpeg" /></figure><h4><strong>What’s wrong with plain old cables?</strong></h4><p>We currently have 95 projectors installed at our campus. Each projector is used at least once every school day at an absolute minimum-sometimes up to six times.</p><p>As you can imagine, such high usage results in a significant amount of cable failures, costing the school both time and money to replace. To put this in to perspective, we tend to a classroom for a cable failure once a day on average and the school spent $25,000 on replacements throughout 2016 alone.</p><h4><strong>So, how do we ditch the cables?</strong></h4><p>We needed a solution for wireless presentation — one which was reliable and did not require endless tinkering to implement. We needed something as close to a turnkey solution as possible and most importantly we needed to remove the need for cables.</p><p>Whatever we implemented, it had to be compatible with multiple operating systems, including Windows, MacOS and ChromeOS, which ruled a large number of products out immediately. After researching almost every solution available, including those aimed at education, we found ourselves coming back to Google’s Chromecast. It was the only multi-platform option which offered simplicity in both its operation and installation — not to mention it was the cheapest of them all.</p><p>We also found that iOS or ChromeOS updates would often break third party solutions, whereas Chromecast is supported end-to-end. Additionally, Chromecast allows the user to cast a single Tab to the room while multitasking and working in other Tabs. This is a huge convenience for teachers, particularly when marking the roll or dealing with sensitive information.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQMerqyMDNmc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQMerqyMDNmc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQMerqyMDNmc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a5591e1b9a4997c7c28ba2637f31d744/href">https://medium.com/media/a5591e1b9a4997c7c28ba2637f31d744/href</a></iframe><h4><strong>Is it that easy?</strong></h4><p>At a glance, Chromecast seems like a miracle solution, but making a non-enterprise product perform in an enterprise environment is quite a challenge. The way Chromecast is designed assumes that there is a limited number of users connected to the network. It operates on a protocol called mDNS and broadcasts its visibility to anyone and everyone on the network. Any user connected to the same network as the Chromecast is able to control it.</p><p>A good example of the type of issues this design can cause is the<a href="https://www.howtogeek.com/282388/how-to-remove-chromecasts-notifications-from-your-android-phone/"> network-wide Android notification</a> recently implemented by Google. If you are not aware of this notification, it is generated by Google Play Services on every Android device whenever a Cast session is seen as active on the same network, allowing the user full control. The user assumes it is their phone Casting, or they just want that pesky notification to go away, so instead of dismissing the notification, they hit the “X”, which ends the Casting session.<br>The same notification is also generated on ChromeOS in the system tray.</p><p>To solve this problem, we created a separate VLAN for the Chromecast devices, implemented a Virtual Machine running Ubuntu and a service called<a href="https://github.com/lathiat/avahi"> Avahi</a>. Avahi “reflects” all mDNS traffic between the Chromecast VLAN and the Staff VLAN, making mDNS discovery possible for clients of the Staff VLAN.</p><p>In addition, we blocked access from our Student VLAN’s to the Chromecast VLAN via an Access Control List (ACL) on the core switch. ACL’s allowed us to prevent any IP communication from the Chromecast VLAN making it across to the Student VLAN’s, as in our setup, it was still possible for Chromecast to be discovered via mDNS — blocking IP access was the only method which prevented discovery. Learn more on ACL’s in <a href="https://medium.com/beyond-the-helpdesk/quickly-improve-your-vlan-security-with-vacls-57e4bdafa6a7#.xlubmu80d">Matthew’s article</a> on the topic.</p><p>Blocking student access certainly wasn’t our aim. However, it was necessary at this stage in the project. Having around 1000 Android devices and 2000 Chromebook’s in the school meant that Casting sessions would be stopped constantly if this was left open.<br>It is a priority that we revisit students ability to Cast in the near future — however, at this stage we are relying on Google to remove the notification from Android devices as well as ChromeOS.</p><h4><strong>The results so far</strong></h4><p>Providing an alternative to VGA or HDMI output immediately reduced the frequency of disruptions in the classroom. We found that the few teachers who were reluctant to the shift in technology would turn to Chromecast when the cables failed, preventing any ongoing disruptions and encouraging them to ditch the cables for good.<br>A quick stroll through the school shows that most teachers have abandoned cables. Word of mouth appears to be spreading and feedback around the staff room is largely positive.</p><p>Thanks for reading and stay tuned for updates on how this progresses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=835d1f0bd040" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/chromecast-in-95-rooms-835d1f0bd040">Chromecast in 95 Rooms</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>