Explore >> Select a destination
|
You are here 
|
debianaddict.com | ||
| | | | |
blog.coffinsec.com
|
|
| | | | | While working on berry-sense and learning about network traffic analysis recently, I had the need for a dedicated device to use as an Ethernet bridge/tap for capturing traffic. This would give me a chance to test the Raspberry Pi's performance while performing traffic captures, as well as produce a usable device for performing simple captures. | |
| | | | |
nbailey.ca
|
|
| | | | | Kubernetes is our generation's Asbestos. | |
| | | | |
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. | |
| | | | |
hjr265.me
|
|
| | | I have lines like these in my /etc/hosts file: 127.0.0.1 toph.local 127.0.0.1 drafts.toph.local 127.0.0.1 quiz.toph.local I can run development servers locally and access them over .local hostnames (e.g. toph.local) instead of the loopback IP addresses (e.g. 127.0.0.1). It works fine. But every time I start working on a new project, I needed to add a new line to the /etc/hosts file. It didn't sit right with me. I should be able to point all *. | ||
