@cmcdonald Appears to be back/fixed. Thanks.

You can set the size it rotates at and the number of files to retain in the log settings at Status > Logs > Settings. As long as you have the space you should be able to increase it.

@stephenw10 The Ultra Ethernet Consortium

@stephenw10 Aye that's right

Hi guys, I create simple shell script reports for AbuseIPDB from filter.log file. Maybe it will be helpful to someone. It was tested over a one-week period and works as expected. Here is the link: ttps://github.com/whoami-0x44/abuseipdb-reporting-pfsense

Yes you can choose 2.8.0-beta from the installer menu. Edit: Now 2.8.0-RC

Nope, none of those are a big concern. Some of that could be cleaned up but they are just ugly.

@w0w Seems so or possibly an interaction with if_pppoe and something else within the new beta. Regressing to 24.11 again and symptoms vanish. Reverting to the old backend on the beta seems fine too (albeit with the old pppoe issues). I had to work back again and re-test as I had the test diff patch applied with the revised beta, which drew some doubts on my results for a while. Fat-fingering in a config error when testing is something I try to avoid but you have to admit your mistakes. I'm waiting for the next beta drop really, to see if the changes also impact the issues I see. Opening up all the cores may just be peeling back something that was already latent and just masked by the old backend process. I did do a couple of tests that suggests the upload fq_codel settings may need adjusting against a different workload for if_pppoe; but too early to be sure. I'm also being nudged to try Kea again, as apparently it has matured a bit since its launch. ️

Hmm, it does seem kinda shady! There's no FreeBSD port as far as I can see, though there is one for v2ray which this was forked from. You are asking about adding it as a client to connect to the xrayvpn service only? I'm not really seeing any advantages over existing VPN options TBH.

@matthijs I had an issue with a static arp entry, but it was a wrong configuration on my side (an old wrong static arp entry/Mac address) The IP adres with this static ARP entry was in use by another host (with another MAC address) an that was an issue. I did not experience this in 2.7.2 So in fact 2.8.0 is behaving correctly

@jimp oh cool, it never even occurred to me that ppl would carry around a universal cert

@patient0 Worked! thanks!

The rule order in the configuration file is supposed to reflect both the rule processing and rule position (i.e. what's shown in the GUI) order. Ultimately, the processing itself is determined by what gets put into /tmp/rules.debug. As for the rule position in the GUI, there are multiple factors involved. With the latest fixes (referenced in the thread linked above), what does happen should finally match what is supposed to happen.

@techpro2004 FFS.

@antoine2711 said in Can’t compile a port software. Error: Unable to determine OS version. Either define OSVERSION, install /usr/include/sys/param.h or define SRC_BASE: Hi @bmeeks, I was able to retreive the pkg in the cache folder of my FreeBSD (/var/cache/pkg). Thanks for your help again. I’m ok for now. Best Regards, Antoine The risk with installing packages from the stock FreeBSD repo (or any other repo except the official pfSense repo for your version) is that the versions of various shared library dependencies may differ from what is currently used by pfSense. The pkg utility will automatically attempt to download and install any shared library dependencies needed by the package you are installing. So long as those are the same ABI and shared library versions as what already exists on the pfSense installation, you are fine. It's when they differ that your pfSense installation can get broken - and sometimes irretrievably broken.