[Device]: Ubiquiti airFiber NxN Scalable MIMO Multiplexer MPx8 (AF-MPx8) #301
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#301
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
Ubiquiti
Exact model name
AF-MPx8
Category
Point-to-point radio
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/ubiquiti-airfiber-nxn-scalable-mimo-multiplexer-mpx8-afmpx8-p-6694.html
What do you want to model with it?
A PtP/PtMP wireless bridge link in a wireless lab.
Capabilities
wireless, l2-forward (bridge)
Before submitting
MPx8 is the eight-path version of the same multiplexer. Same answer: RF plumbing, no data ports.
The catalogue has no category for it. Every spec needs at least one interface the engine can forward on, and these parts have none - the same gap that keeps the Huawei optical modules open. Two ways this could close, and the first needs the owner's decision: add a
passive(orantenna/rf-accessory) category for parts with no data ports, or leave these requests open as a known boundary. I have raised it with the owner and am not inventing a category unilaterally.Closing this one as not a network device.
AF-MPx8 is an NxN MIMO multiplexer - an RF combiner that gangs several airFiber radio chains onto shared antennas through coaxial connectors. Its ports are N-type RF, not Ethernet: no IP stack, no management, nothing for the simulator to forward. This simulator models Ethernet, optical, DSL, console and wireless bearers, not the inside of an antenna run.
The radio chains it combines (AF-11FX and relatives) are already in the catalogue under
devices/ubiquiti/, so a lab can build the topology that matters; the multiplexer changes nothing a packet-level model can observe.Closed as out of scope for the device catalogue. The reasoning is now written down in
docs/DEVICE_REGISTRY.md(What the catalogue cannot represent, commit08d5925) so the next request of this kind can cite it: an accessory with no Ethernet, console, optical or DSL port and no management surface cannot be simulated. A spec for it would be a name with an emptyinterfacesarray, and the palette would then offer a lab something that looks cableable and isn't - worse than leaving the request open.The distinction matters: this is structurally unrepresentable, whereas #527 (Netonix) stays open because that one is a switch and merely lacks a published PoE budget. A gap in the source is not a gap in the simulator, and the fix there is a citation, not a guess.