[Device]: Ubiquiti UniFi Access Point BeaconHD (UAP-BeaconHD) #167
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#167
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
UAP-BeaconHD
Category
Wireless AP
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/ubiquiti-unifi-access-point-beaconhd-uapbeaconhd-p-8552.html
What do you want to model with it?
A Wi-Fi access point in a wireless lab.
Capabilities
wireless, l2-forward
Before submitting
In the catalogue:
devices/ubiquiti/uap-beaconhd.json— no Ethernet port at all: AC wall-plug powered (100-240 V), Bluetooth management, 5 GHz 4x4 1.7 Gbps + 2.4 GHz 2x2 300 Mbps, 11.5 W. It is a pure mesh node: not wireable, not PoE-powered, not reachable except through the mesh.Reopened - this project does not resolve a device request by declaring it impossible.
That closure used the same reasoning I have been applying to RF parts, optical modules and any box whose port table I could not find: "it has no Ethernet ports, so it cannot be modelled". The maintainer's rule is now the opposite, and it is the better one: a device that cannot be modelled yet is still a real device someone asked for, and the request is the record of that. Closing it deletes the interest and loses the evidence that a person wanted it.
So this stays open. What changed in practice:
OptiXtrans E6616/E6608);If you already know the port complement, or have a datapath requirement that this device exists to serve, say so here and it moves up the queue.
Already in the catalogue:
devices/ubiquiti/uap-beaconhd.json- Ubiquiti UniFi BeaconHD (UAP-BeaconHD), 2 interface(s): radio-5g (1700M), radio-2g (300M).This is the second correction on this issue. It was first closed as impossible to model; it is reopened and now closed the only way this project closes a device request - the catalogue answers it, and here is the file that does. The earlier closure was not just against policy, it was wrong on the facts: the device has been modelled the whole time.
If the spec is missing something you need - a port, a radio, a capability - say which and it gets fixed. A wrong entry is worth more attention than a missing one, because it looks answered.