Updated Realtek NIC drivers missing in PfSense 2.6.0

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.

stephenw10

I'm not sure what details the Realtek driver reports but you might check the sysctl stats to see if it shows you what type of errors those are.

sokeada

@stephenw10 thanks for your tips, I'll try it out soon.

sokeada

@fireodo said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

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

thanks bros @fireodo @stephenw10 for the tips and instruction, you guys have made my day, now everything look fine after few days running and another problem I faced before driver update was, I can't plug my Ubiquiti PoE Switch into the network with pfSense box, every time I plugged in, the whole network goes down but now I can attached Ubiquiti into pfSense network without any issue except VLANs Errors Out (WAN, PDA, Guest) but seems no any disconnect issue, I'm not sure if RealTek NIC coz those error.

Anyways, thanks you guys for helping, I really appreciate that.

stephenw10

Are those VLANs all on the same NIC?

Steve

RK0

I use PFsense, a realtek NIC, and Unifi switch with VLANs, and it all works without error. My PFSense system only has two ethernet ports, both realtek. One is WAN, one is LAN.

On the unifi switch for the port connected to PFsense, the port profile is set to "All"
The LAN interface on the PFSense system is re1
re1 is assigned as the parent interface for every VLAN

Make sure your MTU setting is blank on the Realtek NICs

Under system > advanced > network, I have the following selected:

Hardware Checksum Offloading is checked
Hardware TCP Segmentation Offloading is checked
Hardware Large Receive Offloading is checked

hn ALTQ support is unchecked
ARP Handling is unchecked
Reset All States is unchecked

Is this how your setup is?

sokeada

@stephenw10 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

Are those VLANs all on the same NIC?

Steve

yes bro, all VLANs are on the same NIC. LAN is running on native VLAN, the rest are one different VLAN on the same LAN NIC.

sokeada

@rk0 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

I use PFsense, a realtek NIC, and Unifi switch with VLANs, and it all works without error. My PFSense system only has two ethernet ports, both realtek. One is WAN, one is LAN.

On the unifi switch for the port connected to PFsense, the port profile is set to "All"
The LAN interface on the PFSense system is re1
re1 is assigned as the parent interface for every VLAN

Make sure your MTU setting is blank on the Realtek NICs

Under system > advanced > network, I have the following selected:

Hardware Checksum Offloading is checked
Hardware TCP Segmentation Offloading is checked
Hardware Large Receive Offloading is checked

hn ALTQ support is unchecked
ARP Handling is unchecked
Reset All States is unchecked

Is this how your setup is?

My pfSense box have only one NIC (re0) as parent interface. UniFi PoE switch port profile set to all to carry all VLANs as yours. MTU are blank for all interfaces as yours. System -> advance -> network as yours except hn ALTQ support, I'm going to uncheck now.

Note: When I'm using stock driver, I can't plug my UniFi switch into the network, every time I plug in, the whole network goes down but after driver v194.04 installed, UniFi switch can be used normally but I've error out as above.

RK0

@sokeada wait...your system has only one LAN interface as re0...?

What is the WAN interface on?

sokeada

@rk0 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

@sokeada wait...your system has only one LAN interface as re0...?

What is the WAN interface on?

WAN is using VLAN10 so WAN interface is re0.10 and LAN re0 as parent interface.

stephenw10

Strange you do not see errors on all interfaces then if they are using the same NIC.

Maybe a VLAN config error in the switch?

Does that driver report anything in the sysctl mac stats? Can you see what type of error it is?

sokeada

@stephenw10 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

Strange you do not see errors on all interfaces then if they are using the same NIC.

Maybe a VLAN config error in the switch?

Does that driver report anything in the sysctl mac stats? Can you see what type of error it is?

I'm not sure but VLAN seems working fine, looks like no any complain about connection dropped and clients on different VLAN also can connect to the Internet. Bro, how can I use sysctl mac stats? I tried like this, message as below:

RK0

@sokeada What device is tagging the WAN frames coming into the PFsense box with (I assume) "10" before they hit re0?

You may be better served here adding an additional physical NIC that is supported by PFSense as your WAN interface....

sokeada

@rk0 said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

@sokeada What device is tagging the WAN frames coming into the PFsense box with (I assume) "10" before they hit re0?

You may be better served here adding an additional physical NIC that is supported by PFSense as your WAN interface....

I assigned port 1 as tagged and connect to pfSense box, and I assigned port 2 as untagged port with PVID10 for WAN cable. I'm using Micro System Unit so no slots to add any card.

stephenw10

@sokeada said in Updated Realtek NIC drivers missing in PfSense 2.6.0:

Bro, how can I use sysctl mac stats?

Like:

[22.05-RELEASE][admin@apu.stevew.lan]/root: sysctl dev.re
dev.re.2.int_rx_mod: 65
dev.re.2.stats: -1
dev.re.2.%parent: pci3
dev.re.2.%pnpinfo: vendor=0x10ec device=0x8168 subvendor=0x10ec subdevice=0x0123 class=0x020000
dev.re.2.%location: slot=0 function=0 dbsf=pci0:3:0:0
dev.re.2.%driver: re
dev.re.2.%desc: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
dev.re.1.int_rx_mod: 65
dev.re.1.stats: -1
dev.re.1.%parent: pci2
dev.re.1.%pnpinfo: vendor=0x10ec device=0x8168 subvendor=0x10ec subdevice=0x0123 class=0x020000
dev.re.1.%location: slot=0 function=0 dbsf=pci0:2:0:0
dev.re.1.%driver: re
dev.re.1.%desc: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
dev.re.0.int_rx_mod: 65
dev.re.0.stats: -1
dev.re.0.%parent: pci1
dev.re.0.%pnpinfo: vendor=0x10ec device=0x8168 subvendor=0x10ec subdevice=0x0123 class=0x020000
dev.re.0.%location: slot=0 function=0 dbsf=pci0:1:0:0
dev.re.0.%driver: re
dev.re.0.%desc: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet
dev.re.%parent:

That's the default driver and doesn't tell you much. The alternative driver may tell you more.

Do you see input errors on the switch?

If you use a different switch do you still errors on the re NIC? Even just a different port on the same switch?