Skip to content

Images

Every image in the repository, in one place and by kind. The pages use them from here, and so does the wiki, which keeps no images of its own. Each photograph was taken on the appliances themselves; what each one shows is the alt text its page gives it, and the pages that use it are named beside it.

This page is written by tools/images-index.py, and the checks fail when it is out of date: add an image to its folder, use it on a page, and run the tool.

Licence. The photographs and screenshots are © 2026 Abdelmonem Awad, under CC BY 4.0: use them freely, naming the author and linking here. Each carries that notice in a strip added below it - never over the picture, so a measurement is still what the screen showed - and in its metadata: tools/mark-images.py adds both to a new image, and the checks fail on one without them.

folder what it holds images
screens/ The web interface, page by page, in English and in Arabic 62
hardware/ Photographs and drawings of the appliances, one folder each 40
measurements/ Each measurement's photographs, in a folder named after its page 192
readme/ The README's banner and status board, drawn by tools/readme-art.py 4

298 images in all.

The web interface

Full screen, dark theme, photographed on 2026-10-19 on the second XGS 3300. Each page is described in docs/guide/the-pages.md, English first and Arabic under it.

pageEnglishArabic
Lobby: Dashboard on an XGS 3300Lobby: Dashboard on an XGS 3300 - EnglishLobby: Dashboard on an XGS 3300 - Arabic
XGS: Overview on an XGS 3300: the front panel drawn with each port's link, cards for the coprocessor, hardware offloading, the IPsec engine, the front ports, the switch chip and the last restart, and the board's limitsXGS: Overview on an XGS 3300: the front panel drawn with each port's link, cards for the coprocessor, hardware offloading, the IPsec engine, the front ports, the switch chip and the last restart, and the board's limits - EnglishXGS: Overview on an XGS 3300: the front panel drawn with each port's link, cards for the coprocessor, hardware offloading, the IPsec engine, the front ports, the switch chip and the last restart, and the board's limits - Arabic
XGS: Settings on an XGS 3300XGS: Settings on an XGS 3300 - EnglishXGS: Settings on an XGS 3300 - Arabic
XGS: Settings on an XGS 3300, further down: Never offloaded, Cut open connections when listed, Cut connections by TLS fingerprintXGS: Settings on an XGS 3300, further down: Never offloaded, Cut open connections when listed, Cut connections by TLS fingerprint - EnglishXGS: Settings on an XGS 3300, further down: Never offloaded, Cut open connections when listed, Cut connections by TLS fingerprint - Arabic
XGS: Settings on an XGS 3300: the flow maker, and the two settings that count hardware traffic in pf and on the interfacesXGS: Settings on an XGS 3300: the flow maker, and the two settings that count hardware traffic in pf and on the interfaces - EnglishXGS: Settings on an XGS 3300: the flow maker, and the two settings that count hardware traffic in pf and on the interfaces - Arabic
XGS: Ports on an XGS 3300XGS: Ports on an XGS 3300 - EnglishXGS: Ports on an XGS 3300 - Arabic
XGS: Transceivers on an XGS 3300XGS: Transceivers on an XGS 3300 - EnglishXGS: Transceivers on an XGS 3300 - Arabic
XGS: IPsec on an XGS 3300XGS: IPsec on an XGS 3300 - EnglishXGS: IPsec on an XGS 3300 - Arabic
XGS: IPsec, Associations in the engine: one association each way through the tunnel to the XGS 136XGS: IPsec, Associations in the engine: one association each way through the tunnel to the XGS 136 - EnglishXGS: IPsec, Associations in the engine: one association each way through the tunnel to the XGS 136 - Arabic
XGS: IPsec, Counters: frames decrypted and encrypted by the engineXGS: IPsec, Counters: frames decrypted and encrypted by the engine - EnglishXGS: IPsec, Counters: frames decrypted and encrypted by the engine - Arabic
XGS: Offloaded Flows on an XGS 3300XGS: Offloaded Flows on an XGS 3300 - EnglishXGS: Offloaded Flows on an XGS 3300 - Arabic
XGS: Updates on an XGS 3300XGS: Updates on an XGS 3300 - EnglishXGS: Updates on an XGS 3300 - Arabic
XGS: Problem Reports on an XGS 3300XGS: Problem Reports on an XGS 3300 - EnglishXGS: Problem Reports on an XGS 3300 - Arabic
XGS: Log File on an XGS 3300XGS: Log File on an XGS 3300 - EnglishXGS: Log File on an XGS 3300 - Arabic
Reporting: Network Report on an XGS 3300Reporting: Network Report on an XGS 3300 - EnglishReporting: Network Report on an XGS 3300 - Arabic
System: Fan Control on an XGS 3300System: Fan Control on an XGS 3300 - EnglishSystem: Fan Control on an XGS 3300 - Arabic
System: Front Panel on an XGS 3300System: Front Panel on an XGS 3300 - EnglishSystem: Front Panel on an XGS 3300 - Arabic
Interfaces: Link Health on an XGS 3300Interfaces: Link Health on an XGS 3300 - EnglishInterfaces: Link Health on an XGS 3300 - Arabic
The image builder's pageThe image builder's page - EnglishEnglish only
The image builder's form: the release, the image type and the consoleThe image builder's form: the release, the image type and the console - EnglishEnglish only

Hardware

hardware/bench/ - The bench the appliances are measured on (1)

The bench: the XGS 136 at the top, the second XGS 3300 in the middle with its 4x10G module, the first XGS 3300 at the bottom
The bench: the XGS 136 at the top, the second XGS 3300 in the middle with its 4x10G module, the first XGS 3300 at the bottom

hardware/xg330/ - The XG 330, where the story starts (1)

xg330-front.jpg
xg330-front.jpg

hardware/xgs136/ - The XGS 136: the board, its parts, and the USB adapter that kept it reachable (22)

The 88E6193X
The 88E6193X		 The second Marvell part
The second Marvell part		 The AQR412C
The AQR412C		 The BIOS flash and the serial label
The BIOS flash and the serial label
The XGS 136, part by part
The XGS 136, part by part		 The XGS 136 from below
The XGS 136 from below		 What reaches the XGS 136's coprocessor, and from where
What reaches the XGS 136's coprocessor, and from where		 CN8, JP11 and a flash
CN8, JP11 and a flash
The CN9130
The CN9130		 DDR4 and JP12
DDR4 and JP12		 The eMMC
The eMMC		 J1, J2 and the LEDs
J1, J2 and the LEDs
The assembly label
The assembly label		 The Nuvoton NCT6779D
The Nuvoton NCT6779D		 The PoE controller
The PoE controller		 The XGS 136's fourteen front ports, end to end
The XGS 136's fourteen front ports, end to end
The host CPU
The host CPU		 The XGS 136 from above, with its parts numbered
The XGS 136 from above, with its parts numbered		 The XGS 136 from above
The XGS 136 from above		 The RS-232 transceiver
The RS-232 transceiver
Its label: WL-NWU330GCA, Rev.a, the serial number pixelated
Its label: WL-NWU330GCA, Rev.a, the serial number pixelated		 The WAVLINK WL-NWU330GCA USB to 2.5G Ethernet adapter
The WAVLINK WL-NWU330GCA USB to 2.5G Ethernet adapter

hardware/xgs3300/ - The XGS 3300: the board, its parts and its front panel (16)

The host CPU
The host CPU		 The XGS 3300, part by part
The XGS 3300, part by part		 The bypass relays
The bypass relays		 The front panel, end to end
The front panel, end to end
The GIFAR bridge on the front panel board
The GIFAR bridge on the front panel board		 The Intel i210
The Intel i210		 The XGS 3300 opened, with its parts numbered
The XGS 3300 opened, with its parts numbered		 JUART1 and its transceiver
JUART1 and its transceiver
The Lattice device
The Lattice device		 The 88X5113 PHY
The 88X5113 PHY		 NCB-XG330D
NCB-XG330D		 The OCTEON TX coprocessor
The OCTEON TX coprocessor
The service headers
The service headers		 What each header is and what it takes
What each header is and what it takes		 The XGS 3300 opened
The XGS 3300 opened		 Inside the appliance
Inside the appliance

Measurements

Each folder holds one measurement's photographs - the windows the runs were taken in, as they finished - and is named after the page that tables them.

measurements/anomaly-136-2026-10-19/ (1)

image what it shows used on
01-xgs136-unusual-traffic.png The XGS 136: the port scan, the sweep and a stream in hardware, all reported anomaly-2026-10-19.md

measurements/anomaly-2026-10-19/ (3)

The page: anomaly-2026-10-19.md.

image what it shows used on
01-xgs3300-scan-sweep-volume.png Run 1: the port scan and the volume reported, the sweep missed anomaly-2026-10-19.md
02-xgs3300-readings-every-ten-seconds.png Run 2: readings every ten seconds - the port scan, the sweep and the volume, all reported anomaly-2026-10-19.md
03-xgs3300-log-page.png XGS: Log File filtered on xgs-anomaly: the scans, the sweep and the volumes of both runs anomaly-2026-10-19.md

measurements/bench-2026-10-17/ (16)

The page: bench-2026-10-17.md.

image what it shows used on
01-clear-pc-to-old3300.png clear text, PC to the first XGS 3300, one stream: 1.85 Gbit/s bench-2026-10-17.md
02-clear-old3300-to-pc.png clear text, the first XGS 3300 to the PC, one stream: 3.00 Gbit/s bench-2026-10-17.md
03-clear-pc-to-old3300-p4.png clear text, PC to the first XGS 3300, four streams: 2.68 Gbit/s bench-2026-10-17.md
04-clear-old3300-to-pc-p4.png clear text, the first XGS 3300 to the PC, four streams: 4.60 Gbit/s bench-2026-10-17.md
05-clear-pc-to-136.png clear text, PC to the XGS 136 before issue 415: 18.3 Mbit/s bench-2026-10-17.md
06-clear-136-to-pc.png clear text, the XGS 136 to the PC before issue 415: 347 Mbit/s bench-2026-10-17.md
20-ipsec-sw-pc-to-old3300.png IPsec, the second 3300 in software, PC to the first XGS 3300: 1.25 Gbit/s bench-2026-10-17.md
21-ipsec-sw-old3300-to-pc.png IPsec, the second 3300 in software, the first XGS 3300 to the PC: 2.73 Gbit/s bench-2026-10-17.md
22-ipsec-new-sw-136-hw-pc-to-136.png IPsec, the second 3300 in software and the 136 in hardware, PC to the XGS 136: 668 Mbit/s bench-2026-10-17.md
23-ipsec-new-sw-136-hw-136-to-pc.png IPsec, the second 3300 in software and the 136 in hardware, the XGS 136 to the PC: 893 Mbit/s bench-2026-10-17.md
30-ipsec-hw-pc-to-old3300.png IPsec in hardware, PC to the first XGS 3300: 1.85 Gbit/s bench-2026-10-17.md
31-ipsec-hw-old3300-to-pc.png IPsec in hardware, the first XGS 3300 to the PC: 2.42 Gbit/s bench-2026-10-17.md
32-ipsec-hw-pc-to-old3300-p4.png IPsec in hardware, PC to the first XGS 3300, four streams: 2.01 Gbit/s bench-2026-10-17.md
33-ipsec-hw-old3300-to-pc-p4.png IPsec in hardware, the first XGS 3300 to the PC, four streams: 2.58 Gbit/s bench-2026-10-17.md
34-ipsec-hw-pc-to-136.png IPsec in hardware, PC to the XGS 136: 902 Mbit/s bench-2026-10-17.md
35-ipsec-hw-136-to-pc.png IPsec in hardware, the XGS 136 to the PC: 893 Mbit/s bench-2026-10-17.md

measurements/cage-medium-2026-10-19/ (3)

The page: cage-medium-2026-10-19.md.

image what it shows used on
01-cage-medium-before.png Before: the 136's F1 says 1000baseSX with a 1000BASE-T module in it; the XGS 3300's F1 and F2 say 10Gbase-SR with copper modules cage-medium-2026-10-19.md
02-cage-medium-after.png After: every cage's port reports its module's medium cage-medium-2026-10-19.md
03-xgs136-module-media.png The XGS 136's module_media: what it refuses, a cage told nothing, and put back cage-medium-2026-10-19.md

measurements/dos-probe-2026-10-19/ (1)

The page: dos-probe-2026-10-19.md.

image what it shows used on
02-xgs3300-the-answers.png The DoS commands, with the coprocessor's answers: each not dispatched, and the stream untouched dos-probe-2026-10-19.md

measurements/hw-counters-2026-10-19/ (8)

The page: hw-counters-2026-10-19.md.

image what it shows used on
01-xgs3300-4gb.png Run 1: 4,000,000,000 bytes, counted by the coprocessor and by pf, against what the VM received hw-counters-2026-10-19.md
02-xgs3300-4gb-retransmissions.png Run 2: the same, with the PC's retransmission count hw-counters-2026-10-19.md
03-xgs3300-reused-slot.png Run 3: a connection on a slot that had just carried a stream, counted from its own first byte hw-counters-2026-10-19.md
04-xgs3300-given-to-pf.png Run 4: the coprocessor's counts given to pf - its states, and the rules that passed them hw-counters-2026-10-19.md
05-xgs3300-port-counts.png The port counts, summed over every message: a stream in hardware, and the same through the host hw-counters-2026-10-19.md
06-xgs3300-sessions-page.png Firewall: Diagnostics: Sessions with the coprocessor's counts given to pf: each stream at 80 GB and more hw-counters-2026-10-19.md
07-xgs3300-port-counts-applied.png The port counts added to the interfaces' counters: without, the host's interfaces saw 45 packets of a 6.65 GB stream; with, the whole of it hw-counters-2026-10-19.md
08-xgs3300-traffic-graph.png Reporting: Traffic for F1 and F2 with the port counts added: two streams in hardware at about 4.5 Gbit/s hw-counters-2026-10-19.md

measurements/ipv6-and-queues-2026-10-18/ (3)

The page: ipv6-and-queues-2026-10-18.md.

image what it shows used on
xgs136-txq-2026-10-18-four-queues.png Four queues: 937, 941 and 941 Mbit/s, one stream's frames all on one queue and eight streams' spread over all four, nothing falling back ipv6-and-queues-2026-10-18.md
xgs136-txq-2026-10-18-one-queue.png One queue: 936, 941 and 941 Mbit/s, every frame on the first queue ipv6-and-queues-2026-10-18.md
xgs3300-ipv6.png The run: 9.24 Gbit/s from the PC to the server and 9.27 back, eighteen IPv6 directions listed and all eighteen active in hardware each time ipv6-and-queues-2026-10-18.md

measurements/ja4-cut-136-2026-10-19/ (1)

image what it shows used on
01-xgs136-ja4-cut.png The XGS 136: the listed stream cut at second 10, the one beside it ran on ja4-cut-2026-10-19.md

measurements/ja4-cut-2026-10-19/ (2)

The page: ja4-cut-2026-10-19.md.

image what it shows used on
01-xgs3300-now.png XGS 3300, the fingerprint listed at second 10 ja4-cut-2026-10-19.md
02-xgs3300-listed.png XGS 3300, the fingerprint listed before the streams ja4-cut-2026-10-19.md

measurements/lists-cut-2026-10-19/ (4)

The page: lists-cut-2026-10-19.md.

image what it shows used on
01-xgs136-now.png XGS 136, cut at once lists-cut-2026-10-19.md
02-xgs136-cron.png XGS 136, cut by the minute's cron lists-cut-2026-10-19.md
03-xgs3300-now.png XGS 3300, cut at once lists-cut-2026-10-19.md
04-xgs3300-cron.png XGS 3300, cut by the minute's cron lists-cut-2026-10-19.md

measurements/mtu-2026-10-17/ (65)

The page: mtu-2026-10-17.md.

image what it shows used on
drops-old3300-to-pc.png sender retransmits against the PC NIC's discards, one stream at each MTU, and four streams at 9000 mtu-2026-10-17.md
mtu1000-136-clear-in.png MTU 1000, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu1000-136-clear-out.png MTU 1000, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu1000-136-ipsec-in.png MTU 1000, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu1000-136-ipsec-out.png MTU 1000, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu1000-old3300-clear-in.png MTU 1000, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1000-old3300-clear-out.png MTU 1000, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu1000-old3300-ipsec-in.png MTU 1000, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1000-old3300-ipsec-out.png MTU 1000, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu1280-136-clear-in.png MTU 1280, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu1280-136-clear-out.png MTU 1280, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu1280-136-ipsec-in.png MTU 1280, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu1280-136-ipsec-out.png MTU 1280, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu1280-old3300-clear-in.png MTU 1280, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1280-old3300-clear-out.png MTU 1280, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu1280-old3300-ipsec-in.png MTU 1280, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1280-old3300-ipsec-out.png MTU 1280, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu1500-136-clear-in.png MTU 1500, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu1500-136-clear-out.png MTU 1500, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu1500-136-ipsec-in.png MTU 1500, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu1500-136-ipsec-out.png MTU 1500, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu1500-old3300-clear-in.png MTU 1500, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1500-old3300-clear-out.png MTU 1500, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu1500-old3300-ipsec-in.png MTU 1500, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu1500-old3300-ipsec-out.png MTU 1500, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu2000-136-clear-in.png MTU 2000, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu2000-136-clear-out.png MTU 2000, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu2000-136-ipsec-in.png MTU 2000, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu2000-136-ipsec-out.png MTU 2000, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu2000-old3300-clear-in.png MTU 2000, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu2000-old3300-clear-out.png MTU 2000, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu2000-old3300-ipsec-in.png MTU 2000, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu2000-old3300-ipsec-out.png MTU 2000, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu4000-136-clear-in.png MTU 4000, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu4000-136-clear-out.png MTU 4000, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu4000-136-ipsec-in.png MTU 4000, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu4000-136-ipsec-out.png MTU 4000, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu4000-old3300-clear-in.png MTU 4000, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu4000-old3300-clear-out.png MTU 4000, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu4000-old3300-ipsec-in.png MTU 4000, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu4000-old3300-ipsec-out.png MTU 4000, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu576-136-clear-in.png MTU 576, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu576-136-clear-out.png MTU 576, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu576-136-ipsec-in.png MTU 576, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu576-136-ipsec-out.png MTU 576, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu576-old3300-clear-in.png MTU 576, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu576-old3300-clear-out.png MTU 576, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu576-old3300-ipsec-in.png MTU 576, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu576-old3300-ipsec-out.png MTU 576, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu6000-136-clear-in.png MTU 6000, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu6000-136-clear-out.png MTU 6000, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu6000-136-ipsec-in.png MTU 6000, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu6000-136-ipsec-out.png MTU 6000, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu6000-old3300-clear-in.png MTU 6000, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu6000-old3300-clear-out.png MTU 6000, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu6000-old3300-ipsec-in.png MTU 6000, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu6000-old3300-ipsec-out.png MTU 6000, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu9000-136-clear-in.png MTU 9000, clear text, PC to the XGS 136 mtu-2026-10-17.md
mtu9000-136-clear-out.png MTU 9000, clear text, the XGS 136 to the PC mtu-2026-10-17.md
mtu9000-136-ipsec-in.png MTU 9000, IPsec, PC to the XGS 136 mtu-2026-10-17.md
mtu9000-136-ipsec-out.png MTU 9000, IPsec, the XGS 136 to the PC mtu-2026-10-17.md
mtu9000-old3300-clear-in.png MTU 9000, clear text, PC to the first XGS 3300 mtu-2026-10-17.md
mtu9000-old3300-clear-out.png MTU 9000, clear text, the first XGS 3300 to the PC mtu-2026-10-17.md
mtu9000-old3300-ipsec-in.png MTU 9000, IPsec, PC to the first XGS 3300 mtu-2026-10-17.md
mtu9000-old3300-ipsec-out.png MTU 9000, IPsec, the first XGS 3300 to the PC mtu-2026-10-17.md

measurements/powerd-2026-10-17/ (8)

image what it shows used on
01-off-pc-to-3300.png appliance-defaults.md
02-off-3300-to-pc.png appliance-defaults.md
05-off-pc-to-3300-mtu1500.png appliance-defaults.md
06-off-3300-to-pc-mtu1500.png appliance-defaults.md
07-on-pc-to-3300-mtu1500.png appliance-defaults.md
08-on-3300-to-pc-mtu1500.png appliance-defaults.md
09-on-pc-to-3300-mtu9000.png appliance-defaults.md
10-on-3300-to-pc-mtu9000.png appliance-defaults.md

measurements/receive-poll-2026-10-17/ (5)

image what it shows used on
10ms-64.png 10 ms and 64 frames: 18.2 Mbit/s a-hundred-polls-a-second-on-the-armada.md
1ms-1024-reverse.png 1 ms and 1024 frames, the other way: 934 Mbit/s a-hundred-polls-a-second-on-the-armada.md
1ms-1024.png 1 ms and 1024 frames: 773 Mbit/s a-hundred-polls-a-second-on-the-armada.md
1ms-256.png 1 ms and 256 frames: 704 Mbit/s a-hundred-polls-a-second-on-the-armada.md
1ms-64.png 1 ms and 64 frames: 185 Mbit/s a-hundred-polls-a-second-on-the-armada.md

measurements/rpc-bounds-2026-10-19/ (1)

The page: rpc-bounds-2026-10-19.md.

image what it shows used on
01-xgs3300-the-posted-bound.png The posted commands with flow_len 0, 600 and 5000: posted, sent on the low ring, refused rpc-bounds-2026-10-19.md

measurements/xgs136-after-boot-2026-10-19/ (5)

The page: xgs136-after-boot-2026-10-19.md.

image what it shows used on
01-xgs136-f1-down-and-up.png F1 down for 5 seconds and up again: no slow minutes xgs136-after-boot-2026-10-19.md
02-xgs136-port8-down-and-up.png Port8 down for 5 seconds and up again: no slow minutes xgs136-after-boot-2026-10-19.md
03-xgs136-the-minutes-after-a-boot.png The first watch: nothing recorded xgs136-after-boot-2026-10-19.md
04-xgs136-ten-minutes-three-ways.png Ten minutes three ways: nothing slow xgs136-after-boot-2026-10-19.md
05-xgs136-the-minutes-after-a-boot.png A boot watched: nothing slow, the host quiet, the coprocessor's fourth core nearly idle xgs136-after-boot-2026-10-19.md

measurements/xgs136-counts-2026-10-19/ (8)

The page: xgs136-counts-2026-10-19.md.

image what it shows used on
01-xgs136-untagged-frames.png The unknown-tag count each second: none idle, 6 or 7 with a stream in hardware, none with the same stream through the host xgs136-counts-2026-10-19.md
02-xgs136-the-frames-read.png The frames read once a second through a stream in hardware, decoded: connection counts for slot 2, then interface counts xgs136-counts-2026-10-19.md
03-xgs136-counted-against-the-wire.png The first reader: F1 counted 5,455,724 bytes more than the PC sent, four a frame xgs136-counts-2026-10-19.md
04-xgs136-counted-the-other-way.png The first reader the other way: Port8 counted 5,564,860 bytes more than the XGS 3300 sent xgs136-counts-2026-10-19.md
05-xgs136-counted-against-the-wire-fcs-off.png With the FCS taken off: F1 to 42 bytes of what the PC sent xgs136-counts-2026-10-19.md
06-xgs136-counted-the-other-way-fcs-off.png Before the fix: 73 remakes, and pf 117,531 packets short xgs136-counts-2026-10-19.md
07-xgs136-counted-the-other-way-given-before-remake.png XGS 3300 to PC through the 136 in hardware: pf's state equal to what the XGS 3300 sent, to the byte, through 18 remakes xgs136-counts-2026-10-19.md
08-xgs136-counted-against-the-wire-final.png PC to XGS 3300 through the 136 in hardware: pf's state 0 packets and 6 bytes from what the XGS 3300 received; every interface to the frame xgs136-counts-2026-10-19.md

measurements/xgs136-giveback-2026-10-19/ (10)

The page: xgs136-giveback-2026-10-19.md.

image what it shows used on
01-xgs136-given-back-which-way.png The first look: the remakes come with the XGS 3300 sending, not the other way xgs136-giveback-2026-10-19.md
02-xgs136-where-the-frames-go.png The XGS 3300 sending three ways: frames lost between F1 and the PC through the host too, and in hardware hundreds of retransmissions with none lost xgs136-giveback-2026-10-19.md
03-xgs136-out-of-order.png Before: the XGS 3300 sending through the 136 in hardware, 789 Mbit/s, 2,110 retransmissions and 29 remakes, against 887 through the host xgs136-giveback-2026-10-19.md
04-xgs136-out-of-order-with-the-wait.png The first build: the XGS 3300 sending in hardware fell to 365 Mbit/s xgs136-giveback-2026-10-19.md
05-xgs136-out-of-order-held-out-of-the-table.png The second build, the run two minutes after its boot: the PC's way slow in the same way xgs136-giveback-2026-10-19.md
06-xgs136-out-of-order-held-again.png The second build: 812 Mbit/s the XGS 3300's way, and still 1,367 retransmissions xgs136-giveback-2026-10-19.md
07-xgs136-a-minute-the-other-way.png The second build over a minute: 851 Mbit/s and 6,073 retransmissions xgs136-giveback-2026-10-19.md
08-xgs136-out-of-order-held-both-ways.png The first run on the published build, two minutes after its boot: the PC's way at a third of its speed, both paths xgs136-giveback-2026-10-19.md
09-xgs136-a-minute-held-both-ways.png After, over a minute: the holds thinning out, the retransmissions falling, 861 Mbit/s xgs136-giveback-2026-10-19.md
10-xgs136-out-of-order-held-both-ways-settled.png After: 877 Mbit/s in hardware the XGS 3300's way, no remake, and the PC's way unchanged xgs136-giveback-2026-10-19.md

measurements/xgs136-hardware-2026-10-18/ (4)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
01-host-pc-to-3300.png The host, PC to the XGS 3300 xgs136-hardware-2026-10-18.md
02-host-3300-to-pc.png The host, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md
03-hardware-pc-to-3300.png The coprocessor, PC to the XGS 3300 xgs136-hardware-2026-10-18.md
04-hardware-3300-to-pc.png The coprocessor, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md

measurements/xgs136-hardware-2026-10-18/ipv6/ (5)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
01-v6-host-pc-to-3300.png IPv6: the host, PC to the XGS 3300, the first run xgs136-hardware-2026-10-18.md
01b-v6-host-pc-to-3300-again.png IPv6: the host, PC to the XGS 3300, again xgs136-hardware-2026-10-18.md
02-v6-host-3300-to-pc.png IPv6: the host, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md
03-v6-hardware-pc-to-3300.png IPv6: the coprocessor, PC to the XGS 3300 xgs136-hardware-2026-10-18.md
04-v6-hardware-3300-to-pc.png IPv6: the coprocessor, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md

measurements/xgs136-hardware-2026-10-18/many/ (18)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
many-1024-hardware-16384.png A thousand connections: the coprocessor, 16,384 candidate slots xgs136-hardware-2026-10-18.md
many-1024-hardware-posted.png 1,024 connections, flow writes posted xgs136-hardware-2026-10-18.md
many-1024-hardware-sloppy.png 1,024 connections, everything fixed xgs136-hardware-2026-10-18.md
many-1024-hardware.png A thousand connections: the coprocessor, 1,024 candidate slots xgs136-hardware-2026-10-18.md
many-1024-host.png A thousand connections: the host xgs136-hardware-2026-10-18.md
many-1024-series-1-posted.png 1,024 connections, series 1, posted xgs136-hardware-2026-10-18.md
many-1024-series-2-waited.png 1,024 connections, series 2, waited xgs136-hardware-2026-10-18.md
many-1024-series-3-posted.png 1,024 connections, series 3, posted xgs136-hardware-2026-10-18.md
many-1024-series-4-waited.png 1,024 connections, series 4, waited xgs136-hardware-2026-10-18.md
teardown-invalidate-type-0-1-posted.png Teardown, invalidate type 0, posted xgs136-hardware-2026-10-18.md
teardown-invalidate-type-0-2-waited.png Teardown, invalidate type 0, waited xgs136-hardware-2026-10-18.md
teardown-keepalive-1-posted.png Teardown, the walk fixed, posted xgs136-hardware-2026-10-18.md
teardown-keepalive-2-posted.png Teardown, the walk fixed, posted, again xgs136-hardware-2026-10-18.md
teardown-keepalive-3-waited.png Teardown, the walk fixed, waited xgs136-hardware-2026-10-18.md
teardown-reclaim-1-posted.png Teardown, reclaimed, posted xgs136-hardware-2026-10-18.md
teardown-reclaim-2-waited.png Teardown, reclaimed, waited xgs136-hardware-2026-10-18.md
teardown-reclaim-3-posted.png Teardown, reclaimed, posted, again xgs136-hardware-2026-10-18.md
teardown-reclaim-4-waited.png Teardown, reclaimed, waited, again xgs136-hardware-2026-10-18.md

measurements/xgs136-hardware-2026-10-18/nat/ (4)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
01-nat-host-pc-to-3300wan.png Translated: the host, PC to the WAN address xgs136-hardware-2026-10-18.md
02-nat-host-3300wan-to-pc.png Translated: the host, the WAN address to the PC xgs136-hardware-2026-10-18.md
03-nat-hardware-pc-to-3300wan.png Translated: the coprocessor, PC to the WAN address xgs136-hardware-2026-10-18.md
04-nat-hardware-3300wan-to-pc.png Translated: the coprocessor, the WAN address to the PC xgs136-hardware-2026-10-18.md

measurements/xgs136-hardware-2026-10-18/revive/ (6)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
01-host-pc-to-3300.png Revived: the host, PC to the XGS 3300 xgs136-hardware-2026-10-18.md
02-host-3300-to-pc.png Revived: the host, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md
03-hardware-pc-to-3300.png Revived: the coprocessor, PC to the XGS 3300 xgs136-hardware-2026-10-18.md
04-hardware-3300-to-pc.png Revived: the coprocessor, the XGS 3300 to the PC xgs136-hardware-2026-10-18.md
05-hardware-3300-to-pc-by-second.png Revived: the coprocessor, the XGS 3300 to the PC, second by second xgs136-hardware-2026-10-18.md
06-hardware-3300-to-pc-by-second-attached.png Tried: one direction attached at a time, second by second xgs136-hardware-2026-10-18.md

measurements/xgs136-hardware-2026-10-18/takeout/ (7)

The page: xgs136-hardware-2026-10-18.md.

image what it shows used on
01-killed-state-invalidate-type-0.png A killed state, the takeout refused xgs136-hardware-2026-10-18.md
02-killed-state-conn-reclaim.png A killed state, the connection reclaimed xgs136-hardware-2026-10-18.md
03-return-to-host-reclaim-pf-window-stale.png Return to host, pf judging the window xgs136-hardware-2026-10-18.md
04-return-to-host-pf-sloppy.png Return to host, pf states sloppy xgs136-hardware-2026-10-18.md
05-killed-state-pf-sloppy.png A killed state, the connection reclaimed, pf states sloppy xgs136-hardware-2026-10-18.md
06-return-to-host-pf-strict.png Return to host, flow.pf_sloppy 0 xgs136-hardware-2026-10-18.md
07-return-to-host-pf-sloppy.png Return to host, flow.pf_sloppy 1 xgs136-hardware-2026-10-18.md

measurements/xgs136-soak-2026-10-19/ (1)

The page: xgs136-soak-2026-10-19.md.

image what it shows used on
01-xgs136-two-hours-of-tls.png Two hours of TLS through the XGS 136: 795 passes of 1 GiB, none failed and none changed, 945 Mbit/s on average, the CPUs 2.5 % busy xgs136-soak-2026-10-19.md

measurements/xgs3300-many-2026-10-19/ (3)

The page: xgs3300-many-2026-10-19.md.

image what it shows used on
01-xgs3300-a-thousand-connections.png The first run: 10,386 Mbit/s, more than the link carries - the reading's interval, not the traffic xgs3300-many-2026-10-19.md
02-xgs3300-a-thousand-connections-read-right.png The second run: the rate right at 9,816 Mbit/s, the connections counted three times over xgs3300-many-2026-10-19.md
03-xgs3300-a-thousand-connections-counted-right.png A thousand connections through the XGS 3300: 1,032 in hardware, 9,837 Mbit/s, the CPUs 7.8 % busy xgs3300-many-2026-10-19.md

The README's drawings

image used on
banner-dark.svg README.md
banner-light.svg README.md
status-dark.svg no page yet
status-light.svg no page yet

Not on any page yet

Kept for a page that will use them - or for the wiki, which links here:

Discussion

The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.