research(oceanprotect): the doc host renders one generation, not a network block #1859

Merged
jaylouisw merged 2 commits from catalogue/1117-1455 into main 2026-11-17 15:05:15 +00:00
Owner

Refs #743. This records a measurement, not a spec: it does not close the issue.

The correction. research/oceanprotect-x-series-port-census.md section 11(c) says the doc host "refuses this network". Measured in one session with one crawler user-agent, minutes apart:

URL result
EDOC1100318730/ce945100/cabinet-layout-and-connection-planning 200, 567,916 B
EDOC1100319420/5ee6c5f0/overview 200, 501,601 B
EDOC1100319420/a9dbbf6/interface-module 200, 485,245 B
EDOC1100305240/216dcdb5/... 302 -> /view/notFound
EDOC1100305242/4dbe1160/... 302 -> /view/notFound
EDOC1100305200/4bd9b2a1/... 302 -> /view/notFound
EDOC1100368229?idPath=... (X6000/X8000/X8100 PD) 302 -> /view/notFound
EDOC1100368230?idPath=... (X9000/X9100 PD) 302 -> /view/notFound
EDOC1100305237?idPath=... (X6000/X8000/X8100 QIG) 302 -> /view/notFound

So the discriminator is the document, not the host and not the source address: the viewer renders the whole 1.3.0 "(with Data Backup Feature)" set anonymously and refuses everything outside it. That matters because the old framing sends the next pass looking for an ALB bypass, and no bypass can produce EDOC1100368229 / EDOC1100368230 / EDOC1100305240 - there is no renderable version to bypass to.

Three supporting findings. (1) The readable generation cannot be borrowed for X8100: EDOC1100319420/a9dbbf6/interface-module contains X8100 0 times and X9100 0 times in 485,245 bytes. (2) The archive route is dead and was dead in an instructive way: Wayback CDX holds exactly one capture across the three ids - EDOC1100305240/216dcdb5/..., 20250906080606, status 200 - and it is the 6,698-byte SPA shell with an empty <title>; its hash 302s live today, which is the general rule that a section hash from an index or an archive is revision-scoped. (3) info.support.huawei.com mirrors the same path shape and answers 302 -> https://support.huawei.com/ under Chrome 131, Bingbot, Googlebot and curl, including through r.jina.ai (Final URL support.huawei.com/supportindex/).

Unchanged field for #743: the IOM slots that accept front-end modules on X8100 (2 U, 2 controllers) and X9100 (4 U, 4 controllers), plus ports per 10/25/40/100GE and 16/32/64 Gbit/s FC module as fitted to those models. A reader with a support session pasting one section of EDOC1100368229, EDOC1100368230 or EDOC1100305240, Huawei's Spare Parts Query output, or a stated configuration (X8100 node, 2 controllers, 4-port 10GE electrical module in IOM 0 and IOM 1) converts in one step.

Gates: node scripts/syntax-check.js 389 files OK; node scripts/audit-port-types.js no contradiction; node scripts/check-doc-citations.js only the four pre-existing suspects; node scripts/check-control-bytes.js clean. Diff against main is additions only (53 lines, one research file, no device specs).

Refs #743. This records a measurement, not a spec: it does not close the issue. **The correction.** `research/oceanprotect-x-series-port-census.md` section 11(c) says the doc host "refuses this network". Measured in one session with one crawler user-agent, minutes apart: | URL | result | |---|---| | `EDOC1100318730/ce945100/cabinet-layout-and-connection-planning` | 200, 567,916 B | | `EDOC1100319420/5ee6c5f0/overview` | 200, 501,601 B | | `EDOC1100319420/a9dbbf6/interface-module` | 200, 485,245 B | | `EDOC1100305240/216dcdb5/...` | 302 -> /view/notFound | | `EDOC1100305242/4dbe1160/...` | 302 -> /view/notFound | | `EDOC1100305200/4bd9b2a1/...` | 302 -> /view/notFound | | `EDOC1100368229?idPath=...` (X6000/X8000/X8100 PD) | 302 -> /view/notFound | | `EDOC1100368230?idPath=...` (X9000/X9100 PD) | 302 -> /view/notFound | | `EDOC1100305237?idPath=...` (X6000/X8000/X8100 QIG) | 302 -> /view/notFound | So the discriminator is the document, not the host and not the source address: the viewer renders the whole 1.3.0 "(with Data Backup Feature)" set anonymously and refuses everything outside it. That matters because the old framing sends the next pass looking for an ALB bypass, and no bypass can produce `EDOC1100368229` / `EDOC1100368230` / `EDOC1100305240` - there is no renderable version to bypass to. **Three supporting findings.** (1) The readable generation cannot be borrowed for X8100: `EDOC1100319420/a9dbbf6/interface-module` contains `X8100` 0 times and `X9100` 0 times in 485,245 bytes. (2) The archive route is dead and was dead in an instructive way: Wayback CDX holds exactly one capture across the three ids - `EDOC1100305240/216dcdb5/...`, `20250906080606`, status 200 - and it is the 6,698-byte SPA shell with an empty `<title>`; its hash 302s live today, which is the general rule that a section hash from an index or an archive is revision-scoped. (3) `info.support.huawei.com` mirrors the same path shape and answers 302 -> `https://support.huawei.com/` under Chrome 131, Bingbot, Googlebot and curl, including through `r.jina.ai` (Final URL `support.huawei.com/supportindex/`). **Unchanged field for #743:** the IOM slots that accept front-end modules on X8100 (2 U, 2 controllers) and X9100 (4 U, 4 controllers), plus ports per 10/25/40/100GE and 16/32/64 Gbit/s FC module as fitted to those models. A reader with a support session pasting one section of `EDOC1100368229`, `EDOC1100368230` or `EDOC1100305240`, Huawei's Spare Parts Query output, or a stated configuration (`X8100 node, 2 controllers, 4-port 10GE electrical module in IOM 0 and IOM 1`) converts in one step. Gates: `node scripts/syntax-check.js` 389 files OK; `node scripts/audit-port-types.js` no contradiction; `node scripts/check-doc-citations.js` only the four pre-existing suspects; `node scripts/check-control-bytes.js` clean. Diff against main is additions only (53 lines, one research file, no device specs).
Measured in one session with one crawler UA: EDOC1100318730 and EDOC1100319420
sections answer 200 (567,916 / 501,601 / 485,245 B) while EDOC1100305240,
EDOC1100305242, EDOC1100305200, EDOC1100368229, EDOC1100368230 and
EDOC1100305237 all 302 to /view/notFound. The discriminator is the document,
not the host or the source address, so an ALB bypass cannot produce the
X8100/X9100 volumes.

Also recorded: the readable generation names X8100 zero times; the single
Wayback capture of EDOC1100305240 is a 6,698-byte SPA shell and its hash is
revision-scoped (302s live); info.support.huawei.com mirrors the same bounce.
research(oceanprotect): keep the original ellipsis glyphs in the quoted slot rules
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 12s
ec3c525f3c
The ASCII sweep in the previous commit touched three pre-existing quoted lines;
restore them so the diff against main is additions only.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1859
No description provided.