We spend a great deal of time discussing how fast a router can move packets. But when a connection starts dropping, negotiates at the wrong speed, or refuses to come up, wouldn’t it be useful for the router to help answer a simpler question: what is wrong with the connection?
That is a capability I would like to see considered for OpenWrt Two: physical-link diagnostics, covering both Ethernet cable testing on its copper ports and optical-transceiver monitoring on any SFP/SFP+ ports.
Copper ports: is something wrong with the cable?
For the RJ45 ports, I would like support for ethtool --cable-test, ideally with a straightforward interface in LuCI eventually.
I am not suggesting that a router should replace a professional cable-certification instrument. But being able to identify an open or shorted pair—and, where supported, estimate the distance to the fault—would be genuinely useful. For someone troubleshooting a cable running through a wall, that could be more valuable than another increment in headline throughput.
My understanding is that this is not simply a matter of including ethtool in the firmware. The Ethernet PHYs need the appropriate capabilities, and their Linux drivers need to expose them. That makes this worth considering while hardware choices can still be influenced, rather than discovering afterward that an otherwise excellent design cannot provide it.
Optical ports: is enough light getting through?
For any SFP/SFP+ ports, why not also make the diagnostics available from supported optical transceivers accessible to the user?
I mean the digital optical monitoring information available through ethtool -m: transmit and receive optical power, module temperature, laser bias current, and relevant warning or alarm thresholds.
This is a different capability from copper cable testing. I would not expect an ordinary optical transceiver to locate a fiber break or replace an OTDR. But there is a considerable difference between being told “the link is down” and being able to see that the receiver is getting very little light—or that the module is reporting an abnormal condition.
If the module already provides that information, shouldn’t an official OpenWrt router make it easy to see?
OpenWrt: Setting the Gold Standard
What better place to make these capabilities accessible than an official OpenWrt device? A router designed around openness and user control seems like a natural place to give users better visibility into the physical connections their network depends on.
I recognize that cost, component availability, and development time all matter. Command-line support would be a perfectly reasonable starting point. A LuCI “Test cable” button, with a warning about any temporary connection interruption, and an optical-diagnostics page could come later. Clear documentation of supported ports and module-dependent limitations would also be valuable.
Are these capabilities already being considered for OpenWrt Two? If the Ethernet hardware has been selected, do its PHYs and Linux drivers provide a practical path to cable testing? And could supported optical-transceiver diagnostics be exposed alongside it?
These may not be the features that sell a router on a specification sheet—but they could be the features someone most appreciates when their network stops working.
