[Device]: Peplink Pepwave AP One AC Mini (2.4GHz and 5.0GHz) #471

Closed
opened 2026-11-08 06:16:14 +00:00 by jaylouisw · 1 comment
Owner

Vendor

Peplink

Exact model name

2.4GHz and 5.0GHz

Category

Wireless AP

Ports and interfaces

  • See product page for full port list

Ports inferred from the 4gon product name; confirm against the product page.

PoE budget (watts)

None

Datasheet or product page URL

https://www.4gon.co.uk/peplink-pepwave-ap-one-ac-mini-24ghz-and-50ghz-p-6331.html

What do you want to model with it?

A Wi-Fi access point in a wireless lab.

Capabilities

wireless, l2-forward

Before submitting

  • I searched the catalog and existing issues, and this model is not there yet.
  • The port list above comes from a datasheet, not from memory or another wiki.
### Vendor Peplink ### Exact model name 2.4GHz and 5.0GHz ### Category Wireless AP ### Ports and interfaces - See product page for full port list > Ports inferred from the 4gon product name; confirm against the product page. ### PoE budget (watts) None ### Datasheet or product page URL https://www.4gon.co.uk/peplink-pepwave-ap-one-ac-mini-24ghz-and-50ghz-p-6331.html ### What do you want to model with it? A Wi-Fi access point in a wireless lab. ### Capabilities wireless, l2-forward ### Before submitting - [x] I searched the catalog and existing issues, and this model is not there yet. - [x] The port list above comes from a datasheet, not from memory or another wiki.
jaylouisw referenced this issue from a commit 2026-11-08 06:43:28 +00:00
Author
Owner

Modelled - devices/peplink/apo-ac-mini.json, commit 98890f4 on fix/sfp-plus-connectors.

The port count that kept blocking this turned out to be in the AP One series datasheet (pepwave_apone_datasheet.pdf, reached from /products/wifi-poe/ap-one-series-mini/, which the site sitemap lists - the old /products/ap-one-ac-mini/ URL 404s). The APO-AC-MINI row:

  • Ethernet Port: 1x GE - one socket, which is both the uplink and the power inlet;
  • Power Consumption: 9.5W (max.), Power Input: 802.3af PoE (Injector Not Included); package contents add a 12V2A Power Supply (ACW-601), so it runs either way;
  • Simultaneous 802.11ac wave 2 /ac/a/n and 802.11b/g/n, 2x2 MU-MIMO, **2.4 GHz: 300Mbps, 5GHz: 866Mbps** - both rates quoted, not inferred from the class.

So poeIn: 9.5 on the single port, two wireless interfaces at 300M and 866M, and no PoE output of any kind: this is a powered device, not a PSE. An 802.3af injector powers it with margin, and the engine says so.

Also for the record: 16 SSIDs per radio, 60 recommended clients, built-in 2.2/3 dBi omni antennas, plenum-rated indoor plastic, 150 g - bridge, NAT and WDS modes all supported, so the spec carries bridge and nat together.

Modelled - `devices/peplink/apo-ac-mini.json`, commit `98890f4` on `fix/sfp-plus-connectors`. The port count that kept blocking this turned out to be in the **AP One series datasheet** (`pepwave_apone_datasheet.pdf`, reached from `/products/wifi-poe/ap-one-series-mini/`, which the site sitemap lists - the old `/products/ap-one-ac-mini/` URL 404s). The APO-AC-MINI row: * **`Ethernet Port: 1x GE`** - one socket, which is both the uplink and the power inlet; * `Power Consumption: 9.5W (max.)`, `Power Input: 802.3af PoE (Injector Not Included)`; package contents add a `12V2A Power Supply (ACW-601)`, so it runs either way; * `Simultaneous 802.11ac wave 2 /ac/a/n and 802.11b/g/n, 2x2 MU-MIMO, **2.4 GHz: 300Mbps, 5GHz: 866Mbps**` - both rates quoted, not inferred from the class. So `poeIn: 9.5` on the single port, two `wireless` interfaces at 300M and 866M, and **no PoE output of any kind**: this is a powered device, not a PSE. An 802.3af injector powers it with margin, and the engine says so. Also for the record: 16 SSIDs per radio, 60 recommended clients, built-in 2.2/3 dBi omni antennas, plenum-rated indoor plastic, 150 g - bridge, NAT and WDS modes all supported, so the spec carries `bridge` and `nat` together.
Sign in to join this conversation.
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#471
No description provided.