HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
opnsense
core
PHP2021–2025
opnsense / core

core

OPNsense GUI, API and systems backend

7Distinct people
8Mentions
0Explicit recommenders
4.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

OPNsense GUI, API and systems backend

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2021-01-26 04:25:31 UTC to 2025-12-04 07:32:51 UTC.

01232021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

8 sources
Yeah, pfsense apparently just solved this partly (except for aliases) [1], same with OPNsense [2], where there is still an open issue [3]. There are some declined PRs that are not "high priority" [4]. Note that I have just looked these issues up - I don't have insight into any of these. This is not meant as ranting. [1]: https://redmine.pfsense.org/issues/6626 [2]: https://github.com/opnsense/core/issues/2544 [3]: https://github.com/opnsense/core/issues/6158 [4]: https://github.com/opnsense/core/pull/5574
In The world in which IPv6 was a good design (2017)
I researched OPNSense vs pfSense a year or so ago when I was making a choice migrating from my Linux-based firewall. I ended up chosing pfSense, because I thought it offered a better support. I regret now, especially that I only recently learned that OPNsense offers a free ET Pro (Telemetry)[1] subscription for Suricata, which is otherwise available to pfSense on a paid basis only. Now I am looking to migrate to OPNSense, but unfortunately their backup files are not compatible and OPNSense does not make any effort to facilitate the migration ([2]), which, especially in light of recent pfSense controversies, is IMHO a serous omission . Not that I am saying they should provide a "one click wizard" solution, but at least having a way to tell which of the pfSense backup sections are incompatible with OPNsense and need to be otherwise set up
Read the rest
In PfSense Is Closed Source

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.