Updated Realtek NIC drivers missing in PfSense 2.6.0
-
@stephenw10 Oh got it. I manually installed it via this thread. So when I upgrade to the next version release it should remain?
-
stephenw10 Netgate Administratorlast edited by stephenw10 Apr 25, 2022, 12:22 PM Apr 25, 2022, 12:18 PM
Unclear! Since that pkg also doesn't exist in out repo but also has not been replaced specifically.
Let me see if I can test that....
Well I can say it is not removed at upgrade between snapshots.
Steve
-
Forever ago I did the realtek install on the 2.5.x box I do most of my testing and home stuff on. Worked beautifully and finally no network failures.
I then upgraded to 2.6 and the plus versions; all seemed to hold the driver ok.2 days ago I swapped out the hard drive and reloaded the config.
Today it crashed down again; re1 down up down up down...Obviously now I'm very interested in getting the realtek driver back inito the fold properly.
Just added from freebsd directly and recreated the .local file; seems to have loaded the driver fine upon reboot. Fingers crossed it doesn't derp anymore.
-
It's pretty simple to check if the correct driver is loaded: In the log check for the part where the driver is displayed (just search for realtek).
If you find this:
🔒 Log in to view
It's the wrong driver.If you find this:
🔒 Log in to view
It's the correct driver. -
@stephenw10 Hello, I've Dell OptiPlex 3040 Micro with single NIC and its driver shown re0 8168/8111 so pfSense 2.6.0 will support this re NIC out of the box right?
-
Yup, it should do. Using the native FreeBSD driver.
-
@stephenw10 thanks for the confirmation as my pfSense got hanged sometime after few days of operation and I have no clue so I thought its from the re NIC. What I've noticed only LAN package error out and I tried to do some research but not luck.
-
Check the console when that happens. If you see watchdog timeout errors fro the NIC try the alternative Realtek driver.
Steve
-
@stephenw10 thanks, I'll check it out again soon. Would you mind to link me to the correct alternate driver your mention above? for pfSense 2.6.0. Appreciate yours.
Sokeada
-
he pkg listed above should still work: https://forum.netgate.com/post/1025825
Steve
-
@stephenw10 thanks you so much, I really appreciate that.
-
@stephenw10 bro, I can see only one watchdog time out. This could be happened while I'm switching the network cable and restoring config from the backup or NIC driver issue?
-
Were you still able to connect to it after that point? If so it was probably just the cable reconnect but in normal use you should never see that message.
-
@stephenw10 yes I still be able to connect. My problem is after few days of running then it got hanged and I can't even connect or ping. Now I've installed driver you recommend and modify the /boot/loader.conf as required but not yet reboot pfSense as now there are lots of traffic from users. I'll reboot pfSense when time to leave office and see what's next. Hope this will solve my issue.
-
@sokeada said in Updated Realtek NIC drivers missing in PfSense 2.6.0:
Now I've installed driver you recommend and modify the /boot/loader.conf
I chime in with just a little remark: you should make the changes in "loader.conf.local" and if this file dont exist - create it. Changes in loader.conf will be rewritten on updates.
-
@fireodo thanks for the tip bro, the /boot/loader.conf does exist and I just added two lines of code that the driver required. Here is the message after driver install.
🔒 Log in to viewhere is the last two line I modify in /boot/loader.conf
🔒 Log in to viewHope I'm doing correctly as now my pfSense not yet reboot.
-
@stephenw10 @fireodo bros, after rebooted pfSense, I can see the driver was changed to the one that I installed and no watchdog error anymore but I've WAN Error Out as attached, any comments, please.
-
@sokeada said in Updated Realtek NIC drivers missing in PfSense 2.6.0:
WAN Error Out
Is the number increasing over time? If not I wouldn't worry about it.
-
Yup 2 error packets is really nothing.
You should use the file loader.conf.local, as @fireodo said, not loader.conf.
Steve
-
@steveits I've reboot pfSense again last night till now (morning time) there is no any error in or out yet. I'll keep you post when people come to work.
thanks bro.