A host-only network interface is created virtually in software which appears to the host system.
This interface can be attached to one or more VMs, allowing connectivity between those VMs and communication between the host system and VMs.
| /* Heap based virtual machine described in section 3.4 of Three Implementation Models for Scheme, Dybvig | |
| */ | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| #include <ctype.h> | |
| #include <assert.h> | |
| char token[128][32]; |
| # Author: Kewbit.org | |
| # Description: Hardened TOR-based orchestrator for Docker containers with isolated networking, circuit-level Tor routing, and optional container access control. | |
| set -e | |
| # === GLOBALS === | |
| TOR_GW_NAME="tor-gateway" | |
| DEFAULT_TOR_IP="192.168.100.2" | |
| BRIDGE_PREFIX="kewnet" # Changed for consistent prefix | |
| BASE_SUBNET="192.168" |
A host-only network interface is created virtually in software which appears to the host system.
This interface can be attached to one or more VMs, allowing connectivity between those VMs and communication between the host system and VMs.
These are for the combined vim-sexp (https://github.com/guns/vim-sexp) and vim-sexp-mappings-for-regular-people (https://github.com/tpope/vim-sexp-mappings-for-regular-people) plugins. vim-sexp is neat on its own but Tim Pope makes common stuff much easier.
Note that some vim-sexp functionality depends on <LocalLeader> mappings. This is a different leader key than the global leader, and is the variable maplocalleader (instead of mapleader). To see if you have this set, use :echo maplocalleader; if it errors out you'll need to set it, otherwise it will echo the key. If you want to set your LocalLeader to <Space>, you'll need two commands in your .vimrc, since by default <Space> is bound to <Right> in normal mode:
nnoremap <Space> <Nop>
let maplocalleader=" "