devices(mikrotik): the wAP ac LTE6 kit is a router that could not bridge, lease or be powered (refs #130) #2169

Merged
jaylouisw merged 1 commit from catalogue/1119-1452 into main 2026-11-19 15:42:33 +00:00
Owner

refs #130 (records the catalogue defect found underneath this request; it does not close it)

#130 asks for a Dream Wall Pro and is still blocked. Its nine Ubiquiti surfaces were not re-walked this pass (nine exhausted, last measured 13:25 today, nothing has changed). The increment went to the other half of the stated request - "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)" - and to the cheapest such gateway in the catalogue: devices/mikrotik/wap-ac-lte6-kit.json, a weatherproof AP with an embedded LTE Cat 6 modem that MikroTik sells as a router.

Three defects on rows the vendor does print

field before vendor (read 2026-11-19)
switching no l2-forward "Switch chip model IPQ-4018"; throughput table row "Bridging, none (fast path) 162.5 kpps / 1973.4 Mbps" beside the routing row
DHCP nat but no dhcp-server/dhcp-client "RouterOS license 4"; "you can use the device as a wired router with LTE backup via the Micro SIM slot"; RouterOS DHCP "includes both server and client parts"
PoE-in 802.3af only, 12.95 W "PoE in 802.3af/at", "PoE in input Voltage 18-57 V", "Max power consumption 16 W"

The DHCP gap made this the only one of 306 NAT-capable MikroTik entries without a DHCP server - a box with nat that cannot lease the address its NAT would translate. The PoE gap is the same shape as #2165's UISP Router: a declared ceiling the hardware's own published draw exceeds, 12.95 W of 802.3af against a 16 W maximum.

Measured before/after (real CLI, real catalogue, no mocks)

probe before (origin/main) after
ip dhcp pool lan % MikroTik wAP ac LTE6 kit-d1 cannot serve DHCP: it has no dhcp-server capability Created DHCP pool lan
switchport mode trunk on eth2 % ... cannot switch frames: it has no l2-forward capability - this port routes Switchport mode trunk on eth2
channel-group 1 mode active % ... cannot bundle ports into a LAG accepted (now that the box bridges)
computePoe(), port1 of a USW-Lite-8-PoE 12.95 W draw 16 W draw of the 52 W budget

So a lab that hands this wAP the gateway role now gets a DHCP server on it, a bridge for its two copper ports, and a PoE budget that matches the wattage the vendor publishes.

Sources (all MikroTik-hosted)

  • https://mikrotik.com/product/wap_ac_lte6_kit - HTTP 200, 388,174 B. "10/100/1000 Ethernet ports 2"; "RouterOS license 4"; "Switch chip model IPQ-4018"; "PoE in 802.3af/at"; "Max power consumption 16 W"; "Max power consumption without attachments 10 W"; "LTE Category 6 (300Mbit/s Downlink, 50Mbit/s Uplink)"; bridging/routing throughput rows.
  • https://manual.mikrotik.com/hardware/wap-ac-kit-series/ - HTTP 200, the series hardware manual: "Ethernet port accepts 802.3af/at PoE 18-57 V DC. The power consumption under maximum load can reach 16 W."
  • https://help.mikrotik.com/docs/spaces/ROS/pages/24805500/DHCP - HTTP 200: "The MikroTik RouterOS implementation includes both server and client parts and is compliant with RFC 2131."

Deliberately not changed

wwan0 stays at 50M. The vendor prints 300 Mbit/s downlink, but 50 Mbit/s is the Cat 6 uplink and the catalogue uses that LTE class figure consistently - devices/mikrotik/chateau-lte18-ax.json is 50M too. Swapping in a marketing downlink number is the sibling-arithmetic error this stream keeps correcting.

Test

test/wap-ac-lte6-kit-router.test.js (new, 13 assertions) pins the three capability additions, that poeIn is 16 W and therefore above what 802.3af may deliver, that computePoe() budgets 16 W on a PoE+ switch, and that ip dhcp pool is accepted.

Gates

node scripts/syntax-check.js - 456 files, all OK. node scripts/audit-port-types.js - "No port contradicts its declared type." test/hardware-invariants.test.js - 26 passed, 0 failed. test/catalogue-hygiene.test.js - 25 passed, 0 failed. test/capability-vocabulary.test.js - 13 passed, 0 failed. node scripts/run-tests.js - 378 suites, 12,812 assertions, 0 failed. node scripts/audit-poe-budget.js - silent-PSE count unchanged at 103 (this box is a PD, not a PSE). node scripts/regen-registry-doc.js - registry doc unchanged (2,356 models, 29,719 sockets; no model added). node scripts/import-devices.js --dry-run refuses two pre-existing duplicate research files (peplink/MAX-BR1-PRO-5G, zte/F8648P) that are unrelated to this change and were already there before it.

Still missing for #130, unchanged: RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and the cellular/WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller record naming UDW-PRO, or the requester confirming they meant the UDW at devices/ubiquiti/udw.json.

refs #130 (records the catalogue defect found underneath this request; it does not close it) #130 asks for a Dream Wall Pro and is still blocked. Its nine Ubiquiti surfaces were **not** re-walked this pass (nine exhausted, last measured 13:25 today, nothing has changed). The increment went to the other half of the stated request - "a router/gateway node in a routed lab (NAT, DHCP, VPN, **cellular WAN**)" - and to the cheapest such gateway in the catalogue: `devices/mikrotik/wap-ac-lte6-kit.json`, a weatherproof AP with an embedded LTE Cat 6 modem that MikroTik sells as a router. ### Three defects on rows the vendor does print | field | before | vendor (read 2026-11-19) | |---|---|---| | switching | no `l2-forward` | "Switch chip model **IPQ-4018**"; throughput table row "**Bridging**, none (fast path) 162.5 kpps / 1973.4 Mbps" beside the routing row | | DHCP | `nat` but **no** `dhcp-server`/`dhcp-client` | "RouterOS license **4**"; "you can use the device as a **wired router with LTE backup** via the Micro SIM slot"; RouterOS DHCP "includes **both server and client** parts" | | PoE-in | `802.3af` only, 12.95 W | "PoE in **802.3af/at**", "PoE in input Voltage 18-57 V", "Max power consumption **16 W**" | The DHCP gap made this the only one of **306** NAT-capable MikroTik entries without a DHCP server - a box with `nat` that cannot lease the address its NAT would translate. The PoE gap is the same shape as #2165's UISP Router: a declared ceiling the hardware's own published draw exceeds, 12.95 W of 802.3af against a 16 W maximum. ### Measured before/after (real CLI, real catalogue, no mocks) | probe | before (origin/main) | after | |---|---|---| | `ip dhcp pool lan` | `% MikroTik wAP ac LTE6 kit-d1 cannot serve DHCP: it has no dhcp-server capability` | `Created DHCP pool lan` | | `switchport mode trunk` on `eth2` | `% ... cannot switch frames: it has no l2-forward capability - this port routes` | `Switchport mode trunk on eth2` | | `channel-group 1 mode active` | `% ... cannot bundle ports into a LAG` | accepted (now that the box bridges) | | `computePoe()`, port1 of a USW-Lite-8-PoE | 12.95 W draw | **16 W** draw of the 52 W budget | So a lab that hands this wAP the gateway role now gets a DHCP server on it, a bridge for its two copper ports, and a PoE budget that matches the wattage the vendor publishes. ### Sources (all MikroTik-hosted) - `https://mikrotik.com/product/wap_ac_lte6_kit` - HTTP 200, 388,174 B. "10/100/1000 Ethernet ports 2"; "RouterOS license 4"; "Switch chip model IPQ-4018"; "PoE in 802.3af/at"; "Max power consumption 16 W"; "Max power consumption without attachments 10 W"; "LTE Category 6 (300Mbit/s Downlink, 50Mbit/s Uplink)"; bridging/routing throughput rows. - `https://manual.mikrotik.com/hardware/wap-ac-kit-series/` - HTTP 200, the series hardware manual: "Ethernet port accepts **802.3af/at PoE** 18-57 V DC. The power consumption under maximum load can reach **16 W**." - `https://help.mikrotik.com/docs/spaces/ROS/pages/24805500/DHCP` - HTTP 200: "The MikroTik RouterOS implementation includes both server and client parts and is compliant with RFC 2131." ### Deliberately not changed `wwan0` stays at **50M**. The vendor prints 300 Mbit/s downlink, but 50 Mbit/s is the Cat 6 *uplink* and the catalogue uses that LTE class figure consistently - `devices/mikrotik/chateau-lte18-ax.json` is 50M too. Swapping in a marketing downlink number is the sibling-arithmetic error this stream keeps correcting. ### Test `test/wap-ac-lte6-kit-router.test.js` (new, 13 assertions) pins the three capability additions, that `poeIn` is 16 W and therefore above what 802.3af may deliver, that `computePoe()` budgets 16 W on a PoE+ switch, and that `ip dhcp pool` is accepted. ### Gates `node scripts/syntax-check.js` - 456 files, all OK. `node scripts/audit-port-types.js` - "No port contradicts its declared type." `test/hardware-invariants.test.js` - 26 passed, 0 failed. `test/catalogue-hygiene.test.js` - 25 passed, 0 failed. `test/capability-vocabulary.test.js` - 13 passed, 0 failed. `node scripts/run-tests.js` - **378 suites, 12,812 assertions, 0 failed**. `node scripts/audit-poe-budget.js` - silent-PSE count unchanged at 103 (this box is a PD, not a PSE). `node scripts/regen-registry-doc.js` - registry doc unchanged (2,356 models, 29,719 sockets; no model added). `node scripts/import-devices.js --dry-run` refuses two **pre-existing** duplicate research files (`peplink/MAX-BR1-PRO-5G`, `zte/F8648P`) that are unrelated to this change and were already there before it. **Still missing for #130, unchanged:** RJ45 and SFP+ counts and rates, which of them are WAN, the PoE class mix and total budget, drive bays, and the cellular/WAN options. **Unblock, unchanged:** any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller record naming `UDW-PRO`, or the requester confirming they meant the `UDW` at `devices/ubiquiti/udw.json`.
devices(mikrotik): the wAP ac LTE6 kit is a router that could not bridge, lease or be powered (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Docker build (pull_request) Successful in 18s
CI / Test (Node 22) (pull_request) Successful in 49s
CI / Arm auto-merge (pull_request) Successful in 4s
43f19a4138
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 15:05:32 +00:00
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!2169
No description provided.