Updated Realtek NIC drivers missing in PfSense 2.6.0

[sokeada]

@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.

[stephenw10]

Check the console when that happens. If you see watchdog timeout errors fro the NIC try the alternative Realtek driver.

Steve

[sokeada]

@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

[stephenw10]

he pkg listed above should still work: https://forum.netgate.com/post/1025825

Steve

[sokeada]

@stephenw10 thanks you so much, I really appreciate that.

[sokeada]

@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?

[stephenw10]

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.

[sokeada]

@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.

[fireodo]

@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.

[sokeada]

@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.

here is the last two line I modify in /boot/loader.conf

Hope I'm doing correctly as now my pfSense not yet reboot.

[sokeada]

@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.

[SteveITS]

@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.

[stephenw10]

Yup 2 error packets is really nothing.

You should use the file loader.conf.local, as @fireodo said, not loader.conf.

Steve

[sokeada]

@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.

[sokeada]

@stephenw10 thanks bro, so I just created new loader.conf.local in side /boot directory and paste the two lines of script in -> save -> reboot? any permission need to be set on that new conf file?

[stephenw10]

No, the default file permissions should be fine there.

[sokeada]

@stephenw10 thanks bro, I'll make one then.

[sokeada]

@steveits @stephenw10 bros, WAN Errors Out keep increasing, am I doing not correctly?

Note: my pfSense box is a single NIC system unit, I used VLAN for my WAN interface.

[stephenw10]

Are you actually seeing connection issues?

That's still not a huge number but more concerning if there have not been disconnections.

What is the WAN interface physically connected to?

[sokeada]

@stephenw10 on pfSense, I set VLAN10 for WAN Interface. On Dell Power Connect 2800 series switch, I set port 1 as trunk/tagged and connected to pfSense box with a sing NIC port and I set port 2 as access/untagged with PVID10 to carry WAN traffic from port 2 to pfSense box.

This morning, I didn't get any complain from users about disconnection or lost and my team also didn't get any connection lost either but WAN error out keep increasing. Now (night time here) I have remoted to disable all hardware offload in Advance -> Networking as I see it might have problem with RealTek driver as description. After system reboot till now seem no any error out yet but there is not much traffic, the traffic in this statistic is from my system and my team desktops that we leave it on 24/7. Let's see if the error will happen again next week.