Realtek RTL8125BG 2.5GbE Ethernet Controller: Specs and Drivers

Realtek describes the RTL8125BG and RTL8125BGS as integrated 10/100/1000M/2.5G Ethernet controllers for PCI Express applications. The controller combines the Ethernet MAC, four-speed transceiver, PCIe bus controller and embedded memory, and Realtek lists motherboard, notebook and embedded-system Ethernet among its applications.

The 2.5 Gb/s figure is the Ethernet link capability, not a guaranteed application transfer rate. A real connection still depends on the peer switch, router or NIC, the cable, protocol overhead and the systems moving the data. A motherboard advertising an RTL8125BG therefore identifies the LAN controller, not the measured speed of the entire network path.

Realtek lists IEEE 802.3bz 2.5GBASE-T support and compatibility with the NBASE-T PHY specification. Its product documentation states that high-speed transmission is supported over Cat 5e UTP cable, while 10 Mb/s operation can also use Cat 3.

That controller capability should not be turned into a blanket cabling diagnosis. Installed cable quality, termination, patch panels, wall runs and the far-end port all affect whether a link negotiates at 2.5 Gb/s. The RTL8125BG also supports lower Ethernet rates, so a 1 Gb/s negotiated link is possible without implying that the controller itself lacks 2.5GbE capability.

Realtek specifies PCI Express 2.1 for host communication and lists a one-lane 2.5/5 Gb/s PCI Express bus. This is the internal connection between the Ethernet controller and the host platform; it is separate from the copper Ethernet link on the RJ-45 side.

A motherboard vendor still determines how the chip is wired, powered and exposed, and a discrete NIC adds its own PCB and physical implementation. Controller specifications therefore cannot be used to infer every port-layout, lane-sharing or board-level behavior of a particular PC.

The RTL8125BG feature list includes IPv4/IPv6 TCP/UDP checksum offload, large-send offload, quad-core Receive-Side Scaling, ARP and neighbor-solicitation protocol offload, MSI and MSI-X interrupts, and jumbo frames up to 16K bytes. It also supports IEEE 802.1Q VLAN tagging and IEEE 802.3az Energy Efficient Ethernet.

These features describe what the controller can support. The operating system, driver, motherboard firmware, network configuration and peer equipment determine which features are actually enabled and useful. In particular, jumbo frames require a compatible end-to-end path, and RSS/MSI-X capability should not be translated into an invented universal gaming-latency or CPU-usage gain.

Realtek documents the RTL8125BG and RTL8125BGS together but identifies a built-in switching regulator on the RTL8125BGS only. The family also supports link-down power saving, PHY-disable mode, Latency Tolerance Reporting and PCIe L1.1/L1.2 substates.

Those controller-level power features do not define the total power behavior of a motherboard or add-in card. Board design, firmware and driver policy remain separate implementation layers.

Realtek’s current PCIe Ethernet download page groups RTL8125, RTL8125B(G), RTL8125D and RTL8125K under its 2.5G PCI Express controller software. As checked on September 24, 2026, the page lists a Windows 10/11 NDIS auto-install package updated August 28, 2026 and a Linux r8125 driver updated July 3, 2026 for kernels up to 7.1.

Those download listings are current vendor-package information, not a claim that every PC must install Realtek’s standalone package. Windows Update, an OEM package or a Linux distribution kernel may already provide an appropriate driver. For troubleshooting, identify the exact controller and current driver path before replacing a working platform-supplied driver.

Two motherboards can use the same RTL8125BG controller while differing in firmware, driver packaging, connector protection, board routing and the rest of their network implementation. Likewise, Realtek’s optional Dragon bandwidth-control software is a software feature around supported Realtek hardware, not part of the Ethernet standard itself.

Use the controller reference to establish silicon-level capabilities. Use the motherboard, notebook or add-in-card documentation for the actual port implementation, and diagnose negotiated link rate and measured throughput as separate end-to-end questions.