Messages

Nicht rein schreiben sondern einfach zum Stammtisch kommen, bitte. Das ist kein Diskussions- und Hilfe-Thread.

Diesen Freitag ab 17:00 z.B. :-)

Ich bin auch Team "AdGuardHome", nutze dabei eine Textliste, die ich vom Notebook aus automatisch auf einen Webserver lade ( einfacher NGinx-Container ) wo Adguard sich die dann regelmässig holt  und aktiviert

Noch besser als Vorschlag: git. Z.B. ein selbst betriebenes Gitea oder Forgejo. Damit hat man dann sogar noch eine Versionierung.

1. Interfaces > Devices > VLAN - create VLAN
2. Interfaces > Assignments - assign "WAN" to the VLAN you created
3. Interfaces > WAN - enter IP address and mask/prefix-length
4. System > Gateways - add gateway

Done. All of this is well documented.

Then you need the netmask and the gateway in addition to the IP.

Which one is the ISP using?

- DHCP
- PPPoE
- static configuration

Is the modem/ONT set to bridge mode?

https://docs.opnsense.org/manual/other-interfaces.html#vlan

Und das hat genau was mit OPNsense zu tun?

NAT is applied before filter rules, so the destination address needs to be the internal DNAT target, not the public address on WAN.

[all]

Yes to your question about the plugin. But OPNsense pulls all packages from the OPNsense repo. If you manually activate the FreeBSD repo, you have a high probability of messing up you installation. Simply don't do that.

Isn't the business edition always based on the preceding community edition?

Yes.

Say, the CE doesn't adopt FreeBSD 15.1 in July, then the BE won't be based on it either, right?

Most probably.

As I wrote FreeBSD releases and OPNsense releases are not in any way coupled.

OPNsense community editions are released in January and July.
OPNsense business editions are released in April and October.

This is completely independent of the FreeBSD release schedule.

[Output shown here for diagnostic purposes. There is no general need for manual system intervention.]

It appears that it's the x86info utility (also installed by the plugin) that reports itself as deprecated, not the (whole) plugin.

Correct. People also tend to overlook the message below that text box:

Output shown here for diagnostic purposes. There is no general need for manual system intervention.

Kernfgrage : Auf welchem Interface laufen die Unbound-Anfragen für OpenVPN - meine Vermutung ist, dass das WAN hierfür verwendet wird.

Das OpenVPN-Interface, naheliegenderweise. Das hat doch eine IP-Adresse im Infrastruktur-Modus.

At this point, with what we have seen over the last 12 months, I would just remove it

Then you will run your CPU without any ucode updates (apart from ones that might be in your MB manufacturer's BIOS). The updates the FreeBSD/OPNsense plugin provides are not permanent but need to be applied at every boot.

Do I really need to have two network cards?

No.