How russelltao/protocol-2day-training works
Project type and purpose
• This repo is not a typical application but a set of training materials and packet‐capture artifacts for a “2-day network protocol” workshop.
• It collects PCAP/PKT files for various layers (ARP, TCP, HTTP1/2/3, TLS, QUIC, Kubernetes vxlan overlay), plus a PDF on software architecture and a simple Python script.
File structure
• Top-level artifacts: dozens of .pcapng / .pkt capture files named by lesson (l2-…, l10-…, l15-…), a flannel.yaml (CNI config), one Python example script (l14-broadcast_send.py), and a .pdf on architecture styles.
• No traditional “src” or “lib,” but the presence of flannel.yaml and detailed capture instructions in the README point at a Kubernetes + flannel overlay testbed.
README
• Describes how to install capture tools (Wireshark, tcpdump), gives pointers to network / HTTP / TLS / QUIC / ASCII reference materials, and shows a “k8s capture environment” using veth pairs, bridges (cni0), vxlan (flannel.1) overlay atop an L3 underlay.
• Clearly defines Underlay vs. Overlay addresses, show how to find the right veth interface for a given pod.
Main components
a. Physical Hosts (could be VMs) running Linux
b. Underlay Network (eth0 on each host, IP range 172.27.0.0/20)
c. Linux Bridge “cni0” (and docker0) on each host
d. Flannel VXLAN Overlay (flannel.1) on each host, carrying Pod CIDR (10.244.0.0/16)
e. Kubernetes Master & Worker Nodes
f. Pods / Containers with their eth0 interfaces, each linked via a veth pair into cni0
g. Tools (tcpdump/Wireshark) tapping at selected veth or flannel interfaces
h. Data artifacts: lesson PCAP files, Python script, flannel config, architecture PDF
Relationships & interactions
• Pod-to-Pod traffic on the same host: container eth0 → veth pair → cni0 → flannel.1 (via VXLAN) → cni0 → veth → target container.
• Cross-host Pod traffic: container → veth → cni0 → flannel.1 encapsulate in VXLAN → eth0 → network switch → eth0 on other host → flannel.1 de-encapsulate → cni0 → target container.
• Points: annotate tcpdump on vethXXXXX and flannel.1 to illustrate Underlay vs. Overlay captures.
Architectural patterns & design principles
• Layered network architecture: separate Underlay (physical IP/MAC) from Overlay (VXLAN, Pod IP/MAC).
• Control plane vs. data plane: Kubernetes API & etcd on master vs. packet forwarding in flannel agent on each node.
• Use of CNI plugin for container networking, micro-segmentation by Pod CIDRs.
Relevant technologies & files
• Linux bridging (bridge-utils), veth pairs
• Flannel CNI (config in flannel.yaml) over VXLAN
• Kubernetes Pods (represented by IPs in captures)
• Tools: tcpdump, Wireshark, Python (for small broadcast script)
• PCAP/PKT lesson recordings as evidence / test vectors
Essential details
• Clear component labels (Host A / Node1, Host B / Node2, Master Node, Worker Node)
• Interface names + IP/MAC examples