@Andrew Thank you! That driver works.

Hello,

I have a problem with the LAN connection on my NUC I want to run XCP-ng on.
The NIC in that device is the RTL8125BG-CG, 2.5G.

The status lights on the NIC are on until I´m trying to send a package to the device or trying to do something network related in the device (for example ping to XCP-ng or ping from XCP-ng), in that moment the light on the NIC will go off for a few seconds go back on again and go off again.

In the logs I found the following:

Feb 15 22:18:48 xcp-ng-nuc-01 kernel: [   41.454249] r8125: eth0: link down
Feb 15 22:18:51 xcp-ng-nuc-01 kernel: [   44.902253] r8125: eth0: link up
Feb 15 22:19:04 xcp-ng-nuc-01 kernel: [   57.582241] r8125: eth0: link down
Feb 15 22:19:08 xcp-ng-nuc-01 kernel: [   61.074237] r8125: eth0: link up
Feb 15 22:19:20 xcp-ng-nuc-01 kernel: [   73.454273] r8125: eth0: link down
Feb 15 22:19:23 xcp-ng-nuc-01 kernel: [   76.946250] r8125: eth0: link up
Feb 15 22:20:24 xcp-ng-nuc-01 kernel: [  137.454219] r8125: eth0: link down
Feb 15 22:20:27 xcp-ng-nuc-01 kernel: [  140.898166] r8125: eth0: link up
Feb 15 22:20:34 xcp-ng-nuc-01 kernel: [  147.438230] r8125: eth0: link down
Feb 15 22:20:37 xcp-ng-nuc-01 kernel: [  150.890227] r8125: eth0: link up
Feb 15 22:20:50 xcp-ng-nuc-01 kernel: [  163.566212] r8125: eth0: link down
Feb 15 22:20:53 xcp-ng-nuc-01 kernel: [  167.026222] r8125: eth0: link up
Feb 15 22:21:00 xcp-ng-nuc-01 kernel: [  173.550207] r8125: eth0: link down
Feb 15 22:21:03 xcp-ng-nuc-01 kernel: [  177.014173] r8125: eth0: link up
Feb 15 22:21:22 xcp-ng-nuc-01 kernel: [  195.566219] r8125: eth0: link down
Feb 15 22:21:25 xcp-ng-nuc-01 kernel: [  199.030213] r8125: eth0: link up
Feb 15 22:21:32 xcp-ng-nuc-01 kernel: [  205.550218] r8125: eth0: link down
Feb 15 22:21:35 xcp-ng-nuc-01 kernel: [  209.006211] r8125: eth0: link up
Feb 15 22:21:48 xcp-ng-nuc-01 kernel: [  221.422184] r8125: eth0: link down
Feb 15 22:21:51 xcp-ng-nuc-01 kernel: [  224.882217] r8125: eth0: link up
Feb 15 22:22:04 xcp-ng-nuc-01 kernel: [  237.550210] r8125: eth0: link down
Feb 15 22:22:07 xcp-ng-nuc-01 kernel: [  240.998114] r8125: eth0: link up
Feb 15 22:22:50 xcp-ng-nuc-01 kernel: [  283.374203] r8125: eth0: link down
Feb 15 22:22:53 xcp-ng-nuc-01 kernel: [  286.898193] r8125: eth0: link up
Feb 15 22:23:06 xcp-ng-nuc-01 kernel: [  299.502191] r8125: eth0: link down
Feb 15 22:23:09 xcp-ng-nuc-01 kernel: [  302.970201] r8125: eth0: link up
Feb 15 22:23:22 xcp-ng-nuc-01 kernel: [  315.374200] r8125: eth0: link down
Feb 15 22:23:25 xcp-ng-nuc-01 kernel: [  319.014201] r8125: eth0: link up
Feb 15 22:23:38 xcp-ng-nuc-01 kernel: [  331.502303] r8125: eth0: link down
Feb 15 22:23:42 xcp-ng-nuc-01 kernel: [  335.210190] r8125: eth0: link up
Feb 15 22:27:36 xcp-ng-nuc-01 kernel: [  569.582127] r8125: eth0: link down
Feb 15 22:27:40 xcp-ng-nuc-01 kernel: [  573.062138] r8125: eth0: link up
Feb 15 22:27:46 xcp-ng-nuc-01 kernel: [  579.566147] r8125: eth0: link down
Feb 15 22:27:50 xcp-ng-nuc-01 kernel: [  583.162141] r8125: eth0: link up
Feb 15 22:28:02 xcp-ng-nuc-01 kernel: [  595.438125] r8125: eth0: link down
Feb 15 22:28:05 xcp-ng-nuc-01 kernel: [  598.854128] r8125: eth0: link up
Feb 15 22:28:18 xcp-ng-nuc-01 kernel: [  611.566156] r8125: eth0: link down
Feb 15 22:28:21 xcp-ng-nuc-01 kernel: [  614.990136] r8125: eth0: link up

I hope that someone has an idea how this can be fixed.