Mike G mkgin

Fixing Eaton UPS Connection Issues with NUT on Linux

Problem Description

The Network UPS Tools (NUT) driver fails to connect to an Eaton 5E UPS (and likely other Eaton USB-connected UPS models) despite the UPS being properly detected by the system. The driver continuously fails with permission errors.

Symptoms

nut-driver@*.service fails to start with exit code 1
Journalctl shows errors like:

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

First

Install the app "Sports DV" and change WiFi SSID and password

URLs

Wifi and Cam settings are seperated and have different port numbers.
Wifi-Settings (just login withoug username and password): http://192.168.25.1
Cam LiveStream: http://192.168.25.1:8080/?action=stream
Not sure how the configuration is made really... Would need a Man-In-The-Middle-Attack or send the initial ICMP package

Change AP (Cam is the access point) to Station (Cam is a normal WiFi Client)

Turning `emacs` into a Python IDE

## Create a new config/initialisation file

Create a user-level initialisation file init.el:

touch .emacs.d/init.el

Step 1 - Make a Discord Webhook

Find the Discord channel in which you would like to send commits and other updates
In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!

Step 2 - Set up the webhook on Github

Navigate to your repository on Github, and open the Settings

	0. Don't have a SIM card in when you're updating radio firmware or it will bomb out partway through as it changes from internal IP to IP passthrough

	1. Disable external IP passthrough mode: Network Setting -> Broadband -> Cellular APN -> #1 -> Modify icon -> "IP Passthrough" slider to off

	2. Use "management" Wi-Fi AP as general Wi-Fi AP (with limitations) -> Network Setting -> Bridge1 -> Modify icon -> Move the Wi-Fi AP interface to the pane on the right alongside LAN1
	NOTE: by default, once you do the above, the router will happily pass traffic from devices on the Wi-Fi AP to other devices on the LAN1 subnet, but will block traffic originating from the Wi-Fi AP from exiting to the Internet via the LTE side of the device. You can clumsily hack around this by setting another device, e.g. another Wi-Fi AP or Raspberry Pi or Cray supercomputer, as the default gateway for the LAN1 subnet in your DHCP server config, and pointing that device at the Zyxel as its default GW. This adds additional hops, but enabl

	js_include conf.d/oauth2.js;

	server {
	listen 80;
	server_name localhost;
	root /usr/share/nginx/html;

	location / {
	auth_request /_auth_init;
	}

	# Working with Altera Quartus II (Q2) and do proper versioning is not that easy
	# but if you follow some rules it can be accomplished. :)
	# This file should be placed into the main directory where the .qpf file is
	# found. Generally Q2 throws all entities and so on in the main directory, but
	# you can place all stuff also in separate folders. This approach is followed
	# here. So when you create a new design create one or more folders where your
	# entities will be located and put a .gitignore in there that overrides the
	# ignores of this file, e.g. one single rule stating "!*" which allows now all
	# type of files. When you add a MegaFunction or another entity to your design,
	# simply add it to one of your private folders and Q2 will be happy and manage

	#!/bin/bash

	SENDGRID_API_KEY=""
	EMAIL_TO=""
	FROM_EMAIL=""
	FROM_NAME=""
	SUBJECT=""

	bodyHTML="<p>Email body goes here</p>"

	#!/usr/bin/ruby

	# THIS FILE IS MANAGED BY PUPPET

	require 'zbxapi'
	require 'pp'

	zbx = ZabbixAPI.new('http://localhost/zabbix/api_jsonrpc.php', verify_ssl: false, http_timeout: 300)
	zbx.login('<%= @admin_user %>', '<%= @admin_password %>')