Interfaces widget: unknown media type for umb/MBIM

Open Beginner friendly
  • Is something wrong?
#11,201 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start in /usr/local/opnsense/www/js/widgets/Interfaces.js, where the issue's local workaround changes the displayed media label for umb devices. Check how the widget handles unknown media information; done when an umb interface shows a meaningful fallback such as “Mobile broadband (MBIM)” without assuming LTE.

Written by the indexing model from the issue text.

Description

Important notices

If AI was used, please disclose:

  • Model used: OpenAI Codex, based on GPT-6.
  • Extent of AI involvement: Assisted with troubleshooting, a local display workaround, and drafting this report in English. I applied the workaround and verified its effect on my firewall.

Describe the bug

The Interfaces dashboard widget displays <unknown type> as the media description for a working umb0 MBIM cellular interface using a Sierra Wireless MC7455 modem.

The cellular connection works, including Internet access and WAN failover. The problem reported here concerns the displayed media description.

The interface also reports media: <unknown type> through ifconfig. A readable fallback label in the widget would make the interface easier to identify.

I do not have a confirmed last known working version without the local workaround.

To Reproduce

  1. Connect a Sierra Wireless MC7455 modem operating in MBIM mode and using the FreeBSD umb driver.
  2. Assign umb0 as an OPNsense interface and establish the cellular connection.
  3. Open the Interfaces dashboard widget.
  4. Observe the media description: <unknown type>.

Expected behavior

When media information is unavailable for an umb interface, display a meaningful fallback such as Mobile broadband (MBIM).

This wording would avoid assuming that every connection using the driver is specifically LTE.

Describe alternatives you considered

I use a local modification to:

/usr/local/opnsense/www/js/widgets/Interfaces.js

The modification checks whether the device name starts with umb and substitutes LTE / MBIM as the displayed media label.

This works on my system, but OPNsense updates overwrite the modification. A built-in fallback would remove the need to reapply it after updates.

The requested change concerns the widget display; it does not require changing the driver's media reporting.

Screenshots

No screenshot of the original widget display is available. The local workaround is currently applied.

Relevant log files

Relevant lines from previously captured ifconfig umb0 output:

umb0: flags=1008851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        description: WAN_LTE (opt3)
        options=0
        media: <unknown type>

Additional context

My MBIM setup and local workarounds are documented in:
https://github.com/Krzychencjusz/opnsense-lte-umb-mbim

This repository provides background on my setup. This report specifically concerns the Interfaces widget's media label.
I searched open and closed issues using terms including umb, umb0, MBIM, and "unknown type" "Interfaces" and did not find a matching report.

The interface is intentionally configured with IPv4 Configuration Type set to None: its runtime IPv4 configuration is supplied through the MBIM setup. The cellular connection itself is operational.

Environment

  • OPNsense 26.7.9_1 (amd64)
  • Modem: Sierra Wireless MC7455
  • Connection mode: MBIM
  • FreeBSD driver/interface: umb / umb0
  • Assigned interface: WAN_LTE (opt3)
Dominant language
PHP
Stars
4.8k
Forks
1k
Avg merge
1d 20h
Merged PRs (30d)
36

Getting set up

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.

More from opnsense/core

All issues in opnsense/core

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.