Welcome To The Node Whisperer Program
Node whisperers explain how (exit/home) nodes work and keep them from misbehaving by troubleshooting, preparing bug fixes, applying patches, implementing new features and upgrading software. To become a node whisperer, you should be able to show someone how to build your own internet by configuring one, (ideally two) home node(s) (see walkthrough) to use a custom, self-created exitnode. This also includes showing how babeld and tunneldigger work together by using (and improving!) babeld-lab and tunneldigger-lab on the home and exit nodes using tools like ip route , ip addr, tcpdump .
notes and discussion
Some folks chat in the #learning channel about topics covered during in-person node-whisperer sessions:
- understanding of ip addresses, internet routing, osi model.
- git / github
ingredients (internet-in-a-box?) a) laptop with ethernet port b) 2 homenodes c) 1 exitnode (locally/remote)
- re-enact packet routing in person by passing pieces of paper around
- show packets arriving at an exit node
- trace packets from a laptop, via a home node to an exit node to the "internet"
- draw the topology of the mesh network using the routing table
- draw the paths packets take in the topology using traceroute
- turn off babeld on both home node and exit node, and use "ip" to manually create routes, recreating the path as seen in 3.
- describe the steps you would take to debug a peoplesopen ssid that does not provide a path to the internet.
- same as 7. but then a path to other home nodes.
- login to a homenode via a exit node
- login to a homenode via public ssid
- re-start tunnel digger (following tunneldigger-lab)