Messages

Thanks @RamSense!

So the answer to my question is basically in https://github.com/opnsense/core/issues/5205

Code Select Expand

#! /bin/sh
cd /usr/local/lib/python3.8/site-packages/netaddr/eui
curl -s -o oui.txt https://standards-oui.ieee.org/oui/oui.txt
curl -s -o iab.txt https://standards-oui.ieee.org/iab/iab.txt
python3 ieee.py
By the way, I do think we should not rely on the generated files from https://github.com/netaddr/netaddr/blob/master/netaddr/eui/iab.idx and https://github.com/netaddr/netaddr/blob/master/netaddr/eui/oui.idx. The script ieee.py still works as at today and I don't think the author is obligated to update these files in github/upstream as developers using his code shall generate the files on his own.

My 2 cents,
Hazuki

Hi,

In the DHCP lease table of (Web UI) Services: Kea DHCP: Leases DHCPv4, MAC address column shows vendor information if the database in somewhere has such information.

I do believe above-mentioned database is pretty much outdated as the table does not show the vendor information of some of my devices (e.g. D8:3B:DA, 10:00:3B, 5C:01:3B), which upon checking, the OUI was registered in 2024.

I want to update the database (if the database is within the metal) or update the link to the database (if the database is on the internet). Where should I start from? Any help is appreciated.


Thanks in advance,
Hazuki

Thanks Maurice! My bad I didn't mention the firmware version, and indeed it is 15.1.
The patch works like a charm and now everything works as expected.

Hazuki

Hi

I want to set up monit to repeat execute a script when ping keeps failing. According to https://stackoverflow.com/questions/56011030/monit-only-executing-once, monit should be good for my purpose if "repeat" is defined in the syntax. However, with web GUI, my best attempt is to set the syntax to:

Code Select Expand

If failed count 5 size 64 with timeout 5 s via address <router IP> then exec '<some script>' (as seen in httpd). I don't see anywhere in Web GUI I can put "repeat" in to the syntax. How can I complete the syntax to

Code Select Expand

If failed count 5 size 64 with timeout 5 s via address <router IP> then exec '<some script>' repeat every cycle
Thanks in advance,
Hazuki

Not sure if just my geolocation (China) matters, the mirror https://dns-root.de/ seems down. Anyone can verify this ?

Thanks in advance

Thanks for explaining the purpose of experiment track! :)
No wonder I can see the reported OPNsense version is 24.7 yet kernel is still 13.2.

Is it just me after upgrade from release type : development and 24.1, the kernel is still in 13.2?

Code Select Expand

FreeBSD OPNSENSE 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 stable/24.1-n255023-99a14409566 SMP amd64

I am expecting the development 'channel' shall enable the kernel be upgraded to 14.1. May be I was wrong?

I was once tried 14.1-STABLE kernel in 24.1, and

Code Select Expand

opnsense-update -k told me nothing to do

Thanks in advance,
Hazuki

I am not sure if I am looking into the right place. In https://github.com/opnsense/src/blob/volatile/24.7/sys/conf/newvers.sh , looks like 24.7 will be in FreeBSD 14.1.

Code Select Expand

TYPE="FreeBSD"
REVISION="14.1"
BRANCH="BETA1"

If this is true, I really looking forward to test the BETA 24.7 as the performance gain in wireguard is really astonishing.

One may test FreeBSD 14 kernel in OPNSense after selecting the snapshot

Code Select Expand

opnsense-update -zkr 14-STABLE -a FreeBSD:14:amd64

Test FreeBSD 14 kernel at your own risk!

This FreeBSD 14.1 kernel indeed boost up wireguard speed.
More information are in https://forum.opnsense.org/index.php?topic=40413.msg198242#msg198242

EDIT 1: add missing -b switch in code. Solely updating kernel without base file will lead to messed-up routing in my setup.
EDIT 2: add warning regarding failed ISC DHCPv4
EDIT 3: add warning regarding failed pkg command
EDIT 4: I was told by franco that updating kernel only (not base file) should be good to test. Updating base file will break more things. I have removed -b switch and later found out duplicated entry (same port) in port forward led my firewall messed-up while using 14.1 kernel in 24.1 base file. (pfctl: DIOCADDRULENV: File exists). All warnings removed