dash did not like my "${ve_br_orig::15}" in ./lib.shs:69 (nice) |
2 weeks ago | |
---|---|---|
machines | 2 weeks ago | |
networks | 2 weeks ago | |
state | 3 weeks ago | |
LICENSE | 2 weeks ago | |
README.md | 2 weeks ago | |
cleanup.sh | 2 weeks ago | |
init-shim.sh | 2 weeks ago | |
init.sh | 2 weeks ago | |
lib.shs | 2 weeks ago |
README.md
Net horror
Do not use.
This is an attempt to re-create my own network (or rather, a network that has many of the same quirks) in network namespaces in order to be able to test stuff.
Documentation
On some papers on my desk, unless lost completely.
Take xkcd 350 as documentation instead :-P
How it happened
Badly. I had a need for a toy copy/approximation of my infrastructure, no internet connection and a computer with util-linux
, iproute2
and local copies of all the RFCs. Turns out you can do too much with that…
Complaints?
Probably not accepted. Especially if you are going to moan about how there are “secrets” (e.g. wireguard private keys) stored directly in the git repository. (If you can hack into a local network namespace, there are bigger problems than you also getting to a purely-local wireguard tunnels…)
TODO
- DNS
- Dynamic routing
- Interesting network layers (SCTP? PPP over a serial port/named FIFO?)
- Dynamic address assignment
- network booting and diskless machines
- Horrible networks that use all of the RFC 1918 IPv4 addresses in the inside infra (gateways, DNS servers) and therefore clash with any/most private network on the host
- Firewalls