Guide 065 min readFrameAssembly v3.1.2
llms-full.txt

CLI Cheat Sheet, Address Formats & Common Gotchas

Every frameassembly v3.1.2 terminal command, accepted IP/MAC/OID format, typo fix, and why .frasm has nothing to do with x86 Flat Assembler (fasm).

TL;DR — What Matters Here
  • Positional paths all the way: frameassembly in.frasm [out.pcap|.pcapng], show, reverse, help, version — zero -o flags, zero compile subcommand.
  • Paste MACs straight out of Cisco IOS (001a.2b3c.4d5e), Windows (00-1A-2B-3C-4D-5E), or Linux (00:1a:2b:3c:4d:5e).
  • .frasm = FrameAssembly packet captures (text/vnd.frameassembly). .fasm = x86 Flat Assembler CPU opcodes. Totally different beasts.

1. Every CLI Command on One Card (v3.1.2)

The frameassembly binary is a single static Rust executable on Windows, macOS, and Linux — zero Python, zero libc drama, zero network permissions:

Terminal Commands (FrameAssembly CLI v3.1.2)
# Compile -> inspect in tshark -> round-trip reverse back to .frasm
frameassembly lab.frasm lab.pcapng
tshark -r lab.pcapng
frameassembly reverse lab.pcapng lab_copy.frasm
CommandWhat Happens
frameassembly demo.frasmCompiles demo.frasm -> demo.pcap in the same directory.
frameassembly demo.frasm out.pcapCompiles demo.frasm -> out.pcap (microsecond libpcap 0xa1b2c3d4 for tcpdump, tcpreplay, Suricata, and Zeek).
frameassembly demo.frasm out.pcapngCompiles demo.frasm -> out.pcapng (nanosecond IfTsResol=9 for Wireshark and tshark).
frameassembly show demo.frasmValidates and prints the relative-timestamp packet ladder to stdout without writing files.
frameassembly reverse capture.pcap [out.frasm]Decompiles .pcap or .pcapng -> .frasm (host1, host2, ...).
frameassembly help [subcommand] / frameassembly versionPrints CLI usage or version string.

2. IP, MAC, Hex & OID Formats You Can Paste Directly

Copy-paste addresses straight from show mac address-table, ipconfig /all, or ip addr without reformatting:

Literal TypeValid ExamplesNotes
User names (host, flow)client, Core_SW_1, fw-dmz-01Letters, digits, underscores, and internal hyphens.
IPv4 & IPv6 literals10.0.0.1, 2001:db8::1, fe80::1Plain host addresses — no /24 or /64 prefix lengths.
Ethernet MAC literals00:1a:2b:3c:4d:5e, 00-1A-2B-3C-4D-5E, 001a.2b3c.4d5eAuto-derived when omitted (00:00:00:00:00:01, RFC multicast MACs, or IEEE L2 group MACs).
Integers & hex numbers443, 0x0806, 0x1a2bDecimal or 0x hex; signed negatives allowed on ntp precision, ldap msgid, kerberos etype, and SNMP int.
Hex byte stringshexpayload "deadbeef", hexpayload "de:ad:be:ef"Even-length hex octets (spaces or colons fine); mutually exclusive with payload "...".
SNMP OIDs1.3.6.1.2.1.1.1.0 or .1.3.6.1.2.1.1.1.0Unquoted numeric trees (>= 2 arcs) or double-quoted strings.

3. Five Muscle-Memory Typos & Their Instant Fixes

Mistype a keyword and the compiler’s edit-distance suggester usually tells you the exact fix (Did you mean echorequest?). Here are the top five classics:

Muscle-Memory TypoValid v3.1.2 .frasmWhy
a -> b icmp echo_requesta -> b icmp echorequestBuilt-in keywords are strictly [a-z0-9]+ with zero underscores.
Standalone wait 10ms linea -> b icmp echorequest wait 10mswait is a post-packet suffix on the frame that precedes the gap.
a -> b tcp ack 1001a -> b tcp ack acknum 1001Bare ack = ACK flag bit; acknum = 32-bit acknowledgment number.
a -> b http get host "x.test"a -> b http get hosthdr "x.test"host declares top-level boxes; hosthdr sets HTTP / SSDP Host:.
flow ping { ... } or loop 5 { ... }flow ping(a, b) { ... } called inside compile { ... }flow always takes parameters in parentheses; repeat calls in compile instead of loop.

4. Name Check: .frasm (Packets) vs. .fasm (x86 Assembly)

FrameAssembly uses .frasm (text/vnd.frameassembly) to compile and decompile network packet captures (.pcap <-> .pcapng). It has zero connection to Flat Assembler (fasm), Tomasz Grysztar’s classic x86/x86-64 CPU assembler (.asm/.fasm, ; comments), or SymbiFlow FPGA .fasm files.

Quick Notes & Edge Cases

How do I stop ChatGPT / Claude / Gemini from inventing fake underscored keywords?

Grab llms-full.txt from the top navbar (https://frameassembly-lang.dev/llms-full.txt) and drop it into your prompt. It hands the LLM the exact v3.1.2 grammar and all 81 protocol modifiers so it stops hallucinating echo_request or -o flags.