Package realtek-re-kmod198 for pfSense 2.8.0 (amd64)

stephenw10

You see the same thing? Only RX checksum for IPv6 is still enabled?

[25.03-BETA][admin@apu.stevew.lan]/root: ifconfig -vvm re0
re0: flags=1008803<UP,BROADCAST,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=202018<VLAN_MTU,VLAN_HWTAGGING,WOL_MAGIC,RXCSUM_IPV6>
	capabilities=403c1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,TXCSUM_IPV6>
	ether 00:0d:b9:37:30:10
	inet6 fe80::20d:b9ff:fe37:3011%re0 prefixlen 64 tentative scopeid 0x1
	media: Ethernet autoselect
	status: no carrier
	supported media:
		media autoselect
		media 1000baseT mediaopt full-duplex
		media 100baseTX mediaopt full-duplex
		media 100baseTX
		media 10baseT/UTP mediaopt full-duplex
		media 10baseT/UTP
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	drivername: re0

Looking again though that NIC only supports TX checksum.

zeroepoch

Hi @stephenw10,

I don't remember exactly now and it's different with the older driver I'm currently running, so I can't look it up, but I believe only TXCSUM_IPV6 was removed. For sure TXCSUM and RXCSUM were still there on 1.100.00 after running ifconfig re0 -rxcsum -txcsum -rxcsum6 -txcsum6.

What I get now with disable checksum offloading checked on the 1.98.00 driver is:

[2.8.0-RELEASE][admin@router]/root: ifconfig re0
re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: LAN
	options=2018<VLAN_MTU,VLAN_HWTAGGING,WOL_MAGIC>
	ether xx:xx:xx:xx:xx:xx
	inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x
	inet6 x::x prefixlen 64 scopeid 0x1
	inet6 x::x prefixlen 64 scopeid 0x1
	inet6 x::x prefixlen 64
	media: Ethernet autoselect (2500Base-T <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

In this case everything checksum related was disabled as expected. The 1.100.00 driver as you are seeing as well doesn't allow clearing all the flags. The behavior appears to vary I guess depending on the particular chipset?

stephenw10

Yeah if you run ifconfig -vm re0 it should show you what the driver thinks the hardware is capable of too.

SpunkThing

@zeroepoch

Took me a while but I finally have an update.

Unfortunately it did exactly the same as the 1.100.00 driver.
And to make things even stranger, both these drivers left my pfSense installation inoperable even after uninstalling them.

I've not got the faintest idea what kind of voodoo witchcraft sorcery stuff is at work here.
The first time after installing your version of the 1.98 driver the WAN interface immediately came online after the system rebooted, so I thought bingo!
Less than 3 minutes later it collapsed just like before.

The only difference is that this time it was possible to bring it back online by disabling the interface in the GUI and then enabling it again. Not every time though.

I noticed that in the Gateways widget there sometimes was a downward facing red arrow next to the WAN interface. When this happened it could only be brought up again by first doing ifconfig re0 up via SSH and then the GUI steps.

So after fiddling around for a while I decided I had enough and removed the driver, rebooted and to my shock and horror the same strange thing occurred. The WAN interface was down after booting like with the 1.100.00 driver. It could be brought up either through the GUI or ifconfig + GUI, but like before it always went down within a matter of minutes.

I dug up some other, more recent unused computer parts including a different NIC. Still a Realtek based one, but who knows.
Now putting it together and I'll do a fresh install of pfSense 2.7.2 to see how that works out.

Attached a few screenshots again. Maybe, hopefully there is something useful to be seen in them.
If you'd like any other info about my latest adventure, feel free to ask.

stephenw10

Are you sure it's actually loading either of those drivers and not just hitting a timeout on the in-kernel driver?

You should see the version reported in the boot log if a module is loaded correctly.

zeroepoch

@stephenw10

Thanks for sharing that command! I was reading online 1.99+ added support for IPv6 checksum offloading, which explains why the suggestion to disable IPv6 (set to None) on those interfaces helps somewhat.

For 1.98.00 I get:

capabilities=381b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,WOL_UCAST,WOL_MCAST,WOL_MAGIC>

zeroepoch

@SpunkThing

If I'm reading your output correctly (based on kern.ipc.nmbjumbo9?) you enabled jumbo frames? If not there is an additional setting you can add to /boot/loader.conf.local to fix a possible hang (if not using jumbo frames). I did the following on my system.

By default, the size of allocated mbufs is enough
to receive the largest Ethernet frame supported
by the card.  If your memory is highly fragmented,
trying to allocate contiguous pages (more than
4096 bytes) may result in driver hangs.
For this reason the value is tunable at boot time,
e.g. if you don't need Jumbo frames you can lower
the memory requirements and avoid this issue with:

hw.re.max_rx_mbuf_sz="2048"

My /boot/loader.conf.local looks like:

if_re_load="YES"
if_re_name="/boot/modules/if_re.ko"
hw.re.max_rx_mbuf_sz="2048"

As @stephenw10 suggested you should check dmesg to see what version was loaded.

# dmesg | grep "re[0-9]: version:"
...
re0: version:1.98.00
re1: version:1.98.00

SpunkThing

Hi @stephenw10

Seems to be the case. This screenshot was taken after installing the driver we're discussing here.

Another indication, if I saw that correctly, is that there is no corresponding module in the /boot/modules directory. That's placed there only when installing an alternative driver such as this one if my observations were correct.

Can't verify now as I'm in the process of installing pfSense on a 'new' system.

SpunkThing

@zeroepoch

That's not something I would deliberately enable. At least not that I remember.
Actually I think that's one of those things I used to turn off on network adapters in Windows in the old days because it caused trouble.

But on the other hand I am the type that messes around with settings often while not completely understanding them. So don't rule it out completely.

Anyway, as I said I'm currently working on a fresh installation of 2.7.2 and that version has always worked nicely for me, except for that one problem with the WAN going down under "heavy" loads. Suppose I'll be looking out for better NIC's if it happens again.

I'll restore a recent-ish configuration backup and leave it at that for the time being.

I'll keep following this though if you decide to dive further into it.
Very curious why both drivers were acting up on my system while they work fine for you.
Could be anything, my messing in settings not being the least likely of causes... Hehehe

zeroepoch

@SpunkThing

That's right. There is no /boot/modules/if_re.ko without either of these packages being installed. It wouldn't print this message if you didn't have the driver I provided loaded, so indeed you're using the same driver as me.

zeroepoch

@stephenw10 any chance we can get realtek-re-kmod198 to be part of the official pfSense repo? FreeBSD made the decision to package these two versions separately because both 1.98 and 1.100 both have different bugs but each work best for different NICs.

stephenw10

I'll see what I can do.

Seeking Sense

@zeroepoch Thanks for the information and more importantly the warning.

Was contemplating upgrading my local instance of pfSense this weekend. I am using a dual port 2.5gb Realtek Nic and remembered that I had installed the realtek-re-kmod198-198.00.1400094 driver.

Thankfully I came across your post when searching the forum looking for information regarding an updated driver for pfSense 2.8

If you don't mind can you clarify the build process.

You list steps 1-11 but was wondering if step 1 is to create a FreeBSD 15 VM and then do all the within that VM.

Also in step 1 you say you installed some packages mentioned at https://github.com/nkbali/pfSense-Build. What packages?

Thank you for your efforts and your support of the community.

zeroepoch

@Seeking-Sense

Yes, this was all done in a FreeBSD 15 VM using VirtualBox. I had to change the default network card to VirtIO I believe since the performance with the other NICs was like dial-up modem speeds. I also had to install pkg manually using pkg-static since the auto installer when running pkg didn't work and just hung. I don't remember if I tried installing pkg before or after I fixed the slow network issue.

I just installed all the packages mentioned throughout the page since I wasn't trying to optimize size since I intended to throw away the VM when I was done.

Finding a working commit for the kernel was one of the main challenges. I looked for a commit right before a merge from main that was still 1500029.

rob_denver

thank you so much for this! I have been struggling with getting IPV6 working on my virtualized pfsense within Proxmox so I can have more reliable connections for tailscale. I could only get it to work by using PCI passthrough (vs using a bridge) but that of course required me to directly expose my Realtek ethernet controller which led to many lockups and crashes when IPV6 was enabled. I just installed this and -hopefully- this will give me a stable connection.

Seeking Sense

@zeroepoch Finding bits of time here and there to work on this.

I have FreeBSD 15 Current up and running, cloned and built pfSense src & ports.

My NOOB question relates to the following:

@zeroepoch said in Package realtek-re-kmod198 for pfSense 2.8.0 (amd64):

In FreeBSD-src checkout a new local branch using the commit c665fe00146 (for 2.8.0)

What does that mean? How? ( Looks away and hides in embarrassment.)

What I am asking as a NOOB is how do I get to the correct version so that I can make the correct driver.

Running make as is without selecting the correct branch produces:

realtek-re-kmod198-198.00.1500046

Furthermore when running MAKE in realtek-re-kmod198 I get the following warning:

pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended

zeroepoch

@Seeking-Sense

I meant use a command like git checkout -b tmp c665fe00146 to create a local git branch named tmp for the commit c665fe00146, which I found best represents the 2.8.0 kernel source that I could infer. This was so my local checkout was at the right source. You don't technically need to name the branch but it made it easier for me to compare things with other commits. Sorry for the confusing directions.

Seeking Sense

@zeroepoch said in Package realtek-re-kmod198 for pfSense 2.8.0 (amd64):

Sorry for the confusing directions.

I'm sure they are not confusing for the non-NOOB. It great that you have provided the information and I am grateful for your effort and time.

Please check out my last comment as I made some edits.

Seeking Sense

@zeroepoch Thanks I think I have it worked out.

I have the following in work/pkg:

102K Jun 13 11:43 realtek-re-kmod198-198.00.1500029.pkg

I had skipped your step 10:

"To get the correct __FreeBSD_version I had to temporarily replace /usr/include/sys/param.h with FreeBSD-src/sys/sys/param.h"

zeroepoch

@Seeking-Sense Awesome! Glad to hear someone was able to reproduce my quickly written steps I did late at night