2026-07-22T12:26:50Z https://nostr.ae davidgtl https://nostr.ae/npub1eawzd42kvx0rgtn9qv2lxzxaqf9nnm3ghecxql2yhcsc02gclrpqzt8ufd https://pleroma.davidgtl.me/media/bbd1d274-7fe7-43d2-be5f-2b8afa0ad82b/blob https://pleroma.davidgtl.me/media/bbd1d274-7fe7-43d2-be5f-2b8afa0ad82b/blob https://nostr.ae/nevent1qqs245qcrm80ku932vapn0anutn4ww9gvlh3flmyekxemyt69dte5cszyr84cfk42eseudpwv5p3tucgm5pykw0w9zl8qcragjlzrpafrruvytcqpxu In reply to <a href='/nevent1qqstj3nzthrlr38t6erp95ef6t9gdxjsre4awtwfxwszyrrds9enyuskmvu94'>nevent1q…vu94</a><br/>_________________________<br/><br/>Looks interesting! <br/> <br/>When I took a networking class at uni, a significant time was spent in the router&#39;s shell doing things like messing with vlans, dhcp, etc. So unless I missed it an advanced tab would be great <br/> <br/>On a personal note, what I think would be cool is replicating a production environment as a default, i.e. have an ISP which hosts a DNS resolver (which is always out of date :)) ), drag &amp; drop some wiresharks on specific wires to see the traffic through that wire, a STUN server/IP:port echoer to show hole punching, mess with Route tables and see a TTL go down and the packet get dropped, etc. 2026-07-21T11:52:22Z