
LAN Orangutan Self-hosted network discovery for homelabbers v3.0.1 is out
𦧠LAN Orangutan v3.0.1 is out. π For anyone who missed it, LAN Orangutan is our self-hosted network...
Tag archive

𦧠LAN Orangutan v3.0.1 is out. π For anyone who missed it, LAN Orangutan is our self-hosted network...
Clear the ARP cache, ping a neighbor, and capture the broadcast 'who has 10.0.0.2?' request and unicast 'is-at' reply that make IPv4 delivery on a link actually work.
Build a path with a 1400-byte bottleneck link, send a 1500-byte Don't-Fragment packet into it, and watch ICMP fragmentation-needed teach the sender the Path MTU β the mechanism that silently breaks when firewalls drop ICMP.
Boot a client with no IP address at all, run a DHCP client against a tiny server, and capture the full Discover-Offer-Request-Ack (DORA) exchange on the wire.
TL;DR: NAT traversal has historically relied on STUN/TURN/ICE running as an external signalling layer...
Build a point-to-point GRE tunnel, ping across the overlay, and capture the underlay to watch IP protocol 47 carry your inner packets in the clear β completing the WireGuard/VXLAN/GRE tunnel trilogy.
Build a real client β r1 β r2 β server path in containers, run traceroute, and capture the ICMP time-exceeded messages that turn a simple loop-prevention field into a hop-by-hop map.
Build a point-to-point VXLAN overlay, ping across it, then capture the underlay and watch the inner ICMP appear in plain text β proof that encapsulation and encryption are two different jobs.
Build a WireGuard tunnel between two containers, then capture the same ping twice β encrypted UDP on the real link, cleartext ICMP inside wg0 β to see exactly where a VPN's encryption applies.
Run a tiny lab CA, sign a server cert and a client cert, then watch a -Verify server accept the client that presents a certificate and reject the one that doesn't β with a 'certificate required' TLS alert.
Sign a DNS zone, validate it with a trust anchor and watch the AD flag appear β then flip one byte of the data and see the resolver reject the answer with SERVFAIL.
Run a single curl command in a container lab and watch it traverse every layer in sequence β DNS resolution, the TCP handshake, TLS 1.3 with SNI and ALPN, and an HTTP/2 200 β captured on the wire.