[Bug]: a copper SFP in an SFP+ cage cannot mate an RJ45 peer #1514

Closed
opened 2026-11-15 14:21:59 +00:00 by jaylouisw · 0 comments
Owner

What happened

connect() refuses to cable an SFP+ cage to an RJ45 port, even when the SFP+ cage is told to
carry 1000base-t-sfp - which is exactly what a copper SFP module is. The refusal names the
connector pair and then offers no possible media, so the pairing is unreachable through the API:

CRS305-1G-4S+IN/SFP+4 <-> RT-AX89X/wan: Cannot mate SFP+ to RJ45 (incompatible connectors).
1000BASE-T SFP (1000base-t-sfp) is not supported by both CRS305-1G-4S+IN/SFP+4 and RT-AX89X/wan;
possible media: none.

Steps to reproduce

  1. new Topology(); add devices/mikrotik/crs305.json as sw
  2. add any device with a 1G RJ45 port (e.g. devices/asus/rt-ax89x.json, port wan)
  3. t.connect('sw','SFP+4','ap','wan',{ mediaId: '1000base-t-sfp' })
  4. Same result with no mediaId

Expected

1000base-t-sfp should be accepted, because the module is the converter: the cage holds a
copper SFP and the far end is an ordinary RJ45. CAGE_MEDIA['sfp+'] already lists
1000base-t-sfp, so the media table and the mating rule disagree.

Why it matters

This is a common real install (a 10G cage with a copper SFP feeding a 1G RJ45 appliance). Today
the only way to draw it is connect(..., { force: true }), which records a cable the validator
says is impossible - so the topology is either wrong or silently forced.

Environment

Node v24.11.0, Windows 11, main (2625add0)

## What happened `connect()` refuses to cable an SFP+ cage to an RJ45 port, even when the SFP+ cage is told to carry `1000base-t-sfp` - which is exactly what a copper SFP module is. The refusal names the connector pair and then offers no possible media, so the pairing is unreachable through the API: ``` CRS305-1G-4S+IN/SFP+4 <-> RT-AX89X/wan: Cannot mate SFP+ to RJ45 (incompatible connectors). 1000BASE-T SFP (1000base-t-sfp) is not supported by both CRS305-1G-4S+IN/SFP+4 and RT-AX89X/wan; possible media: none. ``` ## Steps to reproduce 1. `new Topology()`; add `devices/mikrotik/crs305.json` as `sw` 2. add any device with a 1G RJ45 port (e.g. `devices/asus/rt-ax89x.json`, port `wan`) 3. `t.connect('sw','SFP+4','ap','wan',{ mediaId: '1000base-t-sfp' })` 4. Same result with no mediaId ## Expected `1000base-t-sfp` should be accepted, because the module *is* the converter: the cage holds a copper SFP and the far end is an ordinary RJ45. `CAGE_MEDIA['sfp+']` already lists `1000base-t-sfp`, so the media table and the mating rule disagree. ## Why it matters This is a common real install (a 10G cage with a copper SFP feeding a 1G RJ45 appliance). Today the only way to draw it is `connect(..., { force: true })`, which records a cable the validator says is impossible - so the topology is either wrong or silently forced. ## Environment Node v24.11.0, Windows 11, main (2625add0)
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#1514
No description provided.