/explore
|
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? |
|
| | | | | ||
| | | | |
blog.yadutaf.fr
[AI summary] This tutorial explains how to isolate and manage network interfaces using Linux NET namespaces, demonstrating practical implementation with veth pairs and a C program. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
blog.ryanjarv.sh
[AI summary] A blog post explaining the security vulnerability in VirtualBox's default NAT settings that allows guest machines to access the host's loopback interface, and advising users to change the network configuration for proper isolation. |
|
| | | |||
