Official Realtek Driver Binary 1.95 For 2.4.4 Release


  • «Disable hardware checksum
    Was not fixing the problem....

    Does anybody know how I can auto disable and enable the card when it goes down?

  • LAYER 8

    try with
    /etc/rc.d/netif restart re0


  • @kiokoman said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    try with
    /etc/rc.d/netif restart re0

    Thank you, I need some script to detect when it shall happens also...

    I found some things to try another place on these forum, so I have added these lines to the boot config:
    net.inet.tcp.tso=0
    hw.pci.enable_msix=0
    hw.pci.enable_msi=0
    hw.re.tso_enable=0

    to the boot loader config, and for now I haven`t seen the issue again, need more hours... will report back later.

  • Netgate Administrator

    Yes, definitely disable all hardware offloading features. Check what is still enabled using ifconfig re1.

    Did you try re-assigning the NICs? Does the fault follow re1 or remain on WAN?
    It's likely you are downloading far more traffic that uploading. Whichever NIC is WAN is doing the receiving of that traffic and a number of those hardware offloading features are receive only.

    Steve


  • @stephenw10 said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    Yes, definitely disable all hardware offloading features. Check what is still enabled using ifconfig re1.

    Did you try re-assigning the NICs? Does the fault follow re1 or remain on WAN?
    It's likely you are downloading far more traffic that uploading. Whichever NIC is WAN is doing the receiving of that traffic and a number of those hardware offloading features are receive only.

    Steve

    I reinstalled the whole pfsense yesterday and then I swapped so re0 is WAN and re1 is LAN.
    The problem have always followed the card I have assigned to be WAN.

    The problem has not accour after I disabled al the things mention above from the HW i the boot loader. But there is a strange thing the uptime on the box is never 1 hour and 47 minutes, but I have not restarted the box today..... I think there are something wrong with the clock... its not going correct... it`s deviate more and more from the "real time"....

    Maybe there is a releation here ? lead time on the DHCP maybe got problem...

    I will look into getting the clock correct first.

  • Netgate Administrator

    Make sure NTP is configured and working. All APUs are old now, the CMOS battery may be dead.

    Edit: Is this an APU? Not sure where I pulled that from.. 🙄

    Steve


  • This post is deleted!

  • @TheNarc

    I just subscribed to thank you for your work,
    I was going mad trying to understand the issue and finally this morning I found a post that directed me here.

    The issues I had on my ci323 nano seems all solved now.

    thanks again


  • @TheNarc, just wanted to thank you and post an interesting update.
    Apparently your fix also solves an issue I had been experiencing with passing the realtek card through to a VM running Pfsense on a Centos 8 host.
    Running on J4105-ITX motherboard.
    The error occured with pretty much any realtek card I tried including the onboard one.
    Until now, it would give an nasty DMAR error and the card would always stop working after pfsense VM reboot.
    Sometimes, it would show a watchdog timeout, sometimes would just quetly stop responding.
    With this driver, the card is stable and there is no DMAR error in Host's dmesg.


  • I've had three Zotac CI32x boxes deployed, running pfsense for a few years now, and I had not run into the dreaded watchdog timeout error until after upgrading to pfSense 2.4.4. Now the lan interface of two out of three boxes goes silent about once a month. Fortunately, since it it is the lan interface, I just reboot them remotely.

    Thanks for doing the work building this driver. This saved me quite a bit of time.

    Question:
    With this new driver, can/should I re-enable hardware offloading under Advanced-> Networking?

    I've also got the following set in loader.conf.local. These were suggested as workarounds in another thread. Is it safe to remove these?
    hw.re.msi_disable=1
    hw.pci.enable_msix=0
    hw.pci.enable_msi=0


  • @knnniggett I'm glad to hear the driver has been useful. I'm sorry to hear about the LAN interface flakiness; that's not something I've seen (yet) in on the two CI323s I run. With regard to your questions:

    I would not recommend re-enabling hardware offloading. I believe that Realtek claims to support it, but from what I understand it can be prone to bugginess and you're unlikely to see any tangible benefit from it. Also, it's the sort of thing that (I think) you wouldn't necessarily know right away if it works. So you might try it and it would seem fine, but some time down the line you'd have a problem and, if you're anything like me, probably forget that you'd changed that setting a while back and not immediately realize that it's related.

    As for the loader.conf.local entries, at least based on my experience it should be fine to get rid of them. I don't have them set on either of my boxes right now and haven't had any issues.


  • @knnniggett said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    I've had three Zotac CI32x boxes deployed, running pfsense for a few years now, and I had not run into the dreaded watchdog timeout error until after upgrading to pfSense 2.4.4. Now the lan interface of two out of three boxes goes silent about once a month. Fortunately, since it it is the lan interface, I just reboot them remotely.

    Thanks for doing the work building this driver. This saved me quite a bit of time.

    Question:
    With this new driver, can/should I re-enable hardware offloading under Advanced-> Networking?

    I've also got the following set in loader.conf.local. These were suggested as workarounds in another thread. Is it safe to remove these?
    hw.re.msi_disable=1
    hw.pci.enable_msix=0
    hw.pci.enable_msi=0

    I do not have these anymore either with the new driver.

    Should be good to remove.


  • I made myself a new router after my previous one failed(power supply fried).

    I got myself a GIGABYTE GA-N3160N-D3V motherboard with an embedded CPU and DUAL NIC's perfect for making a nice small compact router with pfsense. Everything was hunky-dory for a few months with no issues until one day I started encountering this "watchdog timeout" issue.

    I thought that the CPU had overheated and bent the solder like how the Xbox 360 did with the RROD. The CPU was only at 65 degrees Celcius...

    I installed fans in the case and ensured that the temp never grew past 40 degrees Celcius. The issue still persisted and I thought I would now need to RMA the board.

    As I cannot go without internet for longer periods of time due to working from home I needed to get my original pfsense router up and running before sending this board in.

    Whilst in the process of doing so I was doing some uploading of work to Jira when one gif file would repeatedly kill the router. I was stunned, how on earth could a 2mb file kill the router?!?!?!

    I thought I would do one last search online to see if I could find anything software related that might be the issue and I stumbled upon this thread.

    I can confirm that applying the Realtek driver has now solved my issue!

    Thank you!


  • I just ran into a situation similar to @fromage9747, but with a cheapo mini-pc that has two realtec nics of the type discussed above. Worked fine for months, but today watchdog timer started timing out every few minutes. After updating the driver, it hasn't happened yet.

    I followed this post:

    https://forum.netgate.com/post/799000


  • @Zcool31

    Exact same thing... Just updated. We will see what happens..

    Thanks all!


  • @Zcool31 @bedpan Going onto two weeks now without another watchdog timeout. Pretty confident the issue is fixed. But dam, what a pesky issue! I was going to RMA the board. Good thing I didn't!


  • @fromage9747
    Thanks for the followup. Nice to know this is likely dealt with.. A few hours now and problem free.


  • Just for confirmations is anybody upgraded to 2.4.5 with FreeBSD 11.3?

    Any issues or should it be good to go?


  • @Napsterbater Did you take the leap and try 2.4.5 with this driver?


  • Full disclosure: I have not yet tested this and do not know if it is necessary, but I did recompile the v1.95 Realtek driver under FreeBSD 11.3. I'm planning to test it on my pfSense machines within the next day or two and will report back.
    if_re_ko_v195_FREEBSD-11.3_64bit.zip


  • Installed the driver I attached to my previous post w. 2.4.5 and all is well so far . . . will report back if anything goes sideways.


  • @TheNarc said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    Full disclosure: I have not yet tested this and do not know if it is necessary, but I did recompile the v1.95 Realtek driver under FreeBSD 11.3. I'm planning to test it on my pfSense machines within the next day or two and will report back.
    if_re_ko_v195_FREEBSD-11.3_64bit.zip

    Install this updated driver on one box and then updated to 2.4.5, its booted and running. So far so good.


  • @Derelict said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    /boot/loader.conf.local

    Also note after upgrade run "kldstat" to confirm if_re.ko loaded.

    If not make sure you have

    if_re_load="YES"

    in /boot/loader.conf.local NOT /boot/loader.conf as /boot/loader.conf is overwritten on upgrade.


  • Has anyone had trouble with RTL810xE chipsets? Would this driver cover those?


  • @coreybrett from what I can tell. This driver should work with it.

    But worst case be ready to edit the loader.conf.local from the console and remove the reference to it just in case..

  • Netgate Administrator

    Yes, there's only one driver, re(4), for all the Realtek Gigabit NICs. It should work for that.

    Are you actually seeing issues though? I would only use the alternative driver if you are.

    Steve


  • @stephenw10 to be clear that model is a fast ethernet not a gigabit. If that makes a difference.

  • Netgate Administrator

    Ah, been a while since I saw one of those. It's listed as supported by re(4) though so it's probably good.
    Though I would recommend not using it at all if there is any other option. The Realtek 100M NICs were terrible.
    I hope it's better than the rtl8139: https://github.com/freebsd/freebsd/blob/master/sys/dev/rl/if_rl.c#L48 😉

    Steve


  • Compiled on FreeBSD 11.3-STABLE (last):

    if_re.zip


  • @coreybrett

    I have a bunch of HP motherboards that have them:

    re0@pci0:3:0:0: class=0x020000 card=0x2b05103c chip=0x813610ec rev=0x07 hdr=0x00
        vendor     = 'Realtek Semiconductor Co., Ltd.'
        device     = 'RTL810xE PCI Express Fast Ethernet controller'
        class      = network
        subclass   = ethernet
    

    I don't currently use this interface with my pfSense box but I did for a while and it was fine with the driver that ships with pfSense. By "fine" I mean it wasn't obviously broken in any way.

  • Banned

    I just updated it and it really increases the software performance very well. Thank you very much for this contribution, it is very appreciated.


  • @pereirara24 do you still have to check the box ofr the three options below in system advanced networking:
    Disable hardware chekcsum offload
    Disable hardware tcp segmentation offload
    Disable hardware large received offload

    I am running stock now and my box hangs when i do large transfer over the network sometimes

    Thank you.


  • @steeletanner I would say yes.

  • Netgate Administrator

    Yes, I would disable all hardware offloading if you're seeing an issue.

    Do you see anything logged when this happens? Any sort of crash report when you reboot?

    Steve


  • Using this driver for months on 2.4.4 without problems. Now, after upgrade to 2.4.5 I'm getting lots of errors with driver loaded. Without driver loaded, the troughput TO firewall is only around 580mbit but no errors. Traffic FROM firewall is round about 970 mbit. Generating traffic with iperf Server on pfSense. Using the compiled driver version for FreeBSD 11.3 as postet above.

    I'm using VLAN on LAN. WAN interface is free of errors.

    c407d936-2245-4552-9e83-496b106aa4b3-grafik.png

    Any ideas? Disabled hardware checksum offloading without effect.


  • @TheNarc Thank you so much. I was about to replace my Qotom N3150 based firewall as, much like others, on recent releases of pfsense the nics would just stop responding under high load. Fingers crossed this fixes it.


  • @Griffo said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    I was about to replace my Qotom N3150 based firewall

    I have one of these Qotom N3150 and I have never had any issues since updating the drivers over 12 months ago. It just keeps 'trucking' along and only gets rebooted for an update.


  • Driver if_re.ko no longer ,loaded on pfSense 2.4.5-p1, worked fine on versions before.

    Error in dmesg on kldload -nv /boot/kernel/if_re.ko
    KLD if_re.ko: depends on kernel - not available or version mismatch
    linker_load_file: Unsupported file type


  • @wkn said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:

    Driver if_re.ko no longer ,loaded on pfSense 2.4.5-p1,

    Just checked my dmesg and did not find any errors related to if_re.ko in 2.4.5-p1.


  • @gregeeh

    Is the driver loaded for you, shown in kldstat?

    For me it is not loaded on boot with no error shown in dmesg either. The error is only after manual try with kldload.

    [Solved]
    Recompiled driver for me on latest 11.3-RELEASE. Now works again.