It’s so easy! All you have to do is know everything about Hugo and the various ways it can be abused! Fork us On github, create a fork of https://github.com/SysManSquad/sysmansquadblogdev, replace the URL below with the correct URL for your fork: Be sure and run the git commands below before running a hugo server or it will cause you all kinds of trouble. 1 2 3 git clone https://github.com/SysManSquad/sysmansquadblogdev git submodule init git submodule update This will download the site code and theme to your computer.

Every year, we have to produce a total of used hours on our compute cluster. The tools for interacting with slurm’s accounting database are complex and the documentation is not very good, so this simple task is incredibly annoying. If you ever have to do this, hopefully you will have an easier time of it. This post is only an example of one way to do the job and there may be better ways.

As of Windows 11, we noticed that we were getting prompted to continue connecting to a network that we’d never had a problem with before. It’s already defined in group policy, so this new behavior is puzzling and annoying. The certificate in question is for the NPS/Radius server our network uses to validate credentials for the wifi. Continue Connecting I really had no idea how to even begin googling for this problem, but while talking to some of my fellow nerds on the Winadmins Discord server, tossing around some ideas on what could be causing this, looking to see whether there was a problem with the certificate, etc.

I had a need in my home lab to quickly deploy a bunch of thin clones of Ubuntu’s cloud image. I chose to use the cloud images Ubuntu provides instead of building a custom template. Xen Orchestra has had support for cloud-init since 2015. Quick Walkthrough Here is the short version of how this works: Download the current 20.04 ubuntu cloud image OVA file, there should only be 1 on each build’s page.

I volunteer to help run Southwest CCDC every year, and had a need to deploy all of the communication infrastructure in a hurry. With Covid Times™ upon us, we needed to move a competition that usually has at least one round in person to all-virtual. Discord was the obvious choice for how to do that successfully - it is targeted to communities of people, and has moderation tools. My discord server needed to have a few things:

Joe Ravi / CC BY-SA https://creativecommons.org/licenses/by-sa/3.0 In previous articles, we’ve built the basic services you need without getting too far in the weeds. Now we’re going to layer in a central identity service. It’s also hopefully going to be a lot shorter than previous articles, though I can’t make any promises - these things tend to all start small, then balloon rapidly. If you’re continuing from NET-102 you’ll already have the following machines:

Welcome back! We’re now going to move on to the actual effort it takes to build your lab. As you recall we got pretty far last time in documenting the beginnings of our network. For this lab I’ll be using VMWare Workstation, but you can accomplish this with Microsoft Hyper-V, Oracle VirtualBox, the free tier of VMWare’s ESX, or XCP-NG. If you haven’t read the previous post, please have a look here as each post builds upon the last.

As I go through my career, I often find that the answers I take for granted are not easy to find for people who are just starting out. I had the advantage of a dedicated class on network administration to build on, but not everyone had that opportunity. While this article focuses on a lab environment, most of the content will be applicable to real life as well. I’ve tried to include as many reference links as possible to help you learn about the concepts involved, but I cannot explain everything in one article.