-
@stephenw10 Thank you very much for these instructions. They make it very quick and easy!
-
@stephenw10 Thanks for the details, I also followed the instructions and the install worked with our PFSense box.
However, the newer driver borked the re0: WAN pppoe0 interface, which according to the kernel logs is a RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet add-in card. The connection came up, but it didn't stay up.
The re1: LAN interface (RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet) built-in port seemed to still work fine.
As soon as I went back to the native FreeBSD driver, all was well again. Might there be a problem with different Realtek controllers on the same PFSense install? Would trying a slightly older version of the driver be any value?
Edit: Just saw above that the 8169 chipset is not supported by the 197 driver. Well, ain't that just grand...
-
Hmm, well it must support it to some extent since it did attach and come up initially.
At least it's an add-in card so you can replace it.
Steve
-
@stephenw10 True. But that entire box is meant to be a temporary replacement, until we can find another small low-power PC to take over running PFSense. Are Intel controllers preferable to Realtek ones, or is that no longer an issue?
-
Yes, Intel NICs are almost always preferred.
-
@stephenw10 Okay. Last question, I promise.
Our previous PFSense box has Intel NICs, but we were getting watchdog timeouts on it. Is there an update to the Intel drivers that are as easy to install as the Realtek ones? -
No but the Intel NICs do not hang in the same way when seeing errors like that. You can't really compare the two states.
-
This post is deleted! -
@tgdsilva FYI, 198 is out:
pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-198.00.pkg -
@gradius Thank you! Good addition to this post string!
...if any people has experience with 198 in a production environment, it would be good to hear from them... -
@rk0: Your post raises the following questions:
- What specific edits do I have to make to loader.conf.local?
- What directory is it in?
- Does loader.conf.local supersede loader.conf?
- If so, am I correct in assuming that loader.conf remains unchanged?
I realized just now that Question 1 & 2 are answered in @RK0’s [post from Nov. 28, 2022] (https://forum.netgate.com/post/1072717) and @stephenw10’s post from the same day.
-
@dominikhoffmann it should be the same entries I outlined in this same post string on Nov 28, 2022, 7:16 AM
I did load nano as the editor, just because it is easier.
Putting the entries in /boot/loader.conf.local should just have that file persist if you update PFSense.
You won't have those entries in /boot/loader.conf, unless you already modified it yourself.
Also, when you install the package, it should flash up on the screen the entries it wants you to make, with the difference being it will tell you to put them in /boot/loader.conf vs /boot/loader.conf.local. I just do it in the /boot/loader.conf.local so it will be persistent.
-
@dominikhoffmann said in Updated Realtek NIC drivers missing in PfSense 2.6.0:
Does loader.conf.local supersede loader.conf?
If so, am I correct in assuming that loader.conf remains unchanged?Yes and yes.
But, as said, mainly you use the .local file because it will survive pfSense updates/changes that may otherwise re-write the main loader.conf file.
Steve
-
@rk0 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:
I then issued the commands to download the revised Realtek drivers from freebsd
fetch -v https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-197.00.pkg pkg install -f -y realtek-re-kmod-197.00.pkgBecause my Protectli PC with two Realtek NICs had difficulty with one of them, I had trouble controlling it via the WebConfigurator or ssh on the LAN port, while there was an active internet connection. I managed to copy the PKG file over to the Protectli via a USB thumb drive. But then the
pkg install -f -y realtek-re-kmod-198.00.pkgcommand did not work, because there was no active internet connection. A bit of a chicken-and-egg problem.
I think, I’ll wait for the next major version beyond 2.6.0 and hope that the drivers will be included.
By the way the 197 drivers are no longer at pkg.freebsd.org, although the 198 drivers are.
-
@dominikhoffmann just use "pkg add" instead
-
@stephenw10 is there any chance the Realtek 198 drivers will be natively integrated into the next public release of PfSense?
Or...is this impossible since PFSense will probably move to FreeBSD 14.x? Looking at https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/ I get a "forbidden" message, unfortunately.
-
The kmod pkg is in our repo for pfSense 2.7 and 23.01 so installing it there is much easier.
It's unlikely they will be used instead of the native driver by default though. At least not any time soon.
Steve
-
@stephenw10 any word on what that native realtek ethernet package driver version would be for FreeBSD 14? I ask because the previous realtek ethernet native driver version in FreeBSD 12.x (and PfSense) was problematic with the native realtek driver at the time, while the 197 and 198 driver seems to run well.
this site implies 198 exists for FreeBSD 14, but doesn't explicitly say it will be the native driver, and I can't say its in any way authoritative.
https://www.freshports.org/net/realtek-re-kmod/ -
It does. Freshports is pretty accurate, I don't think I've seen it wrong.
The native FreeBSD driver doesn't use the same numbering scheme as Realteks driver:
https://github.com/freebsd/freebsd-src/blob/main/sys/dev/re/if_re.c -
@stephenw10: Can you comment on when those versions will be out?
