Gearbox Tesla Airframe challenge · wireless on the line

2 problems can stop the line·4 tools affected

capture 16 Sep 2026 12:24–12:54 UTC 8 sensors (ch 36/40/44/48/149/153/157/161) 1,118,853 frames 29 AP radios on air (30 planned) 99 devices, 87 connected 11 incidents
● line risk · TESLA-TOOLS ● office network · TESLA-CORP ● security ● info / site ● recovered / clean
Causes, ordered by line risk one card per root cause · click for details
● CAN STOP THE LINE · TESLA-TOOLSsince 12:36:32

Torque tool T-03 switched itself off

where
AP 0f · ch 149 · heard by sensor05
scope
1 tool · silent 17:42 until capture end
who
Line lead: swap the tool now
heartbeat ~30 s · missed 12:35:14 · deauth reason 3 from the tool 12:36:32 · no frame after
● CAN STOP THE LINE · TESLA-TOOLSwhole capture

3 tools cannot connect: their home AP is off

where
radio AP 0d silent · 5 BSSIDs missing (ch 36, 40, 149, 153, 157)
scope
3 tools + 9 office devices (TESLA-CORP)
who
Network team: switch AP 0d on, remove the single-AP binding
devices scan, 52–53 APs answer, no auth ever · no device uses a 2nd AP (87/87, 0 reassociations)
● OFFICE NETWORK · TESLA-CORPwhole capture

Nobody can log in to TESLA-CORP: the login server does not answer

where
26 APs · all 8 channels · all 8 sensors
scope
63 devices · not one login in the whole capture
who
IT / identity team: RADIUS reachability, certificates
EAP-Request/Identity → response in 1 ms → AP asks again 30 s later · no EAP method · 0 EAP-Success · reason 23
● OFFICE NETWORK · TESLA-CORPsince 12:30:53

The controller kicks 18 devices on a timer

where
18 APs · all 8 channels
scope
deauth to 11 devices every 11–15 s · disassoc to 7 every 25–30 s · address order
who
Network team: check controller jobs / client policies
seq continues the AP's own counter (100 % of 1,477 frames) · signal = AP beacons ±0.1 dB → sent by the AP, not an attacker; 802.11w would not help
Controller stall12:28:07 · 2 pulses in 14 s · beacons up to 75 ms late on all 8 channels at onceNetwork team · check controller CPU / logs
Sensor clocks off7 of 8 sensors · up to 1.22 s offset, 25 ppm drift · Gearbox aligns them via beacon TSFSensor owner · no line impact
TESLA-TOOLS: one shared password, no 802.11wWPA2-PSK (AKM 2) · MFP capable = 0 · 27 toolsSecurity team · plan PMF / per-device keys
Sign-off wave15 devices sign off in the first 5 s (12:24:13) · reason 3 / 8 / 36None · planned restart?
Join ramp79 devices join in 3 min · tools one every 2.0 s (12:26:44–12:27:40)None · confirm it was planned
Where devices stop join sequence per network · drops coloured by cause · [from API] = needs a new API field
TESLA-TOOLS · 27 tools · WPA2-PSK (no EAP steps)24 of 27 online at 12:36 · 23 at capture end
27scan
24authenticate−3 home AP off
24associate
n/aEAP identity
n/aEAP method
24 [from API]4-way handshake
24 [from API]data / heartbeat
23 [from API]still online−1 T-03 switched off
TESLA-CORP · 72 devices · WPA2-Enterprise (802.1X)0 of 72 online
72scan
63authenticate−9 home AP off
63associate↺ 18 kicked again and again
63EAP identity
0EAP method−63 login server
04-way handshake
0data / heartbeat
0still online
What we checked 17 fault classes · found = links to the card · clean = tested, nothing found
✓Home AP offfound
✓Device gonefound
✓Controller stallfound
✓AP silentfound (AP 0d)
✓Sensor clock driftfound
✓Security configfound
○Handshake breakcleanno 4-way handshake starts and stops half-way
○Association rejectedcleanno association answered with a reject status
○Roaming ping-pongclean0 reassociations
○Sensor blind spotcleanevery sensor hears its channel's beacons
○Congestionclean78 frames/s per sensor, no retry rise
○Non-Wi-Fi interferencecleannoise floor flat −95…−97 dBm
○Deauth flood / spoofingcleankicks come from the APs themselves
○Evil twincleanno SSID on a foreign BSSID
○Short-lived networkcleanno network appears and vanishes

Gearbox dashboard target · static mockup for the team · numbers from the live result of 26 Sep 2026 (dataset ff1d9f54dee9, 11 incidents) · counts marked [from API] are placeholders.