[Device]: Ubiquiti PowerBeam M 400mm Radome (PBE-RAD-400) #219
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#219
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
PBE-RAD-400
Category
Point-to-point radio
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/ubiquiti-powerbeam-m-400mm-radome-pberad400-p-6014.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
PBE-RAD-400 is a 400 mm radome - a plastic cover for a PowerBeam M. No ports, no logic, nothing to cable.
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.
PBE-RAD-400 is a moulded radome - a cover that fits over the PowerBeam M400 dish. No port, no address, no configuration, nothing to forward; the radio it shields is the thing a lab models, and it is already represented separately.
The request's "Ports and interfaces" line reads "inferred from the 4gon product name", which is the giveaway - there is no port list to confirm because the product does not have one.
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.