[Device]: Netonix 24 Port Gigabit 400W WISP Switch (WS-26-400-AC) #527

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

Vendor

Netonix

Exact model name

WS-26-400-AC

Category

Switch (L3)

Ports and interfaces

  • 24 ports

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/netonix-24-port-gigabit-400w-wisp-switch-ws26400ac-p-8555.html

What do you want to model with it?

A managed L3 switch in a switched/routed lab.

Capabilities

l2-forward, l3-forward, cli

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 Netonix ### Exact model name WS-26-400-AC ### Category Switch (L3) ### Ports and interfaces - 24 ports > 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/netonix-24-port-gigabit-400w-wisp-switch-ws26400ac-p-8555.html ### What do you want to model with it? A managed L3 switch in a switched/routed lab. ### Capabilities l2-forward, l3-forward, cli ### 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:29 +00:00
Author
Owner

Modelled - devices/netonix/ws-26-400-ac.json, commit 7f0d6dc on fix/sfp-plus-connectors. This one has been open longer than any other in the batch, and it was open for a reason that turned out to be the wrong question.

The reason it stayed open: I refused to credit the 400 W as a PoE budget, because "400 W" in the model name is the AC power supply, and this catalogue does not turn a PSU rating into a PoE budget (#527 has been the standing example of that rule).

Why that was the wrong question: this is a passive PoE switch. There is no negotiation and no negotiated budget - a passive PSE guarantees volts and amps per port, which the vendor page states outright:

Mode Ports Pins Per port
24 V @ 1 A 1-24 4,5 (+) 7,8 (-) 24 W
48 V @ 1 A 1-24 4,5 (+) 7,8 (-) 48 W
24VH @ 2 A 1-2 all four pairs 48 W
48VH @ 2 A 1-6 all four pairs 96 W

So poeOut is 24 W - what the base 24 V mode delivers on every one of the 24 ports - and the higher modes are in notes rather than averaged into a figure nobody publishes. poeBudget is deliberately absent: 24 x 24 W exceeds the supply, the supply is the limit, and Netonix publishes no separate PoE budget. That is the honest model of a passive PSE: per-port capability quoted, aggregate left to the supply.

Full census: 24x Gigabit copper with PoE, 2x SFP uplinks, and a serial console port (declared as a console interface - this switch is configured over it as well as the web UI). Fanless, -25 to 55 C.

One contradiction recorded: the summary line says "(12) Gbps POE Ports (2) SFP Uplink Ports", while the PoE mode table assigns ports 01-24 and the model is WS-26-400 with 24 copper ports. The table wins - twelve ports would leave half the chassis unpowered and contradict the model number.

No 802.3af/at capability is declared: this is passive PoE on specific pin pairs, and a lab that expects a standard PSE to negotiate with a camera is describing a link that will not come up.

Modelled - `devices/netonix/ws-26-400-ac.json`, commit `7f0d6dc` on `fix/sfp-plus-connectors`. This one has been open longer than any other in the batch, and it was open for a reason that turned out to be the wrong question. **The reason it stayed open:** I refused to credit the 400 W as a PoE budget, because "400 W" in the model name is the **AC power supply**, and this catalogue does not turn a PSU rating into a PoE budget (#527 has been the standing example of that rule). **Why that was the wrong question:** this is a **passive** PoE switch. There is no negotiation and no negotiated budget - a passive PSE guarantees volts and amps per port, which the vendor page states outright: | Mode | Ports | Pins | Per port | |---|---|---|---| | 24 V @ 1 A | 1-24 | 4,5 (+) 7,8 (-) | 24 W | | 48 V @ 1 A | 1-24 | 4,5 (+) 7,8 (-) | 48 W | | 24VH @ 2 A | 1-2 | all four pairs | 48 W | | 48VH @ 2 A | 1-6 | all four pairs | 96 W | So `poeOut` is **24 W** - what the base 24 V mode delivers on every one of the 24 ports - and the higher modes are in `notes` rather than averaged into a figure nobody publishes. **`poeBudget` is deliberately absent**: 24 x 24 W exceeds the supply, the supply is the limit, and Netonix publishes no separate PoE budget. That is the honest model of a passive PSE: per-port capability quoted, aggregate left to the supply. Full census: 24x Gigabit copper with PoE, 2x SFP uplinks, and a **serial console port** (declared as a console interface - this switch is configured over it as well as the web UI). Fanless, -25 to 55 C. **One contradiction recorded:** the summary line says *"(12) Gbps POE Ports (2) SFP Uplink Ports"*, while the PoE mode table assigns **ports 01-24** and the model is WS-26-400 with 24 copper ports. The table wins - twelve ports would leave half the chassis unpowered and contradict the model number. No 802.3af/at capability is declared: this is passive PoE on specific pin pairs, and a lab that expects a standard PSE to negotiate with a camera is describing a link that will not come up.
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#527
No description provided.