Messages

HISTORY
     The qat driver first appeared in FreeBSD 13.0.

Which implies as soon as OPNsense upgrades to Free/HardenedBSD 13, the support will be there. If not in the UI, you can always set a tunable to load the driver as described in the manpage.

Nicht ganz.

Quelle: LAN_NET
Ziel: WAN1_NET
Action: block

Quelle: LAN_NET
Ziel: WAN2_NET
Action: block

Und diese einfach weiter oben positionieren als die

Quelle: LAN_NET
Ziel: *
Action: permit

If the "old" usb-hid driver works, you are lucky. Sorry if I suggested it was completely broken. It does not work with a couple of devices, though. And the software has indeed not been updated since 2016, because they did not publish another release for 5 years ...

How can install the version from github?

You would need to checkout the source from github and build it on HardenedBSD yourself.

Any downsides to sideloading like that?

Sorry, no idea.

Dang, unfortunately my ups is USB only, surprised that's been broken so long.

The current version on github seems to work fine, but without a release since 2016 it's almost impossible to update the FreeBSD package.

NUT and the USB HID driver are broken on FreeBSD because they are using an unsupported legacy API. According to information I got on their mailing list they have implemented the new API, but since they have not tagged a release since 2016, that code has not made it into any FreeBSD package, yet.

Your best bet (IMHO) is to get a network card for your UPS if available and use SNMP.

Well, even if it is listening on WAN your firewall rules should prevent access, right?

Of course you don't need to activate it on WAN, sorry.

You never should run fsck on a live system! Your filesystem is most probably ok. Inconsistencies exist because your system is up and running ...

That's why you need to boot into single user mode. Then the filesystem is mounted read-only and fsck can work on it.

Run

  fsck -y

in single user mode.

This is by design. These filesystems are created dynamically by the FreeBSD/HardenedBSD OS and you cannot write to them, anyway. They are always at 100%.

I would not want another box just for a single application that works perfectly on my already present OPNsense.

I meant make your Unbound listen to 127.0.0.1:53530. I use BIND, so - sorry - I cannot show you a screenshot. I am just assuming that just as with BIND you can change the listen interface and port for Unbound too. If that is not the case, I am sorry.

You need to do that so AdGuardHome can listen on all interfaces port 53 so clients can use it. Then in AdGuardHome use this dialog to configure the upstream resolver (see screenshot).

To adjust the listen addresses of AdGuardHome itself you need to ssh to your OPNsense and edit the config file at /usr/local/AdGuardHome/AdGuardHome.yaml:

Code Select Expand

bind_host: 0.0.0.0
bind_port: 3000
[...]
dns:
  bind_host: 0.0.0.0
  port: 53

I did a write up in that other thread.

1. Activate mimugmail's community repository
2. Install AdGuardHome from System --> Firmware --> Plugins
3. Change your primary DNS server on OPNsense to use e.g. 127.0.0.1:53530 only
4. Activate and start AdGuardHome from Services --> AdGuardHome
5. Navigate to http://your.opnsense:3000/ to complete the setup

Why don't you install AdGuardHome on your OPNsense? Which was precisely the point in that other thread?