Messages

Thank you Patrick!

You are right. It is 26.1 + upgrade. I meant fresh install as in completely reinstalled this month after the SSD failure.

Other than RSS I haven't enabled anything extra from the default installation. My SSD died so that's why I did a fresh install recently.

It's a fresh install:

Code Select Expand

strings /boot/loader.efi | grep "EFI loader"
FreeBSD/amd64 EFI loader, Revision 3.0

Code Select Expand

strings /boot/efi/efi/freebsd/loader.efi | grep "EFI loader"
DFreeBSD/amd64 EFI loader, Revision 3.0

Hello,

Just FIY for posteriority.

I've had an issue with OPNsense 26.7.1 on bare metal Intel i5 4th gen CPU after power loss. Rebooting would freeze showing:

EFI framebuffer information:
addr, size    0xe0000000, 0x1d4c00
dimensions    800x600
stride        800
masks         0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000

The only way to make it boot was to select kernel.old at the boot menu.

I've tried multiple fixes: disabled Fast Boot, set hw.syscons.disable=1, set efi_max_resolution=0.

The thing that worked was to uninstall cpu_microcode and reboot. I had 3 packages:

Code Select Expand

pkg info | grep microcode

Code Select Expand

pkg remove WhatEverWasFoundInTheEarlierCommand
After this the router booted normally even with power loss.

I'm encountering the same situation. Surely this isn't the desired behavior, right? I mean, what's the point of putting in the Cloudflare API key if you have to manually create the TXT record?

I'm on:

OPNsense 24.1.6-amd64
FreeBSD 13.2-RELEASE-p11
OpenSSL 3.0.13

Sorry to necrobump, but is this tutorial still accurate? I'm asking because I've followed the instructions and IPv6 isn't working for me. I'm trying to assess if the issue is with my configuration or if it's more general. I'm getting the IPv6 only on WAN, but nothing on LAN devices. What's worse, enabling IPv6 seems to be breaking my otherwise functioning HAProxy.

I've opened a bug report and the guys from SunnyValley were fast to reply. It seems that the packet engine is crashing. They gave me a debug binary which generated some logs, that were sent to them.

After activating Sensei I've experienced the same behavior and sent a bug report. Thank you again for mentioning it!

I really would, but after uninstalling Sensei I cleaned up the system, so there are no logs to send.
Anyway, I've reinstalled it and set it to reporting only.
I did that in the past too, and I kept getting disconnects.
I will wait to see when I get the first disconnect in the monitoring system and try to report a bug.
Thanks for the idea!

Hello,

I'm running:

OPNsense 22.1.6-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1n 15 Mar 2022

on:

Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 cores, 4 threads) with 16GB RAM.
My ISP offers a 1 Gbps connection with PPPoE authentication and dynamic IP address.

I have Zenarmor(Sensei) installed and configured(on LAN interfaces) for some time now and it's been working perfect, but for about 2 weeks I keep getting 3 daily disconnects within the same time range with random behavior.
Time range:

• In the morning: between 10:00 to 11:00
• Evening: 19:00
• Night: 03:00

Random behavior: Sometimes all the LAN clients can't access the internet but the WAN connection doesn't change the IP address. Sometimes the WAN IP get's changed, meaning the PPPoE connection has been reinitialized.

It's not a big deal, but it's annoying especially if I'm working from home and have a VPN connection to the office, or my outgoing ssh connections from other servers get dropped.

I've checked the cron and I don't have anything running around that time.
I've arrived at the conclusion that Sensei is to blame after uninstalling it and seeing the issues disappear for a couple of days and having the issues reappear immediately after reinstalling.

Has anyone else experienced this sort of behavior?

Nu-i ashe ?

Salut!

Ca si in celalalt thread, postez pentru cine da din greseala peste aceste intrebari.
Tocmai am rulat un speedtest din spatele OPNsense si acesta este rezultatul https://www.speedtest.net/result/12032620736
OPNsense functioneaza foarte bine cu conexiunea PPPoE de la Digi.

Salut!

Motivul pentru care postez este sa nu se lase impresia ca OPNsense are probleme de performanta cu conexiunea gigabit.
Eu il folosesc si pe clienti transfer cu 8-900 mbps(si am multe servicii activate pe OPNsense).
Problema in acest caz imi pare a fi adaptorul acela USB-RJ45. Poate nu este gigabit, poate nu are driverul bun, poate este conectat intr-un port USB 2.0.

I thought I should try maltrail with the work-around of daily restarting the maltrail sensor from cron but I have noticed two things.

1. In high traffic periods restarting only once per day wasn't enough. I had to modify the cron to run hourly.
2. After a couple of days I found multiple maltrail sensor orphaned processes which I had to kill manually from cli.