|
You are here |
vincent.bernat.ch | ||
| | | | |
blog.oddbit.com
|
|
| | | | | Last week, Oskar Stenberg asked on Unix & Linux if it were possible to configure connectivity between two networks, both using the same address range, without involving network namespaces. That is, given this high level view of the network... ...can we set things up so that hosts on the "inner" network can communicate with hosts on the "outer" network using the range 192.168.3.0/24, and similarly for communication in the other direction? | |
| | | | |
yepoleb.github.io
|
|
| | | | | [AI summary] This guide explains how to set up transparent proxying with mitmproxy on a single VM using host-based networking and iptables for efficient traffic redirection and routing. | |
| | | | |
david.newgas.net
|
|
| | | | | [AI summary] A technical guide explaining how to route a single Linux application through a specific VPN using network namespaces, routing rules, and NAT. | |
| | | | |
boucek.me
|
|
| | | FreeBSD 13 does not (yet) contain working Docker machine, although several implementations are on the way. This post explains how to install Docker daemon in Alpine Linux running in Bhyve. It also shows how to create NAT in Bhyve. I have to use NAT, because I use link aggregation (failover) between Wi-Fi and Ethernet. I will use following tools: pf - Packet Filter, part of the base system vm-bhyve, grub2-bhyve - CLI front end for Bhyve tmux - optional, replacement for default cu Networking Link to headin... | ||