[Bug]: a copper SFP in an SFP+ cage cannot mate an RJ45 peer #1514
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1514
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?
What happened
connect()refuses to cable an SFP+ cage to an RJ45 port, even when the SFP+ cage is told tocarry
1000base-t-sfp- which is exactly what a copper SFP module is. The refusal names theconnector pair and then offers no possible media, so the pairing is unreachable through the API:
Steps to reproduce
new Topology(); adddevices/mikrotik/crs305.jsonasswdevices/asus/rt-ax89x.json, portwan)t.connect('sw','SFP+4','ap','wan',{ mediaId: '1000base-t-sfp' })Expected
1000base-t-sfpshould be accepted, because the module is the converter: the cage holds acopper SFP and the far end is an ordinary RJ45.
CAGE_MEDIA['sfp+']already lists1000base-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 validatorsays is impossible - so the topology is either wrong or silently forced.
Environment
Node v24.11.0, Windows 11, main (
2625add0)