Recent posts

#1
German - Deutsch / Re: Problem mit Port Forwardin...
Last post by BeTZe313 - Today at 05:37:53 PM
Die wurde ja automatisch erstellt als ich das Port Forwarding gespeichert habe. Die kann ich nicht bearbeiten. Folgendes kann ich da sehen
#2
26.1 Series / Re: os-git-backup error with 2...
Last post by franco - Today at 05:35:40 PM
There will probably be a .1 next week for OpenSSL...
#3
25.7, 25.10 Series / Re: After updating Opnsense fr...
Last post by allenlook - Today at 05:32:24 PM
Will do, thank you!

In the past several hours, on the "old" version with IDS enabled, the memory utilization is still in the 30% range.
#4
26.1 Series / Re: radvd warnings
Last post by Boxer - Today at 05:15:25 PM
Ok, Thanks Franco. I'll just keep an eye on it for now then
#5
26.1 Series / Re: Rules migration completion...
Last post by franco - Today at 05:10:34 PM
Yes.


Cheers,
Franco
#6
26.1 Series / Re: radvd warnings
Last post by franco - Today at 05:10:06 PM
Hi,

Thanks for the report.

I'm inclined to say this is due to the noisier logging we've introduced in 26.1 (including RCs), because we don't set "AdvCurHopLimit" anywhere so this is some kind of clash in your network.  I'd say it's safe to ignore but I also don't know what it means since we've never had these logs before.

At some point diving into the radvd source code may be a good idea to see what it means.


Cheers,
Franco
#7
25.1, 25.4 Series / Re: default hw.vtnet.csum_disa...
Last post by jauling - Today at 05:07:01 PM
Would it make sense to track this topic in the 26.1 Series forum? I checked the 26.1 release notes, did not find anything related to hw, hardware, offload.

TBH, I haven't revisited this topic since my last post in this thread. I'm assuming this issue is still open.
#8
26.1 Series / radvd warnings
Last post by Boxer - Today at 05:03:58 PM
Hello and congrats on 26.1 releasing. Thanks for all the hard work!
I'm using radvd with DNSmasq and after updating from 26.1 rc2 my logs are filling up (every minute) with these two radvd warnings that weren't previously there on rc2.

our AdvPreferredLifetime on igb1 for 2a00:23c7:bbbb:d800:: doesn't agree with fe80::bbbb:bbbb:fe67:8b81
our AdvCurHopLimit on igb1 doesn't agree with fe80::bbbb:bbbb:fe67:8b81

Connectivity seems fine, I'm not observing any anomalies. Just wanted to report just in case. I haven't touched router advertisements since rc2. I use 'assisted' mode and everything is as default.
#9
Hey Maurice,

thank you for your reply and glad to hear, that this workaround is also used by other people.

Yeah, my WireGuard clients also have IPv4 addresses. But I need to connect to some IPv6 only services, so I also need the IPv6 capability for the clients.
#10
26.1 Series / Rules migration completion (2 ...
Last post by julsssark - Today at 04:57:06 PM
I completed a test rules migration with 26.1 in a VM. I clicked to remove all rules in the legacy interface. I thought the old Rules interface would disappear, but it continues to coexist with Rules [new]. I rebooted the router but both are still there. Is that the expected behavior?