Realtek RTL8125/8126/8127 new driver 2.5/5/10GBE

Shakroglof said:
Are vlan implemented in this driver ? I installed the package from kmod Latest, on Freebsd 14.3

Edit : the card is a 8125 on an Asus Prime B760-Plus D4 Motherboard
Edit(2) : finally, it worked with
ifconfig rge0 -hwvlantag -hwvlancsum
Click to expand...

Supposed to be.

Does it work with either -hwvlantag or -hwvlancsum on their own?
 
There a strange thing that I noticed, with IPv6 : I found that the machine with the RTL8125 answer to ping from another machine only after I ran tcpdump on it.
After some tests, I found that the NIC starts answering to neighbour solicitations, only after I run ifconfig rge0 promisc.
Then, even after running ifconfig rge0 -promisc the NIC still works properly.
It happens only with IPv6, IPv4 is fine as far as I can tell. FreeBSD is 14.3.
 
Shakroglof said:
There a strange thing that I noticed, with IPv6 : I found that the machine with the RTL8125 answer to ping from another machine only after I ran tcpdump on it.
After some tests, I found that the NIC starts answering to neighbour solicitations, only after I run ifconfig rge0 promisc.
Then, even after running ifconfig rge0 -promisc the NIC still works properly.
It happens only with IPv6, IPv4 is fine as far as I can tell. FreeBSD is 14.3.
Click to expand...

Ya, an issue with the multicast filter. Running tcpdump puts the interface in promiscuous mode working around the bug in the filter setup code.

Thanks. I'll see about getting a system together to test with this weekend and see if I can fix it.
 
it caused me grief cause it seemed fine but when trying to serve windows hosts the wsdd protocol fails to show up after refreshing the windows network neighborhood. was wierd after starting wsdd all looked good until you clicked on it in wndows then it would show it cant connect although by IP is fine.
 
brad0 said:
Ya, an issue with the multicast filter. Running tcpdump puts the interface in promiscuous mode working around the bug in the filter setup code.

Thanks. I'll see about getting a system together to test with this weekend and see if I can fix it.
Click to expand...

This bug hasn't been fixed yet.
 
Oleg_NYC said:
This bug hasn't been fixed yet.
Click to expand...
You'll likely need this commit 2026-07-06; this is where development takes place:
Rich (BB code): 
rge: sync with freebsd
 * 2b5d1d8e298b2f5aff68fd5106d9b09d59fda907 - rge: Fix 32-bit powerpc build
 * 76f9bb488e77ae4cc220b0bbbc53f1a7315ef977 - rge: fix VLAN hardware tagging
 * 92f623e4a98876c897669be0f1220887c996918e - rge: add the Intel Killer E5000 PCI ID
 * 4390c37b5c94b6de4cb4bdbcc3967efe74fa7517 - rge: add disable_aspm tunable for PCIe power management
 * fc68534a9ad93f6df1756ffa8e707c30a35ce4d7 - rge: add Wake-on-LAN support for magic packet
 * 930a790c2abb3680a3449a1f9ce2eff2be7acc36 - rge: make rx_process_limit a sysctl tunable
 * f7fd4e79fa0943446aa5900147f737a70c73d9e3 - rge: handle interface flags changes

 * 9976cff55e8897f74d970567e61512103216cf58 - rge: use C style comments instead of C++

As for the ports tree, you'll need PORTVERSION= 20260706, committed on Jul 6 2026. Wait for the package to appear or build it yourself locally.
 
I am not talking about the VLAN hardware tagging bug. I am talking about the multicast filtering bug. I thought I made it clear by quoting "
Ya, an issue with the multicast filter. Running tcpdump puts the interface in promiscuous mode working around the bug in the filter setup code.

Thanks. I'll see about getting a system together to test with this weekend and see if I can fix it."
 
You must log in or register to reply here.
Back
Top