Notes on what I had to do it setup an IPv6 only Ubuntu bionic 20.04 host.
updated: 2020-04-06 (virus times, whatcha gonna do?)
updated: 2020-10-24 (still virus times...)
2022-03-22, Posted as a Gist because it always should've been...
I'm writing this up as a gist, because I'm not sure I'll pursue any of it, but it seems worth writing down.
A basic problem with IPv6-only LANs at the moment is that you still need support for legacy protocol servers, which implies you doing some kind of DNS64 and NAT64 (IPv6-to-IPv4 stateful translation).
Currently, NAT64 only exists outside the kernel, as userspace software. This is not ideal because it limits available performance (since you have to keep bouncing between user space and kernel space),
router id [our IPv4]; | |
protocol bgp vultr | |
{ | |
local as [our ASN]; | |
source address [our IPv4 from vultr]; | |
import all; | |
export filter { | |
if net ~ [[the IPv4 block we want to announce]] then accept; | |
reject; |
silly gist hack, why do we need you? :( |
#!/usr/bin/env python | |
import os | |
import grp | |
import sys | |
import stat | |
import time | |
import hmac | |
import boto3 | |
import tempfile |
04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.
This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.
[Laughter]
> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation
In a project I'm working on I ran into the requirement of having some sort of persistent FIFO buffer or pipe in Linux, i.e. something file-like that could accept writes from a process and persist it to disk until a second process reads (and acknowledges) it. The persistence should be both across process restarts as well as OS restarts.
AFAICT unfortunately in the Linux world such a primitive does not exist (named pipes/FIFOs do not persist
#!/bin/bash | |
URL="http://doxieflashair.local" | |
DIRS="/DCIM/100DOXIE" | |
list () { | |
curl -s "${URL}/command.cgi?op=100&DIR=${1}" \ | |
| awk 'BEGIN { FS=","; OFS="/" } /.+,(.+,){3}/ { print $1,$2 }' | |
} |
#!/bin/bash | |
# | |
# template script for generating CentOS container for LXC | |
# | |
# | |
# lxc: linux Container library | |
# Authors: |