Explore >> Select a destination
|
You are here 
|
blog.mbrt.dev | ||
| | | | |
osamaelnaggar.com
|
|
| | | | | My in-depth review of Liz Rice's Container Security book | |
| | | | |
blog.quarkslab.com
|
|
| | | | | [AI summary] The provided text discusses the use of Linux namespaces to isolate network stacks, enabling the creation of isolated environments for processes. It covers topics such as network namespaces, virtual interfaces, bridges, and iptables rules to enable communication between namespaces and the outside world. The text also touches on other namespaces like USER, MNT, UTS, IPC, and CGROUP, and references various resources for further reading. | |
| | | | |
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? | |
| | | | |
gabevenberg.com
|
|
| | | I've been using Arch Linux for several years now. Of course, my first installs were... blunderous, as i wanted to do full disk encryption from the get-go, and I didn't know what I was doing. After those first one or two installs, I generally settled on LVM on LUKS with a GRUB bootloader and my swap on an LVM volume, mostly because it makes it much easier to setup hibernation/suspend to disk vs, say, a swap file. | ||
