Topics

Hello,

due to an overlooked gateway change during the expansion of the subnet range last year, I had a network whose gateway was not set up correctly.
So I wanted to get an overview of all configured gateways, DNS, domains, and more, but it's impossible.
All fields except for the standard fields Subnet, Description, Pools, Match client-id, and Auto collect option data are empty.

During my research — why no one has found this obvious error in the last two years is beyond me — I came across

https://github.com/opnsense/core/issues/7298
which was apparently the bug report attempt in this forum post:
https://forum.opnsense.org/index.php?topic=39161.msg191823#msg191823.

I "love" the defensive behavior of the bot and some developers as always...
1. dismissing it as unimportant or unnecessary and delaying it, and
2. then closing the bug because the bot is picky about the behavior that it itself triggered with its extremely poor response.

Maybe someone can take care of the problem after two years.
It shouldn't be that difficult to read and return the field values correctly.

Best regards

For "Packages" it's maybe intentionally not setup because usually they are dependencies of the plugins.
But if not it could be sometimes of interest to remove them manual over GUI (and maybe there could be a function to fetch such rare packages by URL?).

With this update the OS-WireGuard plugin is somehow also a candidate which cannot be removed from list of installed plugins.
I guess because it's now included in main OPNsense core because I can see it still within VPN section ?

We are moving from pfSense to OPNsense and network routers step by step;
Last week we switched DHCP and had some trouble with one user which needs static IP for having dedicated outbound NAT for SEO work with Google.

It seems solved first but today she had again problems - not DHCP assignment anymore but now accessing internal services.
After quick investigation and tcpdump sniping it was clear that the DHCP servers offers the "default" DNS server (him itself) instead of our typed in ADS nameservers.

1st setup was static entry with mac/hostname/ip address and VLAN/Interface based DNS servers "only"
2nd setup was with same additional dns servers in static setup but still "defauilt server" assigned.

Quick workaround was to forward Unbound to query ADS with "private domains" setup as prepared.
But this seems to be a bug which should be fixed for situations where this workaround can't be done.
And we want also best the right DNS servers directly assigned.

Can someone proove it? Dependend on situation I can open bug report if needed on Github.

Hi, neither OPNSense, pfSense nor windows/mac/linux clients can use 2FA for Wireguard because the service lucks of such "complicated feature"... which is sadly because OpenVPN limits clients traffic to usually around 16 MBit .

But there is a nice projected with a "2fa login page" which looks interesting and possible to implement as plugin for OPNsense:
https://github.com/NHAS/wag

Iit's iptables based but it shouldn't be too problematic to adopt such code for pf firewall rules for people which knows what to do?

Bests

Reiner