
The Shell and the Filesystem: Reading Any Path (Linux CLI 101, Lesson 1)
A shell reads the commands you type and runs them. Linux keeps every file in one tree that starts at /. The prompt, commands and their options, …
15 entries

A shell reads the commands you type and runs them. Linux keeps every file in one tree that starts at /. The prompt, commands and their options, …

A packet capture is a recording of the frames that crossed one point in the network. Wireshark's three panes, timestamps, pcap vs pcapng, and why …

Capture filters decide what's saved and can't be undone. Display filters decide what you see. BPF vs Wireshark fields, contains and matches, and why …

Most of what you do on Linux is reading and changing text files: logs, configs, inventories. How to read them with cat, less, head and tail -f, edit …

ARP turns an IP address into a MAC address with one broadcast question and one unicast answer. The fields, the neighbor cache, ARP for the gateway, …

Every Linux command reads from stdin and writes to stdout and stderr. Redirect those streams to files, pipe one command into the next, and grep, sort …

DHCP in packets: four messages sent before the host has an address, the options that matter, leases and renewal, and how a relay with ip …

Every Linux file has an owner, a group and nine permission bits. Read them in ls -l, set them with chmod as 644, 755 or 600, see why SSH ignores a key …

A DNS lookup is two UDP packets matched by a transaction ID. How to read the flags, the reply codes, A, AAAA and CNAME records and TTLs in Wireshark, …

Every running program is a process with a number. How to run jobs in the background, find a process that's eating a CPU and stop it, what TERM and …

SSH gives you a shell on another machine over an encrypted connection. Host keys, known_hosts, what 'host key changed' means, key pairs and …

One web page is twelve TCP frames. How to read the handshake, sequence and acknowledgement numbers, the window and SYN options in Wireshark, how a …

HTTPS hides the page, not the handshake. What Wireshark still reads in TLS 1.2 and 1.3: the server name, versions, ciphers, ALPN and certificate, why …

When a service answers on the server but not from anywhere else, five commands find out why: which way the packet goes, what's listening on which …

Capture at two points at once and follow one packet: the fault is between the last place you see it and the first you don't. How loss, a silent ACL …