opnsense / opnsense/src

RTL8111E not working in 26.7, 26.1, worked fine in all previous releases, RTL8111G works still

Open
#307 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

upstream
Dominant language
C
Stars
505
Forks
202
PR merge metrics
No merged PRs in 30d

Description

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

This started with this forum thread: https://forum.opnsense.org/index.php?topic=52060
In this message:
https://forum.opnsense.org/index.php?topic=52060.msg268284#msg268284
It was suggested I file a report here.
I have done some more testing and found that this NIC is just not working at all as of 26.1, nor 26.7. I did a clean install of 26.7 (not upgrades) and it's the same problem - the NIC just isn't powering up at all. It still works fine with 25.7.
The physical chip is labeled:
RTL8111E
B9C77G1
GB48B

The biggest issues I have, is that this doesn't seem to be announced in ANY of the changelogs I've found, but certainly not the one presented at upgrade time.

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)

I manually validated by manually installing 25.7, 26.1, and 26.7 multiple times, but did not use "opnsense-revert".

To Reproduce

Steps to reproduce the behavior:

  1. Install either 26.1 or 26.7 using any method (upgrade, fresh install, etc)
  2. Observe that the NIC does not work, lights don't blink, no networks are detected, etc., though the interface is still detected as re0
  3. Install 25.7
  4. See that the NIC works perfectly fine, with and without the os-realtek-re package.
    Expected behavior

NICs should not be soft-bricked on upgrades, or clean installs, without a clear changelog indicating it will happen.

Describe alternatives you considered

I do not have an alternative since this is the NIC soldered to the motherboard. I did start a forum post to try do address first.

Screenshots

n/a since the webUI is unreachable. Can take pictures of a physical screen if that is helpful.

Relevant log files

I do not have an easy way to pull log files, but if there's something you'd like me to sneakernet over, let me know.

Additional context

The DHCP server switch mentioned in the forum post was also not well-noted though it's been a long time in the making; the DHCP server stuff is NOT relevant to this bug report, though.

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 25.7, 26.1, 26.7 (amd64)
AT5NM10T-I/NA/SI
RTL8111E

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure on the reported RTL8111E hardware and the re0 interface across OPNsense 25.7, 26.1, and 26.7, using opnsense-revert where useful. Compare available NIC and system logs between working and failing versions, then verify that the interface powers up and detects networks again or that the regression is clearly documented in the changelog.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.