Recent posts

#1
26.1, 26,4 Series / Re: samplicate pegging cpu
Last post by franco - Today at 01:40:35 PM
Ok, that's the why but not the how...

# pluginctl -g OPNsense.Netflow

If you delete that file and it keeps reverting to "YES" you have not reset it properly in the settings.


Cheers,
Franco
#2
26.7 Series / Re: Firmware upgrade from 26.1...
Last post by franco - Today at 01:37:08 PM
Thanks for the feedback.  Happy to hear!  :)


Cheers,
Franco
#3
General Discussion / How is AI leveraged in the dev...
Last post by Lucid1010 - Today at 01:29:04 PM
https://freebsdfoundation.org/blog/freebsd-ai-assisted-vulnerability-discovery-project-launch/

https://www.reddit.com/r/technology/comments/1vkjpxh/linus_torvalds_says_ai_has_made_huge_linux_kernel/


Even if not for vibe coding, it would still be useful for security vulnerability scanning of OPNsense core and plugins, performance tuning, and WebUI development.
#4
General Discussion / Re: Rclone backup support
Last post by Patrick M. Hausen - Today at 01:27:47 PM
What exactly are you intending to backup? There isn't much besides the config.xml, really.
#5
General Discussion / Re: Rclone backup support
Last post by Lucid1010 - Today at 01:23:00 PM
https://rclone.org/downloads/

Since rclone uses a FreeBSD binary, you can run backups directly using a shell script.
I currently back up to Dropbox and S3 via rclone.
#6
German - Deutsch / Re: Log File -> Live View
Last post by Patrick M. Hausen - Today at 01:18:32 PM
@feofan69 Kurzfassung:

Zwei Geräte im selben Netzwerk brauchen keinen Gateway, um miteinander zu kommunizieren. Und selbst wenn sie einen konfiguriert haben, benutzen sie ihn nicht. Niemals. Das ist so. Der Gateway wird nur benutzt für Verbindungen in andere Netze. Das ist die Aufgabe eines Gateways.

Es gibt Switche, die Filter-Funktionen haben und so etwas können, was du wahrscheinlich willst. Außerdem kann man bei vielen Access-Points "Client Isolation" aktivieren, so dass Geräte im selben Netz nur mit dem Gateway aber nicht untereinander kommunizieren dürfen.

Alles andere findest du dann aber wirklich in Netzwerk-Grundlagen-Literatur, da hat @meyergru nicht Unrecht.
#7
26.7 Series / Re: Can settings from ver OPNs...
Last post by lmoore - Today at 12:24:58 PM
Quote from: seamus on Today at 10:47:54 AMI've hit a snag in setting up the "isolated network"

You have a DHCP server running in OPNsense on your LAN port, so you can't simply change the LAN IP address from the console whilst the DHCP server is running.

Isolated Netowrk:

        +-------------------+                       +-------------------+
        |     PC with       |                   LAN |     Backup        |
        |  Ethernet port    |<--------------------->|     OPNsense      |
        |  IP set manually  |    Ethernet Cable     |     Firewall      |
        | 192.168.1.254/24  |                       |  192.168.1.1/24   |
        | unless DHCP is    |                       |                   |
        |    working        |                       |                   |
        +-------------------+                       +-------------------+

I don't understand why you plugged the WAN port in to your functioning LAN - it wasn't going to work. That's why I advised disconnecting network cables.

What happened when you substituted the machines after restoring the configuration?

Working with the Backup machine and your PC, which are isolated from the rest of your network, plug a network cable into the Backup machine's LAN port and plug the other end into your PC's Ethernet port.

If you don't receive an IP address after a couple of minutes, manually configure TCP/IP on the PC and assign an unused IP address on your 192.168.1.0/24 network, such as 192.168.1.254/24, set the gateway and DNS server addresses to 192.168.1.1 .

If you are you able to ping 192.168.1.1 you should be able to access the Web GUI too.

If you have access to the Web GUI, plug your WAN cable from the Primary machine in to the WAN port of the Backup machine.

Let me know what is and isn't working at this point.

What are the interface names for LAN & WAN?
#8
German - Deutsch / Re: Log File -> Live View
Last post by meyergru - Today at 12:10:30 PM
Nein. Zwei Geräte im selben IP-Subnetz/VLAN kommunizieren normalerweise direkt auf Layer 2 miteinander. Bei IPv4 wird die MAC-Adresse des Zielsystems per ARP ermittelt, bei IPv6 übernimmt das NDP. Das konfigurierte Default-Gateway spielt dabei keine Rolle.

Der Traffic geht deshalb vollständig an der Firewall vorbei. Sie kann ihn weder filtern noch überhaupt sehen.

Wenn Du den Verkehr zwischen Geräten filtern willst, musst Du sie in unterschiedliche Layer-3-Netze/VLANs legen, so dass der Verkehr tatsächlich geroutet werden muss. Alternativ braucht es entsprechende Layer-2-Mechanismen auf dem Switch.

Das ist Netzwerk-Basiswissen, das Du Dir aneignen solltest, bevor Du mit einem Werkzeug wie OPNsense arbeitest. Das klingt vielleicht herablassend, ist aber bierernst gemeint: Anders als bei Consumer-Produkten wie einer Fritzbox ist es sehr schwierig, sein Netzwerk mit einem komplexen Werkzeug wie OPNsense tatsächlich "irgendwie sicherer" zu machen, wenn die zugrunde liegenden Netzwerkmechanismen nicht verstanden sind.
Darauf weise ich auch hier in Punkt 1 hin.

Das Risiko, dabei etwas grundsätzlich falsch zu konfigurieren und sich nur in Sicherheit zu wiegen, ist ziemlich hoch – wie diese Diskussion ganz gut illustriert.
#9
General Discussion / Re: No WAN connection after po...
Last post by recess7139 - Today at 11:26:56 AM
Yes my install is on ZFS, I can't currently check the boot issue due to not having physical access. I usually configure everything over wireguard but everything I have mentioned since the connection issue has been done on a video call with people who do have physical access, they're not the most technical and plugging a mouse and keyboard in etc to check the bios is out of scope. It is ridiculous I know but my options are limited at the moment. I do have the ISP router ready to go as a backup if this can't be fixed remotely
#10
26.7 Series / Firmware upgrade from 26.1.11_...
Last post by turipriv - Today at 11:15:04 AM
OK, this time it took me a bit longer than usual to upgrade, given the reported CPU microcode issues.

Today, I finally decided to take the leap and go ahead with the upgrade.

For what it's worth, this is the path I've taken:

 - Uninstalled os-cpu-microcode-intel plugin
 - Upgraded from 26.1.11_10 to 26.7
 - Automatic reboot
 - Upgraded from 26.7 to 26.7.3_11
 - Automatic reboot
 - Reinstalled os-cpu-microcode-intel plugin
 - Manual reboot

My unit works like a charm; all services loaded and no issues whatsoever; hardware and running features as per signature.

For the sake of completeness, the microcode plugin is currently running in late load mode.

Usual round of applause to the team and the community for yet another amazing release.