[Device]: Ubiquiti airFiber Low-Band Duplexer (AF-11-DUP-L) #303

Closed
opened 2026-11-08 06:13:16 +00:00 by jaylouisw · 2 comments
Owner

Vendor

Ubiquiti

Exact model name

AF-11-DUP-L

Category

Point-to-point radio

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/ubiquiti-airfiber-lowband-duplexer-af11fxdupl-p-6819.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

  • 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 Ubiquiti ### Exact model name AF-11-DUP-L ### Category Point-to-point radio ### 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/ubiquiti-airfiber-lowband-duplexer-af11fxdupl-p-6819.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 - [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:32 +00:00
Author
Owner

AF-11-DUP-L is a low-band duplexer: two RF connectors that combine/split 11 GHz paths for one airFiber radio. No Ethernet, no IP, no place in a topology as a node.

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 (or antenna/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.

**AF-11-DUP-L** is a low-band duplexer: two RF connectors that combine/split 11 GHz paths for one airFiber radio. No Ethernet, no IP, no place in a topology as a node. **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` (or `antenna`/`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.
Author
Owner

Closing this one as not a network device.

AF-11-DUP-L is an RF duplexer for the airFiber 11 GHz low band - a passive filter letting transmit and receive share one antenna path. Two coaxial connectors and a cavity; no Ethernet, no address, no configuration.

A lab can cable the AF-11FX radios and set their links; the duplexer changes nothing a simulator of packets could 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, commit 08d5925) 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 empty interfaces array, 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.

Closing this one as **not a network device**. AF-11-DUP-L is an **RF duplexer** for the airFiber 11 GHz low band - a passive filter letting transmit and receive share one antenna path. Two coaxial connectors and a cavity; no Ethernet, no address, no configuration. A lab can cable the AF-11FX radios and set their links; the duplexer changes nothing a simulator of packets could 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*, commit `08d5925`) 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 empty `interfaces` array, 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.
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#303
No description provided.