# LAN Published articles for LAN. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## VLANs explicadas: segmenta tu red DevFeed: [VLANs explicadas: segmenta tu red]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-07-27T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Homelab](), [Ethernet](), [Linux](), [interfaces](), [Hardware]() Tags: [ethernet](), [homelab](), [interfaces](), [lan](), [linux](), [vlan]() ### AI overview This tutorial explains how VLANs divide one physical network into separate logical networks. It covers 802.1Q tagging, VLAN IDs, access and trunk ports, PVIDs, and configuring VLANs on managed switches and Linux for homelab network segmentation. ### Source excerpt Qué son las VLANs y el etiquetado 802.1Q, cómo configurarlas en un switch gestionado y en Linux, y cuándo merece la pena segmentar tu red de homelab. ## Pi-hole: bloquea publicidad en toda tu red DevFeed: [Pi-hole: bloquea publicidad en toda tu red]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-04T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Pi-hole](), [DHCP](), [Raspberry Pi](), [Linux](), [Debian](), [Ubuntu]() Tags: [cloudflare](), [debian](), [dhcp](), [dns](), [lan](), [linux](), [local](), [pi](), [raspberry-pi](), [resolver](), [router](), [script](), [settings](), [ubuntu]() ### AI overview A Spanish tutorial explaining how Pi-hole filters advertising and tracking domains through local DNS, how to install it on a Raspberry Pi or Linux system, configure it on a router, use DHCP when necessary, and resolve local network names. ### Source excerpt Pi-hole a fondo: por qué el DoH del navegador lo esquiva, DNS local para tu LAN, Teleporter y qué revisar si no bloquea. ## Analysis of PPPP "encryption" DevFeed: [Analysis of PPPP "encryption"]() Original publisher: [Read original article]() Author: Wladimir Palant Published: 2026-01-05T15:50:53Z Content type: article Language: en Sources: [Almost Secure]() Topics: [Encryption](), [Cryptography](), [Network](), [Protocol (disambiguation)](), [Algorithms]() Tags: [analysis](), [ascii](), [cryptanalysis](), [encryption](), [lan](), [network](), [pull-request](), [theory]() ### AI overview This analysis examines weaknesses in PPPP "encryption." It explains that app keys are reduced to a four-byte effective key and that the scheme is vulnerable to known-plaintext attacks. For LAN camera discovery when the app and traffic are unknown, the article describes sending all possible encrypted search packets, with at most 157,092 ciphertexts, and notes a pull request to update the device-detection script. ### Source excerpt My first article on the PPPP protocol already said everything there was to say about PPPP "encryption": Keys are static and usually trivial to extract from the app. No matter how long the original key, it is mapped to an effective key that's merely four bytes long. The "encryption" is extremely susceptible to known-plaintext attacks, usually allowing reconstruction of the effective key from a single encrypted packet. So this thing is completely broken, why look any further? There is at least one situation where you don't know the app being used so you cannot extract the key and you don't have any traffic to analyze either. It's when you are trying to scan your local network for potential hidden cameras. This script will currently only work for cameras using plaintext communication. Other cameras expect a properly encrypted "LAN search" packet and will ignore everything else. How can this be solved without listing all possible keys in the script? By sending all possible ciphertexts of course! TL;DR: What would be completely ridiculous with any reasonable protocol turned out to be quite possible with PPPP. There are at most 157,092 ways in which a "LAN search" packet can be encrypted. I've opened a pull request to have the PPPP device detection script adjusted. Note: Cryptanalysis isn't my topic, I am by no means an expert here. These issues are simply too obvious. Contents Mapping keys to effective keys Redundancies within the effective key ASCII to the rescue How large is n? How many ciphertexts is that? Understanding the response Mapping keys to effective keys The key which is specified as part of the app's "init string" is not being used for encryption directly. Nor is it being fed into any of the established key stretching algorithms. Instead, a key represented by the byte sequence b1,b2,...,bnb_1, b_2, \ldots, b_n is mapped to four bytes k1,k2,k3,k4k_1, k_2, k_3, k_4 that become the effective key. These bytes are calculated as follows (⌊x⌋\lfloor x \rfloor means r ## Arista EOS Spooky Action at a Distance DevFeed: [Arista EOS Spooky Action at a Distance]() Original publisher: [Read original article]() Published: 2025-03-17T08:10:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Integration testing](), [Ethernet](), [qemu](), [Linux](), [JSON]() Tags: [blog](), [blog-post](), [ethernet](), [integration-testing](), [ipv4](), [json](), [lan](), [linux](), [netlab](), [qemu](), [testing](), [tests](), [validation](), [virtualization]() ### AI overview This blog post investigates unexpected Arista EOS behavior found during netlab VRRP integration testing. In a minimal lab, shutting down one switch interface caused the other switch's Ethernet line protocol to go down and stopped responses from the VRRP backup. Packet capture indicated that the first switch sent a packet instructing the peer to emulate remote link loss. ### Source excerpt This blog post describes yet another bizarre behavior discovered during the netlab integration testing. It started innocently enough: I was working on the VRRP integration test and wanted to use Arista EOS as the second (probe) device in the VRRP cluster because it produces nice JSON-formatted results that are easy to use in validation tests. Everything looked great until I ran the test on all platforms on which netlab configures VRRP, and all of them passed apart from Arista EOS (that was before we figured out how Sturgeon's Law applies to VRRPv3) - a "That's funny" moment that was directly responsible for me wasting a few hours chasing white rabbits down this trail. Read more ... ## Lab: IS-IS Designated Router Election DevFeed: [Lab: IS-IS Designated Router Election]() Original publisher: [Read original article]() Published: 2025-03-13T07:03:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [IS-IS]() Tags: [is-is](), [lan](), [netlab](), [ospf](), [router](), [standards]() ### AI overview This lab article explains that IS-IS uses a Designated Intermediate System (DIS) router to originate the pseudo-node for a LAN segment. Unlike OSPF, the DIS does not need a backup because it is not responsible for flooding. ### Source excerpt Like OSPF, IS-IS needs a router to originate the pseudo-node for a LAN segment. IS-IS standards call that router a Designated Intermediate System (DIS), and since it is not responsible for flooding, it does not need a backup. Want to know more? The Influence the Designated IS Election lab exercise provides the details (and some hands-on work). ## Capturing Traffic in Virtual Networking Labs DevFeed: [Capturing Traffic in Virtual Networking Labs]() Original publisher: [Read original article]() Published: 2025-03-04T06:43:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Linux](), [qemu](), [virtual machines](), [Containers](), [Docker]() Tags: [capture](), [container](), [containers](), [docker](), [lan](), [linux](), [netlab](), [networking](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview A tutorial on capturing traffic in virtual networking labs. It explains how to capture traffic from Linux bridges and QEMU-connected virtual machines, use netlab capture as a wrapper around virsh, brctl, and tcpdump, and approach traffic capture for containers attached to Docker networks or Linux bridges. ### Source excerpt When I announced the Stub Networks in Virtual Labs blog post on LinkedIn, I claimed it was the last chapter in the "links in virtual labs" saga. I was wrong; here comes the fourth part of the virtual links trilogy - capturing "on the wire" traffic in virtual networking labs. While network devices provide traffic capture capabilities (usually tcpdump in disguise generating a .pcap file), it's often better to capture the traffic outside of the device to see what the root cause of the problems you're experiencing might be. Read more ... ## Why VLAN 1 Should Not Be Tagged in a Trunk DevFeed: [Why VLAN 1 Should Not Be Tagged in a Trunk]() Original publisher: [Read original article]() Published: 2025-02-11T07:05:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Ethernet](), [DHCP](), [Cisco]() Tags: [bridging](), [cisco](), [dhcp](), [ethernet](), [lan](), [netlab](), [network](), [security]() ### AI overview The article examines conflicting interpretations of VLAN 1 in trunks by Cumulus NVUE and Arista EOS. It recommends avoiding VLAN 1 in VLAN trunks and using it as the native VLAN when necessary, while explaining the historical and operational reasons behind this behavior. ### Source excerpt It all started with a netlab issue describing different interpretations of VLAN 1 in a trunk. While Cumulus NVUE (the way the netlab configuration template configures it) assumes that the VLAN 1 in a trunk is tagged, Arista EOS assumes it's the native VLAN. At that point, I should have said, "that's crazy, we shouldn't allow that" and enforce the "VLAN 1 has to be used as a native VLAN" rule. Alas, 20/20 hindsight never helped anyone. TL&DR: Do not use VLAN 1 in VLAN trunks; if you have to, use it as a native VLAN. Read more ... ## The Ethernet/802.1 Protocol Stack DevFeed: [The Ethernet/802.1 Protocol Stack]() Original publisher: [Read original article]() Published: 2025-01-22T07:28:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Ethernet](), [Protocol (disambiguation)]() Tags: [ethernet](), [gigabit-ethernet](), [lan](), [protocol](), [provisioning](), [reconciliation]() ### AI overview An explanation of the Ethernet and IEEE 802.1 protocol stack, including the MAC and LLC sublayers, physical-layer subdivisions, and the placement of discovery, link aggregation, spanning tree, VLAN, and provisioning protocols. ### Source excerpt The believers in the There Be Four Layers religion think everything below IP is just a blob of stuff dealing with physical things: People steeped in a slightly more nuanced view of the world in which IP is not the centerpiece of the universe might tell you that the blob of stuff we need is two things: Read more ... ## Attacking UNIX Systems via CUPS, Part I DevFeed: [Attacking UNIX Systems via CUPS, Part I]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2024-09-26T14:51:30Z Content type: article Language: en Sources: [evilsocket]() Topics: [vulnerability](), [Security](), [Unix](), [Exploit](), [gnu linux](), [systems]() Tags: [bugs](), [cups](), [cups-browsed](), [cve](), [cve-2024-47076](), [cve-2024-47175](), [cve-2024-47176](), [cve-2024-47177](), [cybersecurity](), [disclosure](), [exploit](), [gnu-linux](), [hacking](), [ipp](), [lan](), [linux-security](), [mdns](), [no-authentication](), [port](), [print-services](), [printer](), [printers](), [printing](), [rce](), [responsible-disclosure](), [security](), [udp](), [unauthenticated-access](), [unix](), [vulnerability-research](), [zeroconf]() ### AI overview A security writeup describes multiple vulnerabilities in CUPS components affecting GNU/Linux and other UNIX systems. It reports that remote unauthenticated attackers may replace printer IPP URLs and trigger arbitrary command execution when a print job starts, with attacks possible over the public internet or via spoofed LAN advertisements. ### Source excerpt Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start ## Using wemulate with netlab DevFeed: [Using wemulate with netlab]() Original publisher: [Read original article]() Published: 2024-04-02T05:49:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Containers](), [Linux](), [Docker]() Tags: [bash](), [container](), [containers](), [distributed](), [docker](), [ipv4](), [lan](), [linux](), [netlab](), [networking]() ### AI overview This tutorial shows how to use wemulate with netlab to build a container-based virtual WAN network. It explains how wemulate connects container interfaces with Linux bridges, how to configure static IPv4 prefixes, and how to add jitter before testing connectivity between hosts. ### Source excerpt An RSS hiccup brought an old blog post from Urs Baumann into my RSS reader. I'm always telling networking engineers that it's essential to set up realistic WAN environments when testing distributed software, and wemulate (a nice tc front-end) seemed like a perfect match. Even better, it runs in a container - an ideal component for a netlab-generated virtual WAN network. wemulate acts as a bump in the wire; it uses Linux bridges to connect two container interfaces. We'll use it to introduce jitter into an IP subnet: ┌──┐ ┌────────┐ ┌──┐ │h1├───┤wemulate├───┤h2│ └──┘ └────────┘ └──┘ ◄──────────────────────► 192.168.33.0/24 Read more ... ## How IX.BR Automates Quarantine LAN Testing DevFeed: [How IX.BR Automates Quarantine LAN Testing]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2024-02-01T11:27:29Z Content type: article Language: en Sources: [benjojo blog]() Topics: [Network](), [Ethernet](), [Internet Traffic](), [DDoS](), [proxy](), [Testing]() Tags: [arp](), [bgp](), [ethernet](), [internet](), [internet-traffic](), [lan](), [proxy](), [tests]() ### AI overview The article describes IX.BR São Paulo's automated quarantine LAN testing portal for internet exchange participants. It explains why quarantine testing matters, including the risks of Ethernet loops, management frames, and Proxy ARP on a shared Layer 2 exchange LAN. ### Source excerpt Appreciation of automated IX Quarantine LAN testing Something that bgp.tools (my company) does a great deal is joining internet exchanges. ## Configuring VLANs, Firewall Rules, and WiFi Networks - UniFi Network Application DevFeed: [Configuring VLANs, Firewall Rules, and WiFi Networks - UniFi Network Application]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-03-04T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [networking](), [Firewall](), [Security](), [Ubiquiti]() Tags: [firewall](), [homelab](), [lan](), [network](), [security](), [unifi](), [wireless]() ### AI overview This tutorial explains how to configure VLANs with the UniFi Network Application, including creating a network, setting up a wireless network that uses VLANs, and adding firewall rules. It also describes how VLANs can improve security, performance, management, and flexibility for home networks. ### Source excerpt What is a VLAN and How Do They Help? Today we're going to cover setting up VLANs using UniFi's network controller.We'll set up a VLAN, from start to finish, which includes creating a new network, configuring a wireless network that uses VLANs, and then we'll set up firewall rules to make sure we're keeping our network safe. If you think VLANs are only for the enterprise, you're wrong, I will s... ## How to Configure Wake on LAN Across Windows, macOS, and Linux DevFeed: [How to Configure Wake on LAN Across Windows, macOS, and Linux]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-02-19T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [networking](), [Network](), [Linux](), [macOS](), [Windows](), [boot]() Tags: [guide](), [hardware](), [how-to](), [lan](), [linux](), [macos](), [network](), [networking](), [pikvm](), [utilities](), [windows]() ### AI overview A practical guide to configuring Wake on LAN across Windows, macOS, and Linux. It explains how WoL uses a magic packet to wake a machine and discusses the BIOS settings that may need to be enabled or disabled for different hardware and power states. ### Source excerpt What is Wake on LAN and why is it so hard? After releasing my video on the PiKVM I realized that there was so much confusion about Wake on LAN, and rightfully so, that I decided to put together this guide on how to configure Wake on LAN on any machine. Wake on LAN (WoL) is a networking standard that allows a computer to be turned on by sending a network packet. The client sends a special packe... ## Capture the Flag events and eSports DevFeed: [Capture the Flag events and eSports]() Original publisher: [Read original article]() Author: Jonathan Marcil Published: 2019-09-11T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Sports]() Tags: [competition](), [events](), [games](), [lan](), [sports](), [strategy](), [team]() ### AI overview The article compares Capture the Flag events with eSports and argues that CTFs are intrinsically an eSport with strong educational value. It describes eSports audiences, broadcasts, competition, professional gaming, and amateur LAN and online events. ### Source excerpt A breakdown of CTFs and eSports ## Networking for a Bare-Metal Kubernetes Cluster After AWS DevFeed: [Networking for a Bare-Metal Kubernetes Cluster After AWS]() Original publisher: [Read original article]() Author: ev@goteleport.com (Ev Kontsevoy) Published: 2019-05-14T15:39:34Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Kubernetes](), [networking](), [Amazon Web Services](), [cloud-infrastructure](), [Containers](), [Software-defined networking]() Tags: [aws](), [bare-metal](), [hardware](), [ip](), [k8s](), [kubernetes](), [lan](), [networking](), [router](), [sdn]() ### AI overview This article explains how to design a simple, non-redundant network for a small bare-metal Kubernetes environment in a colocation facility after leaving AWS. It discusses network complexity, legacy limitations, SDN concepts, public subnet routing, and separate private LANs for management, security, and performance. ### Source excerpt This is part three of a three-part series on considerations that companies will want to address if they decide to build their own cloud environment. ## Statystyki odwiedzin dla wielu serwisów z AWStats DevFeed: [Statystyki odwiedzin dla wielu serwisów z AWStats]() Original publisher: [Read original article]() Author: Tom Published: 2011-08-29T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [HTTP](), [servers](), [Open Source](), [Mod\_rewrite]() Tags: [analytics](), [apache](), [debian](), [http](), [lan](), [linux](), [mod-rewrite](), [open-source](), [rewrite](), [sites]() ### AI overview A Polish tutorial explains how to install and configure AWStats to analyze HTTP server logs for multiple websites. It discusses Apache CGI setup and restricting access to local networks or other authorized users. ### Source excerpt Co prawda na swojej stronie zrobiłem kilka podstawowych statystyk i coś tam sobie loguję do bazy danych, ale gdyby się chwilę zastanowić to przecież to samo robi serwer www - wrzuca do logów każde zapytanie HTTP, kod błędu, nazwę agenta, itd. Dublowanie tych danych nie jest najbardziej optymalne. Stąd też chwilę pogooglałem i znalazłem świetny Open Source'owy projekt: AWStats, który jest webowym analizatorem logów dla serwerów HTTP, FTP i SMTP.