Explore >> Select a destination
|
You are here 
|
zserge.com | ||
| | | | |
blog.yadutaf.fr
|
|
| | | | | [AI summary] This article explains the use of Linux namespaces, specifically the NET namespace, to isolate network interfaces and create virtualized network environments for enhanced system management and security. | |
| | | | |
david.newgas.net
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
kittenlabs.de
|
|
| | | There's a number of different ways to distribute an ethernet signal throughout a building. The most common types being: twisted pair wiring fiber optic cable WiFi (2.4 GHz, 5GHz) powerline (also called PLC, IEEE 1901) In my application, running cables wasn't easily possible, so twisted pair and fiber connections were out of the game. PLC-based networking is absolutely unacceptable as a ham radio operator, because these devices produce lots of interference and noise. The distance is a bit too big to utilize "regular" WiFi links, so a different solution was needed. | ||
