Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Upgrade to 2.5.0 went well AFTER an additional upgrade of the Realtek Ethernet NIC driver

    Hardware
    2
    5
    488
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      RK0 last edited by RK0

      I updated my 2.4 p1 release to 2.5.0. It proceeded smoothly. The system I'm running on is a Lenovo ThinkCentre M90n IoT system, which has two Realtek NICs.
      (not all variations of the M90n have two NICs, so if you see this post and think you can use any M90n as a PFSense machine, be aware of which variants have two, and which have only one NIC...example, I think only the M90n IoT fanless "big heatsink" models have two NICs, and only the i3 processor variants on top of that...check carefully)

      However...after the reboot, some sites would not resolve properly (which was weird).

      There was still one more step I did....for my old 2.4.x install, I had updated the Realtek drivers, since I had heard terrible things about the "old", default Realtek driver included in the FreeBSD build.

      It appears per https://redmine.pfsense.org/issues/11079 the newest drivers for the Realtek NICs are present in the 2.5 build, but (I think) must be manually loaded/activated.

      Anyway, I wasn't sure if that was the case or not, so I did the following...and after that, PFSense (so far) has worked perfectly:

      after logging in as root, I issued the following commands. The install command did take a bit of time to fully execute, so be patient

      pkg search realtek

      pkg install realtek-re-kmod

      (entered y when asked to proceed with this action)

      I then edited the /boot/loader.conf file, and added the recommended lines:

      if_re_load="YES"
      if_re_name="/boot/modules/if_re.ko"

      I then rebooted the system.

      Sidenote: can anyone confirm if upgrading the RealTek NIC drivers must be done with the procedure above with the 2.5.0 build, or does merely upgrading to 2.5.x automatically have the system use the most recent Realtek driver? Maybe I did something unnecessary if the most current driver is actually used after an upgrade without manual intervention...?

      1 Reply Last reply Reply Quote 0
      • R
        RK0 last edited by

        Oh, one other question...if a manual upgrade of the Realtek drivers ARE required because the newest ones are NOT used in the install, is that manual upgrade install of the Realtek drivers required with each subsequent upgrade operation? Does that mean with every upgrade of PFSense, the NIC drivers go backlevel, unless that realtek package is reinstalled each time?

        I'm a PFSense novice, and not sure of the proper Linux command to reveal the NIC version in a way where an administrator can be assured of what version of driver is being used, old, "built in" driver, or new, manually upgraded package install Realtek driver....

        1 Reply Last reply Reply Quote 0
        • stephenw10
          stephenw10 Netgate Administrator last edited by stephenw10

          You should always use the file: /boot/loader.conf.local to add custom loader values because that is not overwritten by pfSense which can happen with the main loader file. Create that file if you don't have one yet.

          Steve

          1 Reply Last reply Reply Quote 0
          • R
            RK0 last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • R
              RK0 last edited by

              Ah, so there is a difference between /boot/loader.conf and /boot/loader.conf.local then...

              from your post, I'm gleaning that...

              /boot/loader.conf could be overwritten by PfSense on subsequent upgrades, BUT

              /boot/loader.conf.local would not be overwritten.

              So...does that mean the values of
              if_re_load="YES"
              if_re_name="/boot/modules/if_re.ko"

              ...should only exist in the /boot/loader.conf.local file?

              Also...lets say I do that. With each subsequent upgrade of PFsense, does that also mean the commands

              pkg search realtek

              pkg install realtek-re-kmod

              must be executed again?

              1 Reply Last reply Reply Quote 1
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy