Skip to content

Instantly share code, notes, and snippets.

View aabenitez's full-sized avatar

Alcides Benitez aabenitez

View GitHub Profile
@aabenitez
aabenitez / vm-seal.sh
Last active September 23, 2021 18:21
Seal for clean a VM (machine-id and users log data) for Proxmox - Ubuntu 18.04+
#!/bin/bash
# /usr/local/sbin/vm-seal.sh
unset HISTFILE
apt-get update -y
apt-get upgrade -y
> /etc/machine-id
@aabenitez
aabenitez / gist:186688e70e41f1073316d578f07ac458
Created August 23, 2019 14:49 — forked from leetrout/gist:1810433
UnixBench comparison of EC2, Joe's Data Center, and Rackspace CloudServers
apt-get install -y build-essential libx11-dev libgl1-mesa-dev libxext-dev perl perl-modules make
cd /tmp
wget https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/byte-unixbench/UnixBench5.1.3.tgz
tar xzvf UnixBench5.1.3.tgz
cd UnixBench
./Run
Proxmox on Debian at Hetzner with multiple IP addresses
AUGUST 9, 2016 BY FLORIAN BEER·15 COMMENTS
I’ve spent most of my day today trying a plethora of different ways on how to configure Proxmox on a Hetzner server with multiple IP addresses. Most of the tutorials I found online gave a good deal of information but where lacking in one or two crucial details. Shortly before I was ready to throw my computer out of the window, I had success and managed to get everything set up the way I wanted it.
This aims to be the definitive guide on how to accomplish the aforementioned task. When ready the setup includes the following features:
Host bound to main IPv4 address, that comes with the server (and one of the 18,446,744,073,709,551,616 included IPv6 addresses)
Every IPv4 address of a separately delegated subnet usable for virtual machines
Internal private network for inter-virtual machine communication and non publicly accessible VMs